BTW, I should mention that I just verified that a mojo I wrote with a
parameter specified as:
/**
* @parameter expression="${drefresh.verbose}" default-value="false"
*/
works in a 2.0.3-SNAPSHOT built on Tuesday night, around the same time
as the RC I referenced in the vote email.
Thanks,
John
Brian E. Fox wrote:
I think I'm seeing this same behavior. The cli does work to set parameters that activate profiles, but when I tested with my dependency plugin, none of the parameters seem to get injected into the mojo.
-----Original Message-----
From: Reinhard Poetz [mailto:[EMAIL PROTECTED]
Sent: Friday, February 24, 2006 6:52 AM
To: Maven Developers List
Subject: Setting parameters doesn't work with 2.0.3 (was: [vote] Release Maven
2.0.3)
John Casey wrote:
<snip/>
If you're interested, you can take the current release candidate for a
test drive. The RC tarball is at:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20
060222.031501.tar.gz
As I had some problems with Maven 2.0.2 I tried to use this RC. Unfortunatly
it's not possible to set configuration parameters anymore. I tried to call
mvn eclipse:eclipse -Declipse.downloadSources=false
which still leads to downloads. Printing the value of downloadSource from
within the execute() method to the console shows, that the value is always
'true'.
Switching back to 2.0.2 made the parameter setting work again.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
