[
http://jira.codehaus.org/browse/MGROOVY-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91089
]
Jason Dillon commented on MGROOVY-1:
------------------------------------
Ya, the annotations would only really be needed when compiling the groovy mojo
plugin... though I'm not sure how to get those annotations at compile time. I
was going to compile the *.groovy into *.class files, then inspect the classes
for mojo impls and then extract annotations to generate the plugin.xml. But,
in order for that to work, the .class files need to be Java 5... so I'd have to
retrotranslate them afterwards to strip off the extra bits and make them
compatible with Java 1.4. Then you would have to build the plugin with Java 5,
but could still run with Java 1.4.
Its a bit messy IMO... wish Maven would just require Java 5 already and then it
would not be such a big deal at all ;-)
> Support mojo plugin.xml generation for Groovy mojos
> ---------------------------------------------------
>
> Key: MGROOVY-1
> URL: http://jira.codehaus.org/browse/MGROOVY-1
> Project: Maven 2.x Groovy Plugin
> Issue Type: New Feature
> Reporter: Jason Dillon
> Assigned To: Jason Dillon
> Fix For: 1.0-alpha-3
>
>
> Right now there isn't really a good way to generate a plugin.xml for a Mojo
> implemented in Groovy.
> There is the {{javalike-maven-plugin-tools}} module which kinda works, though
> requires some icky ";" tokens to get qDox to properly parse out javadocs for
> parameters. I'm not sure that this module handles annotations on
> super-classes either.
> I've hacked up an extractor.groovy a while ago (MNG-1664) which uses regex,
> but that doesn't handle super-classes either.
> Really need a nice way to parse regular groovy (w/o needing ";') to generate
> a plugin.xml.
--
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
