Thanks for the reply. I can't say I fully understand why it's needed from within maven.xml and not from the command line, unless settings passed from the command line are "wrapped up" and fed into maven's plugins.
I read through the wiki, and tried to get it to work with the following block, but it's still not set correctly. Do I need to use a specific jelly tag to execute it?
<goal name="all:install">
${pom.getPluginContext("maven-test-plugin").setVariable("maven.test.skip",
"true")}
<attainGoal name="multiproject:install-snapshot" />
</goal>
I don't fully understand the relationship between plugins, contexts, and properties either.
I don't think that you need any extra Jelly tags -- from what I've seen, when Maven evaluates maven.xml and sees a ${} it evaluates the contents as Jelly.
If you see the Jelly output to the console just as you wrote it, then it's not being processed correctly, there may be a syntax error or something. But it looks OK to me.
Maybe write a pregoal to test:test and output ${context.getVariable('maven.test.skip')} to see what the value is.
I've played around with this stuff a bit but I'm no expert, perhaps one of the Maven mavens can chime in?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
