Jan,
I tested this out and the order is being searched correctly. First my
plugin groups, then apache, then codehaus. The first match for a prefix
found is used. See MNG-2296 for more info.

--Brian


-----Original Message-----
From: Brian E. Fox [mailto:[EMAIL PROTECTED] 
Sent: Saturday, October 20, 2007 12:48 PM
To: Maven Developers List
Subject: RE: Plugin Resolution Bug?

Go ahead and open one, then let me know what it is. I did the code for
2.0.7 so I'll check it out before we do 2.0.8

-----Original Message-----
From: Jan Nielsen [mailto:[EMAIL PROTECTED] 
Sent: Saturday, October 20, 2007 11:26 AM
To: Maven Developers List
Subject: Re: Plugin Resolution Bug?

Thanks, Brian. That was my understanding. I'll open a bug on it, as it
appears from the 2.0.7 debug information in my original post that it
is not behaving as such - you agree?

-Jan

On 10/20/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> In 2.0.7, it should first look in pluginGroups you have defined, then
> maven, then codehaus.
>
> -----Original Message-----
> From: Jan Nielsen [mailto:[EMAIL PROTECTED]
> Sent: Saturday, October 20, 2007 10:44 AM
> To: Maven Developers List
> Subject: Re: Plugin Resolution Bug?
>
> Yes; thanks, Wayne - Marco from Triemax mentioned that this
> fully-qualified form should work, and it does:
>
>   mvn triemax:jalopy-maven:format
>
> So, that's my current work-around. But really, despite the unfortunate
> name clash on "jalopy" it seems to me that this should work with a
> properly defined plug-in groups identifier:
>
>   mvn jalopy:format
>
> Question is: is plug-in resolution broken? If so, I'll be happy to
> open a bug on it.
>
>
> Thanks,
>
> -Jan
>
> On 10/19/07, Wayne Fay <[EMAIL PROTECTED]> wrote:
> > Try using the "full name" of the plug-in, something along these
lines:
> > mvn clean triemax:jalopy-maven-plugin:1.0:format
> >
> > If you couldn't tell, that's groupId:artifactId:version:mojo.
> >
> > Wayne
> >
> > On 10/17/07, Jan Nielsen <[EMAIL PROTECTED]> wrote:
> > > I have configured our local repository as a single repository,
> > > mirroring all repository requests, and I have configured the
plugin
> > > groups to use "triemax":
> > >
> > >  <pluginGroups>
> > >    <pluginGroup>triemax</pluginGroup>
> > >  </pluginGroups>
> > >  <mirrors>
> > >    <mirror>
> > >      <id>internal-repository</id>
> > >      <name>Maven Repository Manager</name>
> > >      <url>http://it.access.dev/repository</url>
> > >      <mirrorOf>*</mirrorOf>
> > >    </mirror>
> > >  </mirrors>
> > >
> > > However, when I run:
> > >
> > >    mvn clean jalopy:format -X
> > >
> > > the "org.codehaus.mojo" group ID is used to resolve the plugin
> instead
> > > of "triemax". I have changed the name of the org.codehaus.mojo
> Jalopy
> > > instance which therefore fails to resolve as seen below. But how
do
> I
> > > get Maven to actually use the configured "triemax" as the group
> > > identifier for this plugin???
> > >
> > > It appears that I might be able to use the plugin-registry.xml to
> > > over-ride this (broken?) behavior if I knew how to use it...the
> Maven
> > > web page does not contain a schema:
> > >
> > >
>
http://maven.apache.org/guides/introduction/introduction-to-plugin-regis
> try.html
> > >
> > > Any ideas on how to work-around this issue, or fix it?
> > >
> > >
> > > Many thanks,
> > >
> > > -Jan
> > >
> > >
> > >
> > > + Error stacktraces are turned on.
> > > Maven version: 2.0.7
> > > Java version: 1.6.0
> > > OS name: "windows xp" version: "5.1" arch: "x86"
> > > [DEBUG] Building Maven user-level plugin registry from:
> 'C:\Documents
> > > and Settings\Jan Nielsen\.m2\plugin-registry.xml'
> > > [DEBUG] Building Maven global-level plugin registry from:
> > > 'C:\maven-2.0.7\conf\plugin-registry.xml'
> > > [INFO] Scanning for projects...
> > > [INFO] Reactor build order:
> > > [INFO]   Meridian
> > > [INFO]   Meridian Meta Data
> > > [INFO]   Meridian Offer
> > > [INFO]   Meridian Offer API
> > > [INFO]   Meridian Offer Persistence
> > > [INFO]   Meridian Samples
> > > [INFO]   Merchant Samples
> > > [INFO]   Merchant Samples API
> > > [INFO]   Merchant Samples Migration
> > > [INFO]   Merchant Samples Persistence
> > > [INFO]   Merchant Samples CLI
> > > [INFO]   Merchant Samples JSF Portlet
> > > [INFO] Searching repository for plugin with prefix: 'jalopy'.
> > > [DEBUG] Loading plugin prefixes from group: triemax
> > > [DEBUG] Loading plugin prefixes from group:
org.apache.maven.plugins
> > > [DEBUG] Loading plugin prefixes from group: org.codehaus.mojo
> > > [INFO] org.codehaus.mojo: checking for updates from Access
> Development Releases
> > > [INFO] org.codehaus.mojo: checking for updates from Codehaus
> Snapshots
> > > [INFO] org.codehaus.mojo: checking for updates from central
> > > [INFO] artifact org.codehaus.mojo:jalopy-maven-plugin: checking
for
> > > updates from Access Development Releases
> > > [DEBUG] repository metadata for: 'artifact
> > > org.codehaus.mojo:jalopy-maven-plugin' could not be found on
> > > repository: Access Development Releases
> > > [INFO] artifact org.codehaus.mojo:jalopy-maven-plugin: checking
for
> > > updates from Codehaus Snapshots
> > > [DEBUG] repository metadata for: 'artifact
> > > org.codehaus.mojo:jalopy-maven-plugin' could not be found on
> > > repository: Codehaus Snapshots
> > > [INFO] artifact org.codehaus.mojo:jalopy-maven-plugin: checking
for
> > > updates from central
> > > [DEBUG] repository metadata for: 'artifact
> > > org.codehaus.mojo:jalopy-maven-plugin' could not be found on
> > > repository: central
> > > [DEBUG] jalopy-maven-plugin: using locally installed snapshot
> > > [DEBUG] Artifact not found - using stub model: Unable to determine
> the
> > > latest version
> > >
> > >  org.codehaus.mojo:jalopy-maven-plugin:pom:LATEST
> > >
> > >
> > > [DEBUG] Using defaults for missing POM
> > > org.codehaus.mojo:jalopy-maven-plugin:pom:LATEST
> > > [DEBUG] jalopy-maven-plugin: using locally installed snapshot
> > > [DEBUG] Artifact not found - using stub model: Unable to determine
> the
> > > release version
> > >
> > >  org.codehaus.mojo:jalopy-maven-plugin:pom:RELEASE
> > >
> > >
> > > [DEBUG] Using defaults for missing POM
> > > org.codehaus.mojo:jalopy-maven-plugin:pom:RELEASE
> > > [INFO]
>
------------------------------------------------------------------------
> > > [ERROR] BUILD ERROR
> > > [INFO]
>
------------------------------------------------------------------------
> > > [INFO] The plugin 'org.codehaus.mojo:jalopy-maven-plugin' does not
> > > exist or no valid version could be found
> > > [INFO]
>
------------------------------------------------------------------------
> > > [DEBUG] Trace
> > > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
> > > 'org.codehaus.mojo:jalopy-maven-plugin' does not exist or no valid
> > > version could be found
> > >        at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default
> LifecycleExecutor.java:1286)
> > >        at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(De
> faultLifecycleExecutor.java:1522)
> > >        at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAgg
> regationNeeds(DefaultLifecycleExecutor.java:386)
> > >        at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
> ycleExecutor.java:138)
> > >        at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
> > >        at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
> > >        at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
> > >        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:597)
> > >        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)
> > > Caused by:
> org.apache.maven.plugin.version.PluginVersionNotFoundException:
> > > The plugin 'org.codehaus.mojo:jalopy-maven-plugin' does not exist
or
> > > no valid version could be found
> > >        at
>
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlugi
> nVersion(DefaultPluginVersionManager.java:228)
> > >        at
>
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlugi
> nVersion(DefaultPluginVersionManager.java:90)
> > >        at
>
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM
> anager.java:166)
> > >        at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default
> LifecycleExecutor.java:1257)
> > >        ... 14 more
> > > [INFO]
>
------------------------------------------------------------------------
> > > [INFO] Total time: < 1 second
> > > [INFO] Finished at: Wed Oct 17 09:31:13 MDT 2007
> > > [INFO] Final Memory: 2M/4M
> > > [INFO]
>
------------------------------------------------------------------------
> > >
> > >
> ---------------------------------------------------------------------
> > > 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]


---------------------------------------------------------------------
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]

Reply via email to