RE: Setting parameters doesn't work with 2.0.3 (was: [vote] Release Maven 2.0.3)
It's weird because it does seem to be exactly as you descibed, but not
as I observed with dependency-maven-plugin.
http://jira.codehaus.org/browse/MNG-2112
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Friday, February 24, 2006 12:41 PM
To: Maven Developers List
Subject: RE: Setting parameters doesn't work with 2.0.3 (was: [vote]
Release Maven 2.0.3)
Yes you're right. 1.1 is what I'm using internally. I was pretty sure
that 1.0 had the options. I'll make a test case.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Friday, February 24, 2006 11:34 AM
To: Maven Developers List
Subject: Re: Setting parameters doesn't work with 2.0.3 (was: [vote]
Release Maven 2.0.3)
I just checked out:
https://svn.codehaus.org/mojo/tags/dependency-maven-plugin-1.0
and peeked at both:
CopyDependenciesMojo.java
AbstractFromDependenciesMojo.java
and neither one declares an excludeTransitive parameter. This doesn't
seem to show up until the 1.1-SNAPSHOT code.
-john
Brian E. Fox wrote:
> It looks like all the ones I have in dependency-maven-plugin are like
> this:
>/**
> * If we should exclude transitive dependencies
> * @parameter expression="${excludeTransitive}"
> default-value="false"
> */
> private boolean excludeTransitive;
>
> The plugin is released, you should be able to test it by doing mvn
> dependency:copy-dependencies -DexcludeTransitive=true
>
> -Original Message-
> From: John Casey [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 24, 2006 10:54 AM
> To: Maven Developers List
> Subject: Re: Setting parameters doesn't work with 2.0.3 (was: [vote]
> Release Maven 2.0.3)
>
> 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:
>>
>>
>>> 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-
>>> 2
>>> 0
>>> 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]
>
>
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Setting parameters doesn't work with 2.0.3 (was: [vote] Release Maven 2.0.3)
Yes you're right. 1.1 is what I'm using internally. I was pretty sure
that 1.0 had the options. I'll make a test case.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Friday, February 24, 2006 11:34 AM
To: Maven Developers List
Subject: Re: Setting parameters doesn't work with 2.0.3 (was: [vote]
Release Maven 2.0.3)
I just checked out:
https://svn.codehaus.org/mojo/tags/dependency-maven-plugin-1.0
and peeked at both:
CopyDependenciesMojo.java
AbstractFromDependenciesMojo.java
and neither one declares an excludeTransitive parameter. This doesn't
seem to show up until the 1.1-SNAPSHOT code.
-john
Brian E. Fox wrote:
> It looks like all the ones I have in dependency-maven-plugin are like
> this:
>/**
> * If we should exclude transitive dependencies
> * @parameter expression="${excludeTransitive}"
> default-value="false"
> */
> private boolean excludeTransitive;
>
> The plugin is released, you should be able to test it by doing mvn
> dependency:copy-dependencies -DexcludeTransitive=true
>
> -Original Message-
> From: John Casey [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 24, 2006 10:54 AM
> To: Maven Developers List
> Subject: Re: Setting parameters doesn't work with 2.0.3 (was: [vote]
> Release Maven 2.0.3)
>
> 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:
>>
>>
>>> 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-
>>> 2
>>> 0
>>> 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]
>
>
-
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]
Re: Setting parameters doesn't work with 2.0.3 (was: [vote] Release Maven 2.0.3)
I just checked out:
https://svn.codehaus.org/mojo/tags/dependency-maven-plugin-1.0
and peeked at both:
CopyDependenciesMojo.java
AbstractFromDependenciesMojo.java
and neither one declares an excludeTransitive parameter. This doesn't
seem to show up until the 1.1-SNAPSHOT code.
-john
Brian E. Fox wrote:
It looks like all the ones I have in dependency-maven-plugin are like
this:
/**
* If we should exclude transitive dependencies
* @parameter expression="${excludeTransitive}"
default-value="false"
*/
private boolean excludeTransitive;
The plugin is released, you should be able to test it by doing mvn
dependency:copy-dependencies -DexcludeTransitive=true
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Friday, February 24, 2006 10:54 AM
To: Maven Developers List
Subject: Re: Setting parameters doesn't work with 2.0.3 (was: [vote]
Release Maven 2.0.3)
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:
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-2
0
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting parameters doesn't work with 2.0.3 (was: [vote] Release Maven 2.0.3)
Thanks, I'll take a look...
-john
Brian E. Fox wrote:
It looks like all the ones I have in dependency-maven-plugin are like
this:
/**
* If we should exclude transitive dependencies
* @parameter expression="${excludeTransitive}"
default-value="false"
*/
private boolean excludeTransitive;
The plugin is released, you should be able to test it by doing mvn
dependency:copy-dependencies -DexcludeTransitive=true
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Friday, February 24, 2006 10:54 AM
To: Maven Developers List
Subject: Re: Setting parameters doesn't work with 2.0.3 (was: [vote]
Release Maven 2.0.3)
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:
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-2
0
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting parameters doesn't work with 2.0.3 (was: [vote] Release Maven 2.0.3)
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:
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]
RE: Setting parameters doesn't work with 2.0.3 (was: [vote] Release Maven 2.0.3)
It looks like all the ones I have in dependency-maven-plugin are like
this:
/**
* If we should exclude transitive dependencies
* @parameter expression="${excludeTransitive}"
default-value="false"
*/
private boolean excludeTransitive;
The plugin is released, you should be able to test it by doing mvn
dependency:copy-dependencies -DexcludeTransitive=true
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Friday, February 24, 2006 10:54 AM
To: Maven Developers List
Subject: Re: Setting parameters doesn't work with 2.0.3 (was: [vote]
Release Maven 2.0.3)
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:
>
>
>> 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-2
>> 0
>> 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]
Re: Setting parameters doesn't work with 2.0.3 (was: [vote] Release Maven 2.0.3)
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:
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]
Re: Setting parameters doesn't work with 2.0.3 (was: [vote] Release Maven 2.0.3)
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:
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]
RE: Setting parameters doesn't work with 2.0.3 (was: [vote] Release Maven 2.0.3)
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:
> 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.
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
___
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
-
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]
Re: Setting parameters doesn't work with 2.0.3 (was: [vote] Release Maven 2.0.3)
On Fri, 24 Feb 2006, Reinhard Poetz wrote:
We'll have to look into that, but you're using a very old eclipse
plugin, since the downloadSources is false by default.
-- Kenney
> John Casey wrote:
>
>
> > 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-20060222.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.
>
> --
> Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
>
> {Software Engineering, Open Source, Web Applications, Apache Cocoon}
>
> web(log): http://www.poetz.cc
>
>
>
>
>
>
> ___
> Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
