You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jason Dillon (JIRA)" <ji...@codehaus.org> on 2005/11/23 07:37:06 UTC
[jira] Created: (MNG-1664) Write mojos w/Groovy
Write mojos w/Groovy
--------------------
Key: MNG-1664
URL: http://jira.codehaus.org/browse/MNG-1664
Project: Maven 2
Type: New Feature
Components: maven-plugin-tools
Versions: 2.0
Reporter: Jason Dillon
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1664) Write mojos w/Groovy
Posted by "Joerg Schaible (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1664?page=comments#action_51749 ]
Joerg Schaible commented on MNG-1664:
-------------------------------------
Hi Jason,
is this somehow related to the effort done by Éric Burghard, that announced something similar at the Coocoon list? Might be interesting for a joined work.
http://thread.gmane.org/gmane.text.xml.cocoon.devel/58463
- Jörg
> Write mojos w/Groovy
> --------------------
>
> Key: MNG-1664
> URL: http://jira.codehaus.org/browse/MNG-1664
> Project: Maven 2
> Type: New Feature
> Components: Plugin Creation Tools
> Versions: 2.0
> Reporter: Jason Dillon
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1664) Write mojos w/Groovy
Posted by "Jason Dillon (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1664?page=comments#action_51823 ]
Jason Dillon commented on MNG-1664:
-----------------------------------
To build/test these modules you need plexus, maven2 & groovy (probably from the trunk/head).
Then:
(cd plexus-groovy-factory && mvn install)
(cd maven-plugin-tools-groovy && mvn install)
cd groovytest-maven-plugin
mvn install -DupdateReleaseInfo=true
And finally to test:
mvn grrovytest:run
Which should say something like:
...
[INFO] [groovytest:run]
[INFO] Running...
[INFO] Base Dir: /Volumes/iDisk/Documents/maven2-groovy/groovytest-maven-plugin
[INFO] ----------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
...
> Write mojos w/Groovy
> --------------------
>
> Key: MNG-1664
> URL: http://jira.codehaus.org/browse/MNG-1664
> Project: Maven 2
> Type: New Feature
> Components: Plugin Creation Tools
> Versions: 2.0
> Reporter: Jason Dillon
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1664) Write mojos w/Groovy
Posted by "Jason Dillon (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1664?page=comments#action_51821 ]
Jason Dillon commented on MNG-1664:
-----------------------------------
So, Éric Burghard basically wrote a proxy from Java to a .groovy, where as the modules attached to this issue provide plexus-level support for binding Groovy objects a first-class components... and provide tools to scrape plugin.xml details directly from the .groovy source.
I however don't have an archetype... haven't figured out how to make one of those yet ;-)
> Write mojos w/Groovy
> --------------------
>
> Key: MNG-1664
> URL: http://jira.codehaus.org/browse/MNG-1664
> Project: Maven 2
> Type: New Feature
> Components: Plugin Creation Tools
> Versions: 2.0
> Reporter: Jason Dillon
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1664) Write mojos w/Groovy
Posted by "Jason Dillon (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1664?page=comments#action_51820 ]
Jason Dillon commented on MNG-1664:
-----------------------------------
This is the first I've heard of other similar works. I will take a peek :-)
> Write mojos w/Groovy
> --------------------
>
> Key: MNG-1664
> URL: http://jira.codehaus.org/browse/MNG-1664
> Project: Maven 2
> Type: New Feature
> Components: Plugin Creation Tools
> Versions: 2.0
> Reporter: Jason Dillon
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org