[
http://jira.codehaus.org/browse/MGROOVY-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103213
]
Mauro Talevi commented on MGROOVY-62:
-------------------------------------
Will do - but honestly not trivial as I get different behaviours on different
OS and (more worrying) as different build users.
I have been able to work through some failures by:
- Upgrading from mvn 2.0.6 to 2.0.7
- Upgrading to cglib 2.1_3
But failures do remain.
One thing I would suggest is to provide:
1 - A detailed log within the plugin of the classpath elements used.
2 - A possibly more unified treatment of classpath and scriptpath elements - I
would not expect this wildly different behaviour when using one or other.
Maybe reconducting one case to the other?
Not sure how the classpath is constructed as it extends another mojo
(plugin-support).
> Better scriptpath support for multi-module projects
> ---------------------------------------------------
>
> Key: MGROOVY-62
> URL: http://jira.codehaus.org/browse/MGROOVY-62
> Project: Maven 2.x Groovy Plugin
> Issue Type: Improvement
> Components: execute
> Affects Versions: 1.0-beta-1
> Reporter: Mauro Talevi
> Assignee: Jason Dillon
> Priority: Minor
>
> Currently, scriptpath works well with single-module projects, eg if your
> scripts are in src/groovy dir:
> <scriptpath>
> <element>${pom.basedir}/src/groovy</element>
> </scriptpath>
> If you have a multi-module project, it gets a bit messy, ie you have to
> declare the path the groovy dir from all the modules, eg
> <scriptpath>
> <element>${pom.basedir}/src/groovy</element>
> <element>${pom.basedir}/../src/groovy</element>
> </scriptpath>
> which is kind of pointless, there being only one groovy dir.
> Not sure what the best way to approach this - or what best-practice should be
> suggested.
> One way could be to package the groovy scripts in a separate module (and
> create a corresponding artifact) and then to add allow the script path to be
> built using the dependency.
--
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
