[ 
http://jira.codehaus.org/browse/MGROOVY-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103155
 ] 

Mauro Talevi commented on MGROOVY-62:
-------------------------------------

Jason, 

I had to revert to using scriptpath - as using classpath broke the build 
strange and unexpected places - and depending on the JVM.

It built fine on Mac OS X, but failed on both Windows and Linux (JDK 1.5.0).   
Even when it failed, it did so in different places depending on the OS. 
The failure manifested itself in the failure of unit tests that were otherwise 
working and continued to work once reverted to using scriptpath.

Sorry to be so vague, but I've not been able to pinpoint the origin of the 
problem.   






> 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

Reply via email to