Garvin LeClaire (JIRA | 1 Apr 2008 05:09

[jira] Assigned: (MFINDBUGS-53) The plugin fails for non-source modules


     [
http://jira.codehaus.org/browse/MFINDBUGS-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Garvin LeClaire reassigned MFINDBUGS-53:
----------------------------------------

    Assignee: Garvin LeClaire

> The plugin fails for non-source modules 
> ----------------------------------------
>
>                 Key: MFINDBUGS-53
>                 URL: http://jira.codehaus.org/browse/MFINDBUGS-53
>             Project: Maven 2.x FindBugs Plugin
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Maven 2.0.7
>            Reporter: Odd Vinje
>            Assignee: Garvin LeClaire
>
> When using the plugin versjon 2.0-SNAPSHOT on a module without sources (and classes), i.e. ear modules,
it fails with : 
> [ERROR] BUILD ERROR
> [INFO] ----------------------------------------
> [INFO] Failed executing FindBugs
> Embedded error: No classes found to analyze in ...
> This works in version 1.1.1, and s probably related to the findbugs core upgrade. 

--

-- 
(Continue reading)

Garvin LeClaire (JIRA | 1 Apr 2008 05:13

[jira] Commented: (MFINDBUGS-53) The plugin fails for non-source modules


    [
http://jira.codehaus.org/browse/MFINDBUGS-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129258#action_129258
] 

Garvin LeClaire commented on MFINDBUGS-53:
------------------------------------------

Does this mean you are running this against a Maven build that assembles a WAR or EAR but does not have source
files itself?

> The plugin fails for non-source modules 
> ----------------------------------------
>
>                 Key: MFINDBUGS-53
>                 URL: http://jira.codehaus.org/browse/MFINDBUGS-53
>             Project: Maven 2.x FindBugs Plugin
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Maven 2.0.7
>            Reporter: Odd Vinje
>            Assignee: Garvin LeClaire
>
> When using the plugin versjon 2.0-SNAPSHOT on a module without sources (and classes), i.e. ear modules,
it fails with : 
> [ERROR] BUILD ERROR
> [INFO] ----------------------------------------
> [INFO] Failed executing FindBugs
> Embedded error: No classes found to analyze in ...
> This works in version 1.1.1, and s probably related to the findbugs core upgrade. 
(Continue reading)

deckrider (JIRA | 1 Apr 2008 06:44

[jira] Created: (MOJO-1084) solaris maven plugin behaves badly when used in two modules of a multi-module build

solaris maven plugin behaves badly when used in two modules of a multi-module build
-----------------------------------------------------------------------------------

                 Key: MOJO-1084
                 URL: http://jira.codehaus.org/browse/MOJO-1084
             Project: Mojo
          Issue Type: Bug
         Environment: solaris
            Reporter: deckrider

I have a multi-module build where two of the modules are solaris packages.  During install or deploy,
instead of copying to 'foo-1.0.pkg' it copies to 'foo-1.0.solaris'.

Is there a workaround or patch for this?  I'm kinda desparate  :)

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Jason Dillon (JIRA | 1 Apr 2008 08:02

[jira] Updated: (MGROOVY-111) Stub generation does not build implied getter/setter methods


     [
http://jira.codehaus.org/browse/MGROOVY-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dillon updated MGROOVY-111:
---------------------------------

    Fix Version/s: 1.0-beta-4

> Stub generation does not build implied getter/setter methods
> ------------------------------------------------------------
>
>                 Key: MGROOVY-111
>                 URL: http://jira.codehaus.org/browse/MGROOVY-111
>             Project: Maven 2.x Groovy Integration
>          Issue Type: Bug
>          Components: stub generation
>    Affects Versions: 1.0-beta-3
>            Reporter: Jonathan Whitall
>            Assignee: Jason Dillon
>             Fix For: 1.0-beta-4
>
>         Attachments: Demo.groovy, DemoTest.java
>
>
> I'm using mixed compilation mode, and Groovy stubs generated do not include the implied getter / setter
methods you should get when defining a field with no modifier on a Groovy class. Therefore Java code which
depends on the methods signature of implied methods will not compile.

--

-- 
(Continue reading)

Jason Dillon (JIRA | 1 Apr 2008 08:02

[jira] Updated: (MGROOVY-105) Expose ExecuteMojo in script's execution context


     [
http://jira.codehaus.org/browse/MGROOVY-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dillon updated MGROOVY-105:
---------------------------------

    Fix Version/s: 1.0-beta-4

> Expose ExecuteMojo in script's execution context
> ------------------------------------------------
>
>                 Key: MGROOVY-105
>                 URL: http://jira.codehaus.org/browse/MGROOVY-105
>             Project: Maven 2.x Groovy Integration
>          Issue Type: Improvement
>          Components: execute
>    Affects Versions: 1.0-beta-3
>            Reporter: Andrew Perepelytsya
>            Assignee: Jason Dillon
>             Fix For: 1.0-beta-4
>
>
> I'm facing a big problem - need to determine the path to the m2 repo used at runtime (e.g. get an artifact and
scan it's file path). However, there's nothing like that accessible in the ExecuteMojo. I think adding
the ['mojo', this] map would help, executed scripts could then peek into maven api.

--

-- 
This message is automatically generated by JIRA.
-
(Continue reading)

Jason Dillon (JIRA | 1 Apr 2008 08:04

[jira] Updated: (MGROOVY-101) src/main/groovy folder is missing


     [
http://jira.codehaus.org/browse/MGROOVY-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dillon updated MGROOVY-101:
---------------------------------

    Fix Version/s: 1.0-beta-4

> src/main/groovy folder is missing
> ---------------------------------
>
>                 Key: MGROOVY-101
>                 URL: http://jira.codehaus.org/browse/MGROOVY-101
>             Project: Maven 2.x Groovy Integration
>          Issue Type: Bug
>          Components: archetype
>            Reporter: Zemian Deng
>            Assignee: Jason Dillon
>             Fix For: 1.0-beta-4
>
>
> Also the example groovy script should be in the groovy folder as well. Without this folder created, the mvn
compile fails.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
(Continue reading)

Jason Dillon (JIRA | 1 Apr 2008 08:10

[jira] Created: (MGROOVY-112) Drop Groovy 1.1 runtime support

Drop Groovy 1.1 runtime support
-------------------------------

                 Key: MGROOVY-112
                 URL: http://jira.codehaus.org/browse/MGROOVY-112
             Project: Maven 2.x Groovy Integration
          Issue Type: Improvement
            Reporter: Jason Dillon
            Assignee: Jason Dillon
            Priority: Minor

Drop the Groovy 1.1 runtime support module.  1.1 was never released, instead 1.5 was released.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

Jason Dillon (JIRA | 1 Apr 2008 08:12

[jira] Updated: (MGROOVY-112) Drop Groovy 1.1 runtime support


     [
http://jira.codehaus.org/browse/MGROOVY-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dillon updated MGROOVY-112:
---------------------------------

    Fix Version/s: 1.0-beta-4

> Drop Groovy 1.1 runtime support
> -------------------------------
>
>                 Key: MGROOVY-112
>                 URL: http://jira.codehaus.org/browse/MGROOVY-112
>             Project: Maven 2.x Groovy Integration
>          Issue Type: Improvement
>            Reporter: Jason Dillon
>            Assignee: Jason Dillon
>            Priority: Minor
>             Fix For: 1.0-beta-4
>
>
> Drop the Groovy 1.1 runtime support module.  1.1 was never released, instead 1.5 was released.

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
(Continue reading)

Jason Dillon (JIRA | 1 Apr 2008 08:12

[jira] Updated: (MGROOVY-113) Upgrade to Groovy 1.5.4


     [
http://jira.codehaus.org/browse/MGROOVY-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Dillon updated MGROOVY-113:
---------------------------------

    Fix Version/s: 1.0-beta-4

> Upgrade to Groovy 1.5.4
> -----------------------
>
>                 Key: MGROOVY-113
>                 URL: http://jira.codehaus.org/browse/MGROOVY-113
>             Project: Maven 2.x Groovy Integration
>          Issue Type: Improvement
>            Reporter: Jason Dillon
>            Assignee: Jason Dillon
>             Fix For: 1.0-beta-4
>
>
> Upgrade to Groovy 1.5.4

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

(Continue reading)

Jason Dillon (JIRA | 1 Apr 2008 08:12

[jira] Created: (MGROOVY-113) Upgrade to Groovy 1.5.4

Upgrade to Groovy 1.5.4
-----------------------

                 Key: MGROOVY-113
                 URL: http://jira.codehaus.org/browse/MGROOVY-113
             Project: Maven 2.x Groovy Integration
          Issue Type: Improvement
            Reporter: Jason Dillon
            Assignee: Jason Dillon
             Fix For: 1.0-beta-4

Upgrade to Groovy 1.5.4

--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Gmane