Elliot Metsger wrote:
Hi David,

Is the groupId for the pluto maven plugin supposed to be 'org.apache.maven.plugins' or 'org.apache.pluto'?

It should be org.apache.pluto. All this time it's been in the maven namespace and shouldn't have been.


The current 1.1.0-beta2 tag installs the pluto maven plugin with a groupId of 'org.apache.pluto', because no groupId is explicitly defined in maven-pluto-plugin/pom.xml.

Yes.  that's right.


1) Prior to building the 1.1.0-beta2 tag I manually removed any and all maven pluto plugins from my local maven repo, including snapshots. 2) I installed the 1.1.0-beta2 maven plugin by cd'ing into maven-pluto-plugin and running 'mvn install'. It installed the plugin into my local repository with an org.apache.pluto group id.

It builds from root without a problem - right?


This causes a build failure [0]. Adding '<groupId>org.apache.maven.plugins</groupId>' to the maven-pluto-plugin/pom.xml, and re-installing the plugin fixed the issue.

Hmmm, shouldn't have to do that.


The group id was removed in r449543, dunno if that was intentional or not.

Nope on purpose.  the maven guys pinged me that we had it wrong.


With regard to the binary release, this shouldn't be a problem as long as the maven-pluto-plugin is installed to a reachable maven repository with the correct groupId.

It shouldn't be anywhere with the maven namespace. Is it? We'll need to update docs to make sure that they are pointing to the pluto namespace. Anything else we need to fix?

David


Elliot

[0]:

[EMAIL PROTECTED]:~/src/asf/svn-exports/release-1.1.0-beta2$ mvn -X -e clean install pluto:install -DinstallDir=/home/esm/apache/apache-tomcat-5.5.17-pluto11beta2 -Dmaven.test.skip=true
+ Error stacktraces are turned on.
Maven version: 2.0.4
[DEBUG] Building Maven user-level plugin registry from: '/home/esm/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/home/esm/apache/maven-2.0.4/conf/plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]   Apache Pluto
[INFO]   Pluto Descriptor Service API
[INFO]   Pluto Descriptor Service Implementation
[INFO]   Pluto Portlet Container
[INFO]   Pluto Portlet Tag Library
[INFO]   Pluto Portal Driver
[INFO]   Pluto Portal Driver Implementation Classes
[INFO]   Pluto Portal
[INFO]   Pluto Testsuite Portlet
[INFO]   Pluto Utilities
[INFO]   Maven Pluto Installer Plugin
[INFO]   Pluto Ant Tasks
[INFO]   Pluto Website Documentation
[INFO] Searching repository for plugin with prefix: 'pluto'.
[DEBUG] maven-pluto-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the latest version

  org.apache.maven.plugins:maven-pluto-plugin:pom:LATEST


[DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-pluto-plugin:pom:LATEST
[DEBUG] maven-pluto-plugin: using locally installed snapshot
[DEBUG] Artifact not found - using stub model: Unable to determine the release version

  org.apache.maven.plugins:maven-pluto-plugin:pom:RELEASE


[DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-pluto-plugin:pom:RELEASE [INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------ [INFO] The plugin 'org.apache.maven.plugins:maven-pluto-plugin' does not exist or no valid version could be found [INFO] ------------------------------------------------------------------------
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.apache.maven.plugins:maven-pluto-plugin' does not exist or no valid version could be found at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1281) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1517) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.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: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)
Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'org.apache.maven.plugins:maven-pluto-plugin' does not exist or no valid version could be found at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:225) at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:158) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1252)
        ... 14 more
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Mon Sep 25 16:00:03 EDT 2006
[INFO] Final Memory: 1M/3M
[INFO] ------------------------------------------------------------------------

Reply via email to