Maven ${} resolution of inlined Groovy scripts is causing problems with GStrings
--------------------------------------------------------------------------------
Key: MGROOVY-32
URL: http://jira.codehaus.org/browse/MGROOVY-32
Project: Maven 2.x Groovy Plugin
Issue Type: Improvement
Components: execute
Affects Versions: 1.0-alpha-2, 1.0-alpha-1
Reporter: Jason Dillon
Assignee: Jason Dillon
Fix For: 1.0-alpha-3
Maven by default will resolve ${foo} (based on something... not sure what, but
some set of properties) in <configuration> elements. This is causing problems
using Groovy GStrings, which could look like ${foo} or just $foo.
Need to see if we can somehow get Maven to not perform ${} subst for one
configuration element (that would be configuration/source/body) and still
perform the default for other configuration elements.
The work around is to not use GStrings in inline code source, or to use an
external code source (file,url).
--
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
