Hmm, I can't even replicate this scenario any more...it makes me wonder
whether I had a typo in the mojo the last time I saw it...
Anyway, I cannot verify this cli behavior...can you post a test case? I
definitely want to make sure we don't put something like this into the
next release.
Thanks,
John
John Casey wrote:
Can you verify something for me? Does your mojo's parameter specify
something like:
/**
* @parameter default-value="something" expression="${something}"
*/
(Note the ordering of default-value and expression.)
I noticed something awhile ago where the expression was being hidden
from the qdox parser when specified as the last attribute in that line,
but I thought it had always been there. It's even filed in jira, but I
thought it could wait (again, b/c I assumed it had always been there).
Can you verify that this is the case, and that for this mojo,
command-line specification of this parameter works in 2.0.2?
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
