here is a blocker with mvn 2.0.8
>mvn -e --debug install
[DEBUG] xerces:xercesImpl:jar:2.8.1
[GC [DefNew: 3968K->0K(4032K), 0.0073060 secs] 34845K->31546K(262080K),
0.007430
0 secs]
[INFO] Reloading plugin container for:
org.apache.axis2:axis2-mar-maven-plugin.
The plugin artifact has changed.
[GC [DefNew: 3968K->0K(4032K), 0.0091788 secs] 35514K->32406K(262080K),
0.009302
3 secs]
[INFO] Reloading plugin container for:
org.apache.axis2:axis2-mar-maven-plugin.
The plugin artifact has changed.
[GC [DefNew: 3960K->0K(4032K), 0.0091827 secs] 36367K->33217K(262080K),
0.009303
7 secs]
[INFO] Reloading plugin container for:
org.apache.axis2:axis2-mar-maven-plugin.
The plugin artifact has changed.
[GC [DefNew: 3968K->0K(4032K), 0.0087908 secs] 37185K->34039K(262080K),
0.008909
8 secs]
[GC [DefNew: 3968K->0K(4032K), 0.0044061 secs] 38007K->34357K(262080K),
0.004521
0 secs]
[GC [DefNew: 3968K->0K(4032K), 0.0081681 secs] 38325K->35118K(262080K),
0.008291
0 secs]
[DEBUG] Unable to find the lifecycle component in the extension
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Com
ponent descriptor cannot be found in the component repository:
org.apache.maven.
artifact.handler.ArtifactHandlermar.
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:323)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:312)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:440)
at
org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusCon
tainer.java:390)
at
org.apache.maven.plugin.DefaultPluginManager.getPluginComponents(Defa
ultPluginManager.java:1353)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeH
andlers(DefaultLifecycleExecutor.java:1181)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(De
faultLifecycleExecutor.java:178)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:141)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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] Reloading plugin container for:
org.apache.axis2:axis2-mar-maven-plugin.
The plugin artifact has changed.
[GC [DefNew: 3968K->0K(4032K), 0.0068601 secs] 39086K->35756K(262080K),
0.006984
1 secs]
[DEBUG] Unable to find the lifecycle component in the extension
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Com
ponent descriptor cannot be found in the component repository:
org.apache.maven.
artifact.handler.ArtifactHandleraar.
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:323)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:312)
at
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai
ner.java:440)
at
org.codehaus.plexus.DefaultPlexusContainer.lookupMap(DefaultPlexusCon
tainer.java:390)
at
org.apache.maven.plugin.DefaultPluginManager.getPluginComponents(Defa
ultPluginManager.java:1353)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findArtifactTypeH
andlers(DefaultLifecycleExecutor.java:1181)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(De
faultLifecycleExecutor.java:178)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:141)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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] Building Apache Axis 2.0 - Parent
[INFO] task-segment: [install]
[INFO] ---------------------------------------------------------------------
---
[DEBUG] Skipping disabled repository apache-snapshots
[DEBUG] maven-site-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the
latest ve
rsion
org.apache.maven.plugins:maven-site-plugin:pom:LATEST
[DEBUG] Using defaults for missing POM
org.apache.maven.plugins:maven-site-plugi
n:pom:LATEST
[DEBUG] maven-site-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the
release v
ersion
org.apache.maven.plugins:maven-site-plugin:pom:RELEASE
//maven-site-plugin is installed in localRepository located at
//${USERPROFILE}\.m2\repository\org\apache\maven\plugins\maven-site-plugin\1
7
//in that folder I see the 1.7 specific files
maven-site-plugin-1.7.jar
maven-site-plugin-1.7.pom
//contents of maven-metadata.xml
<metadata>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<versioning>
<latest>1.7</latest>
<release>1.7</release>
<versions>
<version>1.7</version>
</versions>
<lastUpdated>20080114041911</lastUpdated>
</versioning>
</metadata>
//How come mvn 2.08 does'nt see my 1.7 maven-site-plugin and hunts for
LATEST RELEASE versions?
Thanks
M--
----- Original Message -----
From: "Brian E. Fox" <[EMAIL PROTECTED]>
To: "Maven Users List" <users@maven.apache.org>
Sent: Friday, March 07, 2008 8:28 PM
Subject: RE: [POLL] Why are you not able to use the most recent maven
release?
I've been working through that list and I grabbed some of the serious
artifact/repo issues as well as the highest voted issues from all groups
for the .10 release. The plan most likely will be to fix the regressions
and the most popular issues for 2.0.x but it is unlikely that all of
those will get fixed; the edge cases and improvement issues will
probably get bumped to 2.1 at some point. The 2.0.x branch should start
to become very refined in scope of issues being fixed once 2.1 is
closing in. Naturally people will still use 2.0.x for sometime so we'll
be supporting it, but splitting the effort will only slow down the
overall progress. (typical release management stuff yada yada)
The moral is to vote for the issues you most want fixed, and call out
loudly regressions and blockers to updating as those are the priority.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Paul Benedict
Sent: Friday, March 07, 2008 8:11 PM
To: Maven Users List
Subject: Re: [POLL] Why are you not able to use the most recent maven
release?
There are about 110 bugs slated in the "2.0.x" release category. As I
watch
2.0.9 and 2.0.10 develop, I notice that issues from "2.0.x" are not
touched.
My recommendation -- and hope -- is that someone could schedule a 2.0.11
and
2.0.12 based on 25 (swag) issues respectively from that big list. Those
are
the issues, it appears, that are long-standing and have been reported
early.
Paul
On Fri, Mar 7, 2008 at 6:22 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 7, 2008 at 2:44 PM, Brian E. Fox
<[EMAIL PROTECTED]>
> wrote:
>
> > If this is the case for you, please reply and state the version
you're
> > using and why (preferably referring to a Jira). We will use this
> > information to prioritize issues for 2.0.10 and beyond.
>
> Some time after 2.0.5, Maven seems to have lost the ability to deal
> with multiple repositories containing different versions of the same
> plugin.
>
> For example:
> * a 'third-party' repository with maven-whatever-plugin version 1.0
final
> * a 'sandbox' repository with maven-whatever-plugin version
2.0-alpha-1
>
> I think someone brought this up on the dev list recently as a problem
> when trying to test a staged plugin release-- it would be the same
> situation, with the latest release of the plugin in the 'central' repo
> and the staged one in some other repo.
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> 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]
