You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brian E. Fox" <br...@reply.infinity.nu> on 2007/03/17 06:11:09 UTC
Mojo to test for MNG-1577 was [vote] MNG-1577 as the default behavior
I whipped up a mojo to test a build for cases where the resolved
dependency is different than what is set in the dependencyManagement
section. Use maven-dependency-plugin 2.0-alpha-3-SNAPSHOT (deployed to
snapshot repo) run as "mvn dependency:analyze" and it will display
mismatches. It currently skips snapshots but any released artifacts that
don't match will cause a problem.
-----Original Message-----
From: Brett Porter [mailto:brett@apache.org]
Sent: Friday, March 16, 2007 7:39 PM
To: Maven Developers List
Subject: Re: [vote] MNG-1577 as the default behavior
Mike,
Good plan. This is exactly what I was getting at - but I thought we
could already do this from the branch that the feature was
implemented on? That's what I was intending to use.
I'm obviously having trouble grokking the actual implications of this
- I was getting the clear impression this was going to break builds,
but it seems that may not be the case from the ensuing discussion. So
all I really want to do is play with it and see for myself at this
point. I have some time later today/tomorrow.
- Brett
On 17/03/2007, at 7:35 AM, Mike Perham wrote:
> The key question to me is: are existing 2.0.5 builds going to be
> better or worse after this upgrade? I would prefer to see less
> speculation and more bits. Put out a Maven 2.0.6 snapshot that people
> can try with their project and get reports from the people in this
> thread. If no one has problems, this discussion becomes a lot
> shorter. If they do have problems, at least we have specific examples
> to discuss.
>
> mike
>
> ---------------------------------------------------------------------
> 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: Mojo to test for MNG-1577 was [vote] MNG-1577 as the default behavior
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Going through my builds, I'm finding a surprising number of mismatches.
Looks like I've got some significant cleanup to do. Here's some sample
output:
[INFO] [dependency:analyze]
[INFO] Found Resolved Dependency / DependencyManagement mismatches:
[INFO] Dependency: oracle:adf-faces-api:jar
[INFO] DepMgt : 20.5-STCEA
[INFO] Resolved: 10.1.3.0.4
[INFO] Dependency: javax.servlet:servlet-api:jar
[INFO] DepMgt : 2.3
[INFO] Resolved: 2.4
[INFO] Dependency: junit:junit:jar
[INFO] DepMgt : 3.7
[INFO] Resolved: 3.8.1
[INFO] Dependency: oracle:adf-faces-impl:jar
[INFO] DepMgt : 20.5-STCEA
[INFO] Resolved: 10.1.3.0.4
[INFO] Dependency: commons-lang:commons-lang:jar
[INFO] DepMgt : 1.0
[INFO] Resolved: 2.3
[INFO] Dependency: commons-digester:commons-digester:jar
[INFO] DepMgt : 1.5
[INFO] Resolved: 1.7
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Saturday, March 17, 2007 1:14 AM
To: Maven Developers List
Subject: RE: Mojo to test for MNG-1577 was [vote] MNG-1577 as the
default behavior
I meant to say:
It currently skips snapshots but any released artifacts that
don't match will potentially cause a problem with a build with MNG-1577
applied.
I'm hoping that we can get this fixed up, release the analyze test and
make MNG-1577 the default behavior. We can not only describe it clearly
in the release notes, but now we'll have a tool to have people run in
2.0.5 to identify issues BEFORE they upgrade.
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Saturday, March 17, 2007 1:11 AM
To: Maven Developers List
Subject: Mojo to test for MNG-1577 was [vote] MNG-1577 as the default
behavior
I whipped up a mojo to test a build for cases where the resolved
dependency is different than what is set in the dependencyManagement
section. Use maven-dependency-plugin 2.0-alpha-3-SNAPSHOT (deployed to
snapshot repo) run as "mvn dependency:analyze" and it will display
mismatches. It currently skips snapshots but any released artifacts that
don't match will cause a problem.
-----Original Message-----
From: Brett Porter [mailto:brett@apache.org]
Sent: Friday, March 16, 2007 7:39 PM
To: Maven Developers List
Subject: Re: [vote] MNG-1577 as the default behavior
Mike,
Good plan. This is exactly what I was getting at - but I thought we
could already do this from the branch that the feature was
implemented on? That's what I was intending to use.
I'm obviously having trouble grokking the actual implications of this
- I was getting the clear impression this was going to break builds,
but it seems that may not be the case from the ensuing discussion. So
all I really want to do is play with it and see for myself at this
point. I have some time later today/tomorrow.
- Brett
On 17/03/2007, at 7:35 AM, Mike Perham wrote:
> The key question to me is: are existing 2.0.5 builds going to be
> better or worse after this upgrade? I would prefer to see less
> speculation and more bits. Put out a Maven 2.0.6 snapshot that people
> can try with their project and get reports from the people in this
> thread. If no one has problems, this discussion becomes a lot
> shorter. If they do have problems, at least we have specific examples
> to discuss.
>
> mike
>
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Mojo to test for MNG-1577 was [vote] MNG-1577 as the default behavior
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
I meant to say:
It currently skips snapshots but any released artifacts that
don't match will potentially cause a problem with a build with MNG-1577
applied.
I'm hoping that we can get this fixed up, release the analyze test and
make MNG-1577 the default behavior. We can not only describe it clearly
in the release notes, but now we'll have a tool to have people run in
2.0.5 to identify issues BEFORE they upgrade.
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Saturday, March 17, 2007 1:11 AM
To: Maven Developers List
Subject: Mojo to test for MNG-1577 was [vote] MNG-1577 as the default
behavior
I whipped up a mojo to test a build for cases where the resolved
dependency is different than what is set in the dependencyManagement
section. Use maven-dependency-plugin 2.0-alpha-3-SNAPSHOT (deployed to
snapshot repo) run as "mvn dependency:analyze" and it will display
mismatches. It currently skips snapshots but any released artifacts that
don't match will cause a problem.
-----Original Message-----
From: Brett Porter [mailto:brett@apache.org]
Sent: Friday, March 16, 2007 7:39 PM
To: Maven Developers List
Subject: Re: [vote] MNG-1577 as the default behavior
Mike,
Good plan. This is exactly what I was getting at - but I thought we
could already do this from the branch that the feature was
implemented on? That's what I was intending to use.
I'm obviously having trouble grokking the actual implications of this
- I was getting the clear impression this was going to break builds,
but it seems that may not be the case from the ensuing discussion. So
all I really want to do is play with it and see for myself at this
point. I have some time later today/tomorrow.
- Brett
On 17/03/2007, at 7:35 AM, Mike Perham wrote:
> The key question to me is: are existing 2.0.5 builds going to be
> better or worse after this upgrade? I would prefer to see less
> speculation and more bits. Put out a Maven 2.0.6 snapshot that people
> can try with their project and get reports from the people in this
> thread. If no one has problems, this discussion becomes a lot
> shorter. If they do have problems, at least we have specific examples
> to discuss.
>
> mike
>
> ---------------------------------------------------------------------
> 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