[jira] Commented: (MGROOVY-48) Generate groovy plexus components descriptor

    [
http://jira.codehaus.org/browse/MGROOVY-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108715
] 

Jason Dillon commented on MGROOVY-48:
-------------------------------------

FYI, I've not forgotten about this... and I've recently been all over the plexus-maven-plugin and its cdc
stuff to get Java5 annotations and Java 1.5 Javadoc tags working... so I think I've got the tools to make
this happen finally.

> Generate groovy plexus components descriptor
> --------------------------------------------
>
>                 Key: MGROOVY-48
>                 URL: http://jira.codehaus.org/browse/MGROOVY-48
>             Project: Maven 2.x Groovy Integration
>          Issue Type: New Feature
>          Components: mojo support
>            Reporter: Raphaël Piéroni
>            Assignee: Jason Dillon
>             Fix For: 1.0-beta-3
>
>
> It will be help full to have META-INF/plexus/components.xml auto generated
> this should work for a groovy component implementing a java interface
> - when the component is compiled by maven (in src/main/groovy or src/main/java) 
> - or when the groovy component is dynamically compiled at runtime by groovy (in src/main/resources)
> this will enable to create cleaner groovy mojos

[jira] Created: (MOJO-917) Add the possibility to configure the LoadOrder

Add the possibility to configure the LoadOrder
----------------------------------------------

                 Key: MOJO-917
                 URL: http://jira.codehaus.org/browse/MOJO-917
             Project: Mojo
          Issue Type: New Feature
          Components: weblogic
            Reporter: Joris Geuens

Add the possibility to configure the LoadOrder. Default one is 100, but it can be configured when deploying
an application to a Weblogic server. This property is important if one application must startup before
another one when your server does a reboot.

--

-- 
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

[jira] Created: (MOJO-918) Refactor Antlr3PluginMojo to AntlrMojo to allow for the creation of a goal to generate test code

Refactor Antlr3PluginMojo to AntlrMojo to allow for the creation of a goal to generate test code
------------------------------------------------------------------------------------------------

                 Key: MOJO-918
                 URL: http://jira.codehaus.org/browse/MOJO-918
             Project: Mojo
          Issue Type: Improvement
            Reporter: Kenny MacDermid
            Priority: Minor

This is a patch to antlr3-maven-plugin.

Simple refactor to a base class for the 'antlr' mojo. This is required so I can use the same code to also
generate antlr test code.

Patch will be attached as soon as I get the issue number for this.

Kenny

--

-- 
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

[jira] Updated: (MOJO-918) Refactor Antlr3PluginMojo to AntlrMojo to allow for the creation of a goal to generate test code

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

Kenny MacDermid updated MOJO-918:
---------------------------------

    Attachment: MOJO-918-antlr3-maven-plugin.patch

Apply with -p1.

Kenny

> Refactor Antlr3PluginMojo to AntlrMojo to allow for the creation of a goal to generate test code
> ------------------------------------------------------------------------------------------------
>
>                 Key: MOJO-918
>                 URL: http://jira.codehaus.org/browse/MOJO-918
>             Project: Mojo
>          Issue Type: Improvement
>            Reporter: Kenny MacDermid
>            Priority: Minor
>         Attachments: MOJO-918-antlr3-maven-plugin.patch
>
>
> This is a patch to antlr3-maven-plugin.
> Simple refactor to a base class for the 'antlr' mojo. This is required so I can use the same code to also
generate antlr test code.
> Patch will be attached as soon as I get the issue number for this.
> Kenny

[jira] Assigned: (MOJO-918) Refactor Antlr3PluginMojo to AntlrMojo to allow for the creation of a goal to generate test code

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

David Holroyd reassigned MOJO-918:
----------------------------------

    Assignee: David Holroyd

> Refactor Antlr3PluginMojo to AntlrMojo to allow for the creation of a goal to generate test code
> ------------------------------------------------------------------------------------------------
>
>                 Key: MOJO-918
>                 URL: http://jira.codehaus.org/browse/MOJO-918
>             Project: Mojo
>          Issue Type: Improvement
>            Reporter: Kenny MacDermid
>            Assignee: David Holroyd
>            Priority: Minor
>         Attachments: MOJO-918-antlr3-maven-plugin.patch
>
>
> This is a patch to antlr3-maven-plugin.
> Simple refactor to a base class for the 'antlr' mojo. This is required so I can use the same code to also
generate antlr test code.
> Patch will be attached as soon as I get the issue number for this.
> Kenny

--

-- 
This message is automatically generated by JIRA.

VOTE: Move rat-maven-plugin to Apache RAT

Hi,

as you can see on

    http://wiki.apache.org/incubator/RatProposal

the RAT project aims to enter the Apache Incubator. At that point, it
seems to make more sense, if the rat-maven-plugin becomes a part of
the base project. More precisely, I would like to

- release the current projects state as 1.0-alpha-3 (no major changes
since the last
  release, apart from the upgrade of rat-lib to 0.5.1)
- add the rat-maven-plugin to the above proposal under "Initial Source"
- if the Incubator accepts the proposal: Move the current rat-maven-plugin from
  trunk/mojo to trunk/retired or a similar path. ("retired" was suggested in the
  discussion regarding the clover plugin, but that didn't seem to make it).
- Change the groupId, as soon as the plugin arrives at Apache.

Thanks,

Jochen

--

-- 
Look, that's why there's rules, understand? So that you think before
you break 'em.

    -- (Terry Pratchett, Thief of Time)

---------------------------------------------------------------------

Re: VOTE: Move rat-maven-plugin to Apache RAT

Jochen Wiedmann wrote:
> Hi,
> 
> as you can see on
> 
>     http://wiki.apache.org/incubator/RatProposal
> 
> the RAT project aims to enter the Apache Incubator. At that point, it
> seems to make more sense, if the rat-maven-plugin becomes a part of
> the base project. More precisely, I would like to
> 
> - release the current projects state as 1.0-alpha-3 (no major changes
> since the last
>   release, apart from the upgrade of rat-lib to 0.5.1)
> - add the rat-maven-plugin to the above proposal under "Initial Source"
> - if the Incubator accepts the proposal: Move the current rat-maven-plugin from
>   trunk/mojo to trunk/retired or a similar path. ("retired" was suggested in the
>   discussion regarding the clover plugin, but that didn't seem to make it).
> - Change the groupId, as soon as the plugin arrives at Apache.

+1

--
Trygve

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

    http://xircles.codehaus.org/manage_email

[jira] Created: (MOJO-919) No product launcher application generated on linux

No product launcher application generated on linux 
---------------------------------------------------

                 Key: MOJO-919
                 URL: http://jira.codehaus.org/browse/MOJO-919
             Project: Mojo
          Issue Type: Bug
          Components: pde
         Environment: Eclipse 3.3.1, Ubuntu Linux 7.10
            Reporter: Mark Howard

When following the simple_product
example(http://mojo.codehaus.org/pde-maven-plugin/examples/simple_product.html), mvn
install reports success and doesn't show any errors. It generates a zip file with lots of jars but no
launcher application or startup.jar. When I run the eclipse product export wizard directly, I do get an
eclipse application and startup.jar.

--

-- 
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

[jira] Created: (MOJO-920) testing is not integrated in pde plugin

testing is not integrated in pde plugin
---------------------------------------

                 Key: MOJO-920
                 URL: http://jira.codehaus.org/browse/MOJO-920
             Project: Mojo
          Issue Type: Bug
          Components: pde
         Environment: Eclipse 3.3.1, ubuntu linux 7.10
            Reporter: Mark Howard

The pde plugin does not handle unit testing gracefully. 
If I have unit tests in src/test/java, which require classes from src/main/java and dependencies in order
to run, mvn package should be able to compile these successfully and run the tests. This does not currently happen.

All the builds are handled by a headless pde build. When the tests are compiled, this fails due to missing
class files (pde places them in /target/pdeTemp/plugins/≤app>/ <at> dot/, instead of target/classes). If
you fudge the tests compile to look here too, then the tests themselves fail since the pde dependencies
aren't included on the classpath. 

Note that this could simply be a documentation issue, since dependency resolution in maven-pde-plugin is
currently undocumented. 

--

-- 
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

Re: VOTE: Move rat-maven-plugin to Apache RAT