You are viewing a plain text version of this content. The canonical link for it is here.
Posted to announce@maven.apache.org by Brian Fox <br...@apache.org> on 2007/03/28 14:23:38 UTC
[ANN] Maven Dependency Plugin 2.0-alpha-4 Released
The Maven team is pleased to announce the release of the Maven
Dependency Plugin, version 2.0-alpha-4
http://maven.apache.org/plugins/maven-dependency-plugin/
The dependency plugin provides the capability to manipulate artifacts.
It can copy and/or unpack artifacts from local or remote repositories
to a specified location.
Changes:
Fixed several issues related to the new analyze and analyze-dep-mgt
goals:
Release Notes - Maven 2.x Dependency Plugin - Version 2.0-alpha-4
** Bug
* [MDEP-72] - "IllegalArgumentException: Cannot accept visitor on
URL" when project contains a non-jar (e.g. zip) dependency
* [MDEP-73] - dependency:analyze in a packaging=pom project should
skip, not die or produce a redundant report
* [MDEP-74] - dependencies in test scope are not handled properly by analyze
* [MDEP-77] - dependency:analyze is reporting impossible results
* [MDEP-78] - analyze-dep-mgt has the labels reversed
* [MDEP-79] - index out of bounds exception on analyze against
maven-war-plugin
** Improvement
* [MDEP-76] - It would be nice to analyze dependencyManagement
exclusions as well as versions
- The Maven Team
Re: [ANN] Maven Dependency Plugin 2.0-alpha-4 Released
Posted by Barrie Treloar <ba...@gmail.com>.
On 4/2/07, Brian E. Fox <br...@reply.infinity.nu> wrote:
> Barrie, you'll probably need to clear that info from your maven-proxy.
Done, and sorted.
I figured it was something to do with my environment.
More incentive to get Archiva complete and working.
Thanks
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: [ANN] Maven Dependency Plugin 2.0-alpha-4 Released
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Barrie, you'll probably need to clear that info from your maven-proxy.
-----Original Message-----
From: Barrie Treloar [mailto:baerrach@gmail.com]
Sent: Monday, April 02, 2007 1:36 AM
To: Maven Users List
Subject: Re: [ANN] Maven Dependency Plugin 2.0-alpha-4 Released
On 4/2/07, Brett Porter <br...@gmail.com> wrote:
> Barrie:
> rm ~/.m2/repository/org/codehaus/mojo/maven-metadata.xml* should do
the trick.
Tried that already.
Deleted ~/.m2/repository/org/codehaus/mojo/
maven-metadata*
dependency-maven-plugin/
I have the added complication that mvn-proxy is between me and
central, but maven itself must be requesting
org.codehaus.mojo:dependency-maven-plugin:1.0 instead.
As you can see from the stack trace codehaus is checked first.
I'm not sure why any one else is not having the same problems...
(maybe mvnproxy related)
>mvn -X -cpu -U dependency:analyze
+ Error stacktraces are turned on.
Maven version: 2.0.4
[DEBUG] Building Maven user-level plugin registry from:
'USER\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from: 'C:\Program
Files\maven-2.0.4\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[DEBUG] Searching for parent-POM:
groupId:parentArtifactId::0.6-SNAPSHOT of project:
groupId:artifactId:jar:0.6-SNAPSHOT in relative path: ../
pom.xml
[DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml'
for project: groupId:artifactId:jar:0.6-SNAPSHOT
[DEBUG] Searching for parent-POM: bootstrap:bootstrap::14 of project:
groupId:parentArtifactId:pom:0.6-SNAPSHOT in relative path: .
./pom.xml
[DEBUG] Parent-POM: bootstrap:bootstrap::14 not found in relative
path: ../pom.xml
[DEBUG] Retrieving parent-POM: bootstrap:bootstrap::14 for project:
groupId:parentArtifactId:pom:0.6-SNAPSHOT from the repository.
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO] org.apache.maven.plugins: checking for updates from
internal_plugins
[INFO] org.apache.maven.plugins: checking for updates from central
[INFO] org.codehaus.mojo: checking for updates from internal_plugins
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'b28764024a091702daad3896cd31bad23659f129'; remote
= '19be53dfb67e6ed64b314a34221b67db12d3723f' - RETRYING
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'b28764024a091702daad3896cd31bad23659f129'; remote
= '19be53dfb67e6ed64b314a34221b67db12d3723f' - IGNORING
[INFO] org.codehaus.mojo: checking for updates from central
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'b28764024a091702daad3896cd31bad23659f129'; remote
= '19be53dfb67e6ed64b314a34221b67db12d3723f' - RETRYING
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'b28764024a091702daad3896cd31bad23659f129'; remote
= '19be53dfb67e6ed64b314a34221b67db12d3723f' - IGNORING
[INFO] artifact org.codehaus.mojo:dependency-maven-plugin: checking
for updates from internal_plugins
[INFO] artifact org.codehaus.mojo:dependency-maven-plugin: checking
for updates from central
[DEBUG] dependency-maven-plugin: resolved to version 1.0 from repository
central
[DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::5 for project:
org.codehaus.mojo:dependency-maven-plugin:maven-pl
ugin:1.0 from the repository.
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Required goal not found: dependency:analyze
[INFO]
------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.BuildFailureException: Required goal not found:
dependency:analyze
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(De
faultLifecycleExecutor.java:1533)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAgg
regationNeeds(DefaultLifecycleExecuto
r.java:381)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:135)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Mon Apr 02 15:02:01 CST 2007
[INFO] Final Memory: 1M/3M
[INFO]
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Dependency Plugin 2.0-alpha-4 Released
Posted by Barrie Treloar <ba...@gmail.com>.
On 4/2/07, Wayne Fay <wa...@gmail.com> wrote:
> Also, any particular reason you're still running 2.0.4 when 2.0.5 has
> been out for a while, and 2.0.6 was just released? ;-)
We have only just come to the end of our iteration (a suitable place
to reassess tooling)
and 2.0.5 didn't offer anything extra yet. But 2.0.6 dependency
management does, which is why I am trying to analyze our projects as I
can guarantee that we are not declaring dependencies that are required
to build a project but relying on transitive dependencies to pull them
in.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Dependency Plugin 2.0-alpha-4 Released
Posted by Wayne Fay <wa...@gmail.com>.
Also, any particular reason you're still running 2.0.4 when 2.0.5 has
been out for a while, and 2.0.6 was just released? ;-)
Wayne
On 4/1/07, Brett Porter <br...@gmail.com> wrote:
> It looks more like the metadata is out of date on internal_plugins.
>
> - Brett
>
> On 02/04/07, Barrie Treloar <ba...@gmail.com> wrote:
> > On 4/2/07, Brett Porter <br...@gmail.com> wrote:
> > > Barrie:
> > > rm ~/.m2/repository/org/codehaus/mojo/maven-metadata.xml* should do the trick.
> >
> > Tried that already.
> > Deleted ~/.m2/repository/org/codehaus/mojo/
> > maven-metadata*
> > dependency-maven-plugin/
> >
> > I have the added complication that mvn-proxy is between me and
> > central, but maven itself must be requesting
> > org.codehaus.mojo:dependency-maven-plugin:1.0 instead.
> >
> > As you can see from the stack trace codehaus is checked first.
> > I'm not sure why any one else is not having the same problems...
> > (maybe mvnproxy related)
> >
> > >mvn -X -cpu -U dependency:analyze
> > + Error stacktraces are turned on.
> > Maven version: 2.0.4
> > [DEBUG] Building Maven user-level plugin registry from:
> > 'USER\.m2\plugin-registry.xml'
> > [DEBUG] Building Maven global-level plugin registry from: 'C:\Program
> > Files\maven-2.0.4\conf\plugin-registry.xml'
> > [INFO] Scanning for projects...
> > [DEBUG] Searching for parent-POM:
> > groupId:parentArtifactId::0.6-SNAPSHOT of project:
> > groupId:artifactId:jar:0.6-SNAPSHOT in relative path: ../
> > pom.xml
> > [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml'
> > for project: groupId:artifactId:jar:0.6-SNAPSHOT
> > [DEBUG] Searching for parent-POM: bootstrap:bootstrap::14 of project:
> > groupId:parentArtifactId:pom:0.6-SNAPSHOT in relative path: .
> > ./pom.xml
> > [DEBUG] Parent-POM: bootstrap:bootstrap::14 not found in relative
> > path: ../pom.xml
> > [DEBUG] Retrieving parent-POM: bootstrap:bootstrap::14 for project:
> > groupId:parentArtifactId:pom:0.6-SNAPSHOT from the repository.
> > [INFO] Searching repository for plugin with prefix: 'dependency'.
> > [INFO] org.apache.maven.plugins: checking for updates from internal_plugins
> > [INFO] org.apache.maven.plugins: checking for updates from central
> > [INFO] org.codehaus.mojo: checking for updates from internal_plugins
> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> > 'b28764024a091702daad3896cd31bad23659f129'; remote
> > = '19be53dfb67e6ed64b314a34221b67db12d3723f' - RETRYING
> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> > 'b28764024a091702daad3896cd31bad23659f129'; remote
> > = '19be53dfb67e6ed64b314a34221b67db12d3723f' - IGNORING
> > [INFO] org.codehaus.mojo: checking for updates from central
> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> > 'b28764024a091702daad3896cd31bad23659f129'; remote
> > = '19be53dfb67e6ed64b314a34221b67db12d3723f' - RETRYING
> > [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> > 'b28764024a091702daad3896cd31bad23659f129'; remote
> > = '19be53dfb67e6ed64b314a34221b67db12d3723f' - IGNORING
> > [INFO] artifact org.codehaus.mojo:dependency-maven-plugin: checking
> > for updates from internal_plugins
> > [INFO] artifact org.codehaus.mojo:dependency-maven-plugin: checking
> > for updates from central
> > [DEBUG] dependency-maven-plugin: resolved to version 1.0 from repository central
> > [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::5 for project:
> > org.codehaus.mojo:dependency-maven-plugin:maven-pl
> > ugin:1.0 from the repository.
> > [INFO] ------------------------------------------------------------------------
> > [ERROR] BUILD FAILURE
> > [INFO] ------------------------------------------------------------------------
> > [INFO] Required goal not found: dependency:analyze
> > [INFO] ------------------------------------------------------------------------
> > [DEBUG] Trace
> > org.apache.maven.BuildFailureException: Required goal not found:
> > dependency:analyze
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1533)
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto
> > r.java:381)
> > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:324)
> > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> > at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> > [INFO] ------------------------------------------------------------------------
> > [INFO] Total time: < 1 second
> > [INFO] Finished at: Mon Apr 02 15:02:01 CST 2007
> > [INFO] Final Memory: 1M/3M
> > [INFO] ------------------------------------------------------------------------
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Dependency Plugin 2.0-alpha-4 Released
Posted by Brett Porter <br...@gmail.com>.
It looks more like the metadata is out of date on internal_plugins.
- Brett
On 02/04/07, Barrie Treloar <ba...@gmail.com> wrote:
> On 4/2/07, Brett Porter <br...@gmail.com> wrote:
> > Barrie:
> > rm ~/.m2/repository/org/codehaus/mojo/maven-metadata.xml* should do the trick.
>
> Tried that already.
> Deleted ~/.m2/repository/org/codehaus/mojo/
> maven-metadata*
> dependency-maven-plugin/
>
> I have the added complication that mvn-proxy is between me and
> central, but maven itself must be requesting
> org.codehaus.mojo:dependency-maven-plugin:1.0 instead.
>
> As you can see from the stack trace codehaus is checked first.
> I'm not sure why any one else is not having the same problems...
> (maybe mvnproxy related)
>
> >mvn -X -cpu -U dependency:analyze
> + Error stacktraces are turned on.
> Maven version: 2.0.4
> [DEBUG] Building Maven user-level plugin registry from:
> 'USER\.m2\plugin-registry.xml'
> [DEBUG] Building Maven global-level plugin registry from: 'C:\Program
> Files\maven-2.0.4\conf\plugin-registry.xml'
> [INFO] Scanning for projects...
> [DEBUG] Searching for parent-POM:
> groupId:parentArtifactId::0.6-SNAPSHOT of project:
> groupId:artifactId:jar:0.6-SNAPSHOT in relative path: ../
> pom.xml
> [DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml'
> for project: groupId:artifactId:jar:0.6-SNAPSHOT
> [DEBUG] Searching for parent-POM: bootstrap:bootstrap::14 of project:
> groupId:parentArtifactId:pom:0.6-SNAPSHOT in relative path: .
> ./pom.xml
> [DEBUG] Parent-POM: bootstrap:bootstrap::14 not found in relative
> path: ../pom.xml
> [DEBUG] Retrieving parent-POM: bootstrap:bootstrap::14 for project:
> groupId:parentArtifactId:pom:0.6-SNAPSHOT from the repository.
> [INFO] Searching repository for plugin with prefix: 'dependency'.
> [INFO] org.apache.maven.plugins: checking for updates from internal_plugins
> [INFO] org.apache.maven.plugins: checking for updates from central
> [INFO] org.codehaus.mojo: checking for updates from internal_plugins
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> 'b28764024a091702daad3896cd31bad23659f129'; remote
> = '19be53dfb67e6ed64b314a34221b67db12d3723f' - RETRYING
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> 'b28764024a091702daad3896cd31bad23659f129'; remote
> = '19be53dfb67e6ed64b314a34221b67db12d3723f' - IGNORING
> [INFO] org.codehaus.mojo: checking for updates from central
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> 'b28764024a091702daad3896cd31bad23659f129'; remote
> = '19be53dfb67e6ed64b314a34221b67db12d3723f' - RETRYING
> [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
> 'b28764024a091702daad3896cd31bad23659f129'; remote
> = '19be53dfb67e6ed64b314a34221b67db12d3723f' - IGNORING
> [INFO] artifact org.codehaus.mojo:dependency-maven-plugin: checking
> for updates from internal_plugins
> [INFO] artifact org.codehaus.mojo:dependency-maven-plugin: checking
> for updates from central
> [DEBUG] dependency-maven-plugin: resolved to version 1.0 from repository central
> [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::5 for project:
> org.codehaus.mojo:dependency-maven-plugin:maven-pl
> ugin:1.0 from the repository.
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Required goal not found: dependency:analyze
> [INFO] ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.BuildFailureException: Required goal not found:
> dependency:analyze
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1533)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto
> r.java:381)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: < 1 second
> [INFO] Finished at: Mon Apr 02 15:02:01 CST 2007
> [INFO] Final Memory: 1M/3M
> [INFO] ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Dependency Plugin 2.0-alpha-4 Released
Posted by Barrie Treloar <ba...@gmail.com>.
On 4/2/07, Brett Porter <br...@gmail.com> wrote:
> Barrie:
> rm ~/.m2/repository/org/codehaus/mojo/maven-metadata.xml* should do the trick.
Tried that already.
Deleted ~/.m2/repository/org/codehaus/mojo/
maven-metadata*
dependency-maven-plugin/
I have the added complication that mvn-proxy is between me and
central, but maven itself must be requesting
org.codehaus.mojo:dependency-maven-plugin:1.0 instead.
As you can see from the stack trace codehaus is checked first.
I'm not sure why any one else is not having the same problems...
(maybe mvnproxy related)
>mvn -X -cpu -U dependency:analyze
+ Error stacktraces are turned on.
Maven version: 2.0.4
[DEBUG] Building Maven user-level plugin registry from:
'USER\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from: 'C:\Program
Files\maven-2.0.4\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[DEBUG] Searching for parent-POM:
groupId:parentArtifactId::0.6-SNAPSHOT of project:
groupId:artifactId:jar:0.6-SNAPSHOT in relative path: ../
pom.xml
[DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml'
for project: groupId:artifactId:jar:0.6-SNAPSHOT
[DEBUG] Searching for parent-POM: bootstrap:bootstrap::14 of project:
groupId:parentArtifactId:pom:0.6-SNAPSHOT in relative path: .
./pom.xml
[DEBUG] Parent-POM: bootstrap:bootstrap::14 not found in relative
path: ../pom.xml
[DEBUG] Retrieving parent-POM: bootstrap:bootstrap::14 for project:
groupId:parentArtifactId:pom:0.6-SNAPSHOT from the repository.
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO] org.apache.maven.plugins: checking for updates from internal_plugins
[INFO] org.apache.maven.plugins: checking for updates from central
[INFO] org.codehaus.mojo: checking for updates from internal_plugins
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'b28764024a091702daad3896cd31bad23659f129'; remote
= '19be53dfb67e6ed64b314a34221b67db12d3723f' - RETRYING
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'b28764024a091702daad3896cd31bad23659f129'; remote
= '19be53dfb67e6ed64b314a34221b67db12d3723f' - IGNORING
[INFO] org.codehaus.mojo: checking for updates from central
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'b28764024a091702daad3896cd31bad23659f129'; remote
= '19be53dfb67e6ed64b314a34221b67db12d3723f' - RETRYING
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'b28764024a091702daad3896cd31bad23659f129'; remote
= '19be53dfb67e6ed64b314a34221b67db12d3723f' - IGNORING
[INFO] artifact org.codehaus.mojo:dependency-maven-plugin: checking
for updates from internal_plugins
[INFO] artifact org.codehaus.mojo:dependency-maven-plugin: checking
for updates from central
[DEBUG] dependency-maven-plugin: resolved to version 1.0 from repository central
[DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::5 for project:
org.codehaus.mojo:dependency-maven-plugin:maven-pl
ugin:1.0 from the repository.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Required goal not found: dependency:analyze
[INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.BuildFailureException: Required goal not found:
dependency:analyze
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1533)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecuto
r.java:381)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:135)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Mon Apr 02 15:02:01 CST 2007
[INFO] Final Memory: 1M/3M
[INFO] ------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Dependency Plugin 2.0-alpha-4 Released
Posted by Brett Porter <br...@gmail.com>.
Barrie:
rm ~/.m2/repository/org/codehaus/mojo/maven-metadata.xml* should do the trick.
- Brett
On 02/04/07, Barrie Treloar <ba...@gmail.com> wrote:
> On 4/2/07, Wayne Fay <wa...@gmail.com> wrote:
> > Try the fully qualified plugin name ie:
> > -Dplugin=org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4
>
> This works, and pulls down the correct version from central.
>
> However, now that the new version is available, it is still resolving
> to org.codehaus.mojo:dependency-maven-plugin:1.0
>
> I am running
> mvn dependency:analyze
>
> How do I run the same command but fully qualifying the plugin?
>
> Next question would be to work out why Maven is resolving codehaus
> first. If I recall correctly the expansion of <plugin>:<goal> first
> checks codehaus with <plugin>-maven-plugin and then checks central
> with maven-<plugin>-plugin.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Dependency Plugin 2.0-alpha-4 Released
Posted by Barrie Treloar <ba...@gmail.com>.
On 4/2/07, Wayne Fay <wa...@gmail.com> wrote:
> Try the fully qualified plugin name ie:
> -Dplugin=org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4
This works, and pulls down the correct version from central.
However, now that the new version is available, it is still resolving
to org.codehaus.mojo:dependency-maven-plugin:1.0
I am running
mvn dependency:analyze
How do I run the same command but fully qualifying the plugin?
Next question would be to work out why Maven is resolving codehaus
first. If I recall correctly the expansion of <plugin>:<goal> first
checks codehaus with <plugin>-maven-plugin and then checks central
with maven-<plugin>-plugin.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Dependency Plugin 2.0-alpha-4 Released
Posted by Mykel Alvis <my...@weirdness.com>.
Never mind. Answered that myself. My silly parent pom has a version
identifier in it.... :(
On 4/14/07, Mykel Alvis <my...@weirdness.com> wrote:
>
> This doesn't work for me. I've deleted the cache in proximity, which I
> assumed was the initial problem and when I do
>
> mvn dependency:analyze -Dplugin=
> org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4
>
> it still resolves to 2.0-alpha-1. What am I doing wrong here?
>
>
> On 4/1/07, Wayne Fay <waynefay@gmail.com > wrote:
> >
> > Try the fully qualified plugin name ie:
> > -Dplugin=org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4
> >
> > Wayne
> >
> > On 4/1/07, Barrie Treloar <ba...@gmail.com> wrote:
> > > On 3/28/07, Brian Fox <br...@apache.org> wrote:
> > > > The Maven team is pleased to announce the release of the Maven
> > > > Dependency Plugin, version 2.0-alpha-4
> > >
> > > For some reason mvn is resolving to the codehaus version and not the
> > > apache version.
> > >
> > > I thought there was someway to fully qualify the path of a plugin when
> > > invoking them, but I can't find any documentation about how to do so.
> > >
> > > Any clues on how to resolve this? I've tried deleting the repository
> > > copies and metadata but that didn't work either.
> > >
> > > >mvn --version
> > > Maven version: 2.0.5
> > >
> > > >mvn help:describe -Dplugin=dependency
> > > [INFO] Scanning for projects...
> > > [INFO] Searching repository for plugin with prefix: 'help'.
> > > [INFO]
> > ----------------------------------------------------------------------------
> > > [INFO] Building Client Application
> > > [INFO] task-segment: [help:describe] (aggregator-style)
> > > [INFO]
> > ----------------------------------------------------------------------------
> > > [INFO] [help:describe]
> > > [INFO] Plugin: 'org.codehaus.mojo:dependency-maven-plugin:1.0'
> > > -----------------------------------------------
> > > Group Id: org.codehaus.mojo
> > > Artifact Id: dependency-maven-plugin
> > > Version: 1.0
> > > Goal Prefix: dependency
> > > Description:
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> I'm just an unfrozen caveman software developer. I don't understand your
> strange, "modern" ways.
--
I'm just an unfrozen caveman software developer. I don't understand your
strange, "modern" ways.
Re: [ANN] Maven Dependency Plugin 2.0-alpha-4 Released
Posted by Mykel Alvis <my...@weirdness.com>.
This doesn't work for me. I've deleted the cache in proximity, which I
assumed was the initial problem and when I do
mvn dependency:analyze -Dplugin=
org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4
it still resolves to 2.0-alpha-1. What am I doing wrong here?
On 4/1/07, Wayne Fay <wa...@gmail.com> wrote:
>
> Try the fully qualified plugin name ie:
> -Dplugin=org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4
>
> Wayne
>
> On 4/1/07, Barrie Treloar <ba...@gmail.com> wrote:
> > On 3/28/07, Brian Fox <br...@apache.org> wrote:
> > > The Maven team is pleased to announce the release of the Maven
> > > Dependency Plugin, version 2.0-alpha-4
> >
> > For some reason mvn is resolving to the codehaus version and not the
> > apache version.
> >
> > I thought there was someway to fully qualify the path of a plugin when
> > invoking them, but I can't find any documentation about how to do so.
> >
> > Any clues on how to resolve this? I've tried deleting the repository
> > copies and metadata but that didn't work either.
> >
> > >mvn --version
> > Maven version: 2.0.5
> >
> > >mvn help:describe -Dplugin=dependency
> > [INFO] Scanning for projects...
> > [INFO] Searching repository for plugin with prefix: 'help'.
> > [INFO]
> ----------------------------------------------------------------------------
> > [INFO] Building Client Application
> > [INFO] task-segment: [help:describe] (aggregator-style)
> > [INFO]
> ----------------------------------------------------------------------------
> > [INFO] [help:describe]
> > [INFO] Plugin: 'org.codehaus.mojo:dependency-maven-plugin:1.0'
> > -----------------------------------------------
> > Group Id: org.codehaus.mojo
> > Artifact Id: dependency-maven-plugin
> > Version: 1.0
> > Goal Prefix: dependency
> > Description:
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
I'm just an unfrozen caveman software developer. I don't understand your
strange, "modern" ways.
Re: [ANN] Maven Dependency Plugin 2.0-alpha-4 Released
Posted by Wayne Fay <wa...@gmail.com>.
Try the fully qualified plugin name ie:
-Dplugin=org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4
Wayne
On 4/1/07, Barrie Treloar <ba...@gmail.com> wrote:
> On 3/28/07, Brian Fox <br...@apache.org> wrote:
> > The Maven team is pleased to announce the release of the Maven
> > Dependency Plugin, version 2.0-alpha-4
>
> For some reason mvn is resolving to the codehaus version and not the
> apache version.
>
> I thought there was someway to fully qualify the path of a plugin when
> invoking them, but I can't find any documentation about how to do so.
>
> Any clues on how to resolve this? I've tried deleting the repository
> copies and metadata but that didn't work either.
>
> >mvn --version
> Maven version: 2.0.5
>
> >mvn help:describe -Dplugin=dependency
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'help'.
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Client Application
> [INFO] task-segment: [help:describe] (aggregator-style)
> [INFO] ----------------------------------------------------------------------------
> [INFO] [help:describe]
> [INFO] Plugin: 'org.codehaus.mojo:dependency-maven-plugin:1.0'
> -----------------------------------------------
> Group Id: org.codehaus.mojo
> Artifact Id: dependency-maven-plugin
> Version: 1.0
> Goal Prefix: dependency
> Description:
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ANN] Maven Dependency Plugin 2.0-alpha-4 Released
Posted by Barrie Treloar <ba...@gmail.com>.
On 3/28/07, Brian Fox <br...@apache.org> wrote:
> The Maven team is pleased to announce the release of the Maven
> Dependency Plugin, version 2.0-alpha-4
For some reason mvn is resolving to the codehaus version and not the
apache version.
I thought there was someway to fully qualify the path of a plugin when
invoking them, but I can't find any documentation about how to do so.
Any clues on how to resolve this? I've tried deleting the repository
copies and metadata but that didn't work either.
>mvn --version
Maven version: 2.0.5
>mvn help:describe -Dplugin=dependency
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'help'.
[INFO] ----------------------------------------------------------------------------
[INFO] Building Client Application
[INFO] task-segment: [help:describe] (aggregator-style)
[INFO] ----------------------------------------------------------------------------
[INFO] [help:describe]
[INFO] Plugin: 'org.codehaus.mojo:dependency-maven-plugin:1.0'
-----------------------------------------------
Group Id: org.codehaus.mojo
Artifact Id: dependency-maven-plugin
Version: 1.0
Goal Prefix: dependency
Description:
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org