<define:tag name="export-property">
<j:set var="${property}" value="${pom.getPluginContext(context).getVariable(property)}" scope="parent"/>
</define:tag>
Just tested this and it appears to work!
<eclipse-plugin:export-property property="maven.test.dest" context="maven-test-plugin"/>
<echo>maven.test.dest = ${maven.test.dest}</echo>
God I love this!
jeff
[EMAIL PROTECTED] wrote:
Jeffrey Bonevich <[EMAIL PROTECTED]> wrote on 19/10/2003 09:32:17 AM:
Am I correct in thinking that the scope of individual plugin properties does not extend to preGoals and postGoals? Did some more testing (e.g. with the maven-jar-plugin and trying to get at 'maven.jar.excludes') and
this seems to be the case.
jeff
Correct, the variables are stored in the plugin's context. Currently to access a plugin's variables you must use some jelly code:
${pom.getPluginContext('maven-test-plugin').getVariable('maven.test.dest')}
We really should make this a tag. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
