[
http://jira.codehaus.org/browse/MGROOVY-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon closed MGROOVY-40.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.0-alpha-3
Groovy mojos now live happily with Java mojos during extraction w/o needing to
override the list of extractors to just include groovy.
> The groovy plugin.xml extractor parses out .java and .groovy mojos, which
> causes duplicate conflicts
> -----------------------------------------------------------------------------------------------------
>
> Key: MGROOVY-40
> URL: http://jira.codehaus.org/browse/MGROOVY-40
> Project: Maven 2.x Groovy Plugin
> Issue Type: Bug
> Components: mojo support
> Affects Versions: 1.0-alpha-3
> Reporter: Jason Dillon
> Assignee: Jason Dillon
> Fix For: 1.0-alpha-3
>
>
> The groovy plugin.xml descriptor extractor parses java and groovy sources, so
> that groovy mojos can properly pick up javadoc annotations from java base
> classes. But it also picks up mojos implemented in java too, which causes
> the maven-plugin-plugin to detect a 2 mojos (one extracted from the java
> extractor, and another from the groovy extractor).
> The groovy extractor should not include mojo descriptors for java sources,
> only groovy sources... yet it should still process both groovy and java
> sources for base-class annotation inclusion.
--
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
