You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason Dillon (JIRA)" <ji...@codehaus.org> on 2007/02/25 20:41:15 UTC

[jira] Commented: (MNG-1664) Write mojos w/Groovy

    [ http://jira.codehaus.org/browse/MNG-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88500 ] 

Jason Dillon commented on MNG-1664:
-----------------------------------

I'm going to revisit this again... see whats usable here from my work, as well as whats usable in the current groovy plexus factory and the groovy-maven-tools at the Mojo project.

> Write mojos w/Groovy
> --------------------
>
>                 Key: MNG-1664
>                 URL: http://jira.codehaus.org/browse/MNG-1664
>             Project: Maven 2
>          Issue Type: New Feature
>          Components: Plugin Creation Tools
>    Affects Versions: 2.0
>            Reporter: Jason Dillon
>             Fix For: 2.2.x
>
>         Attachments: maven2-groovy-mojo-support.tar.gz
>
>
> Attached is an archive containing 3 modules:
>  * plexus-groovy-factory
>  * maven-plugin-tools-groovy
>  * groovytest-maven-plugin
> plexus-groovy-factory is a plexus component factory, which allows Groovy objects to be used as components inside of Plexus.  I started with the existing module of the same name in the plexus project, but most of it changed, so I just included the entire module instead of providing a patch.  Tests included.
> maven-plugin-tools-groovy provides the ability to extract MojoDescriptors from one or more .groovy sources.  This is based off of the beanshell extractor.sh... its kinda hacky, but functions _well enough_ for now.  groovytest-maven-plugin is used to test.
> groovytest-maven-plugin is just a simple maven plugin that uses the new groovy script support.  It shows that a .groovy can use other .groovy sources inside of the plugin, and shows that the descriptor extractor functions.  Its basically useful for integration testing.
>  * * *
> Someone should check & update the version details for the parent pom of these modules.  I just used whatever I had on my local system to get it working.
> This plugin depends on Groovy 1.0 JSR 05, but 04 will sorta work, but will not function with included classes in the same jar.  Since 04 was just releases yesterday, these modules depend on 05 SNAPSHOT, which should be available on the codehaus ci repo.  When 1.0 is released this dep should be updated to that version.

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