You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Paul Gier <pg...@redhat.com> on 2007/10/22 23:35:57 UTC
Maven release plugin question
Hi All,
Does anyone know why the release plugin requires test scope dependency
resolution? I was looking into this issue:
http://jira.codehaus.org/browse/MRELEASE-285
And I found that if I remove this:
@requiresDependencyResolution test
The issue is resolved and all of the unit tests still pass. This issue is a
PITA for me because it means that any multi-module project with test scope
intermodule deps cannot use the release plugin.
Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Maven release plugin question
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Done.
-----Original Message-----
From: Paul Gier [mailto:pgier@redhat.com]
Sent: Tuesday, October 23, 2007 3:54 PM
To: Maven Developers List
Cc: Brian E. Fox
Subject: Re: Maven release plugin question
I tested the plugin without the requiresDependencyResolution parameter,
and it
was still able to find test scope snapshots. So I don't think it needs
that to
find snapshot versions.
I looked into the issue a bit more, and I was wrong about the cause of
the
problem. Maven tricked me! The issue is actually caused by a bug in
the maven
jar plugin (setting the wrong artifact type), and it occurs anytime you
have
test-jar inter-module dependencies and you try to run something like
"mvn
verify" without the test jar installed locally.
Can someone unlink the MNG-2277 issue dependency? It looks like this
problem
will go away with the next release of the jar plugin.
Thanks!
Brian E. Fox wrote:
> Maybe they want to check that no test dependencies are snapshots
either?
>
> -----Original Message-----
> From: Paul Gier [mailto:pgier@redhat.com]
> Sent: Monday, October 22, 2007 5:36 PM
> To: Maven Developers List
> Subject: Maven release plugin question
>
> Hi All,
> Does anyone know why the release plugin requires test scope dependency
> resolution? I was looking into this issue:
> http://jira.codehaus.org/browse/MRELEASE-285
>
> And I found that if I remove this:
> @requiresDependencyResolution test
>
> The issue is resolved and all of the unit tests still pass. This
issue
> is a
> PITA for me because it means that any multi-module project with test
> scope
> intermodule deps cannot use the release plugin.
>
> Thanks!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Maven release plugin question
Posted by Paul Gier <pg...@redhat.com>.
I tested the plugin without the requiresDependencyResolution parameter, and it
was still able to find test scope snapshots. So I don't think it needs that to
find snapshot versions.
I looked into the issue a bit more, and I was wrong about the cause of the
problem. Maven tricked me! The issue is actually caused by a bug in the maven
jar plugin (setting the wrong artifact type), and it occurs anytime you have
test-jar inter-module dependencies and you try to run something like "mvn
verify" without the test jar installed locally.
Can someone unlink the MNG-2277 issue dependency? It looks like this problem
will go away with the next release of the jar plugin.
Thanks!
Brian E. Fox wrote:
> Maybe they want to check that no test dependencies are snapshots either?
>
> -----Original Message-----
> From: Paul Gier [mailto:pgier@redhat.com]
> Sent: Monday, October 22, 2007 5:36 PM
> To: Maven Developers List
> Subject: Maven release plugin question
>
> Hi All,
> Does anyone know why the release plugin requires test scope dependency
> resolution? I was looking into this issue:
> http://jira.codehaus.org/browse/MRELEASE-285
>
> And I found that if I remove this:
> @requiresDependencyResolution test
>
> The issue is resolved and all of the unit tests still pass. This issue
> is a
> PITA for me because it means that any multi-module project with test
> scope
> intermodule deps cannot use the release plugin.
>
> Thanks!
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Maven release plugin question
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Maybe they want to check that no test dependencies are snapshots either?
-----Original Message-----
From: Paul Gier [mailto:pgier@redhat.com]
Sent: Monday, October 22, 2007 5:36 PM
To: Maven Developers List
Subject: Maven release plugin question
Hi All,
Does anyone know why the release plugin requires test scope dependency
resolution? I was looking into this issue:
http://jira.codehaus.org/browse/MRELEASE-285
And I found that if I remove this:
@requiresDependencyResolution test
The issue is resolved and all of the unit tests still pass. This issue
is a
PITA for me because it means that any multi-module project with test
scope
intermodule deps cannot use the release plugin.
Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org