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
Affects Versions: 1.0-beta-1
Reporter: Mauro Talevi
Assignee: Jason Dillon
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
