Maven 2 & 3

Relocation not working for plugins

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.0.9
  • Fix Version/s: Issues to be reviewed for 3.x
  • Component/s: None
  • Labels:
    None
  • Environment:
    Maven version: 2.0.9
    Java version: 1.5.0_13
    OS name: "mac os x" version: "10.5.4" arch: "i386" Family: "unix"
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

As discussed on the user list, the relocation pom for the Jetty plugin does not seem to work correctly.

See: http://www.nabble.com/Does-relocation-work-for-plugins--td19618624.html

To reproduce, create a project from the webapp archetype, and introduce the Jetty plugin:

 <build>
   ...
   <plugins>
     <plugin>
       <groupId>org.mortbay.jetty</groupId>
       <artifactId>maven-jetty-plugin</artifactId>
       <version>7.0.0pre3</version>
     </plugin>
   </plugins>

Attempting to build the project results in an error:

$ mvn install
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building mywebapp Maven Webapp
[INFO]    task-segment: [install]
[INFO] ------------------------------------------------------------------------
Downloading: http://repo1.maven.org/maven2/org/mortbay/jetty/maven-jetty-plugin/7.0.0pre3/maven-jetty-plugin-7.0.0pre3.jar
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] A required plugin was not found: Plugin could not be found -
check that the goal name is correct: Unable to download the artifact
from any repository

Try downloading the file manually from the project website.

Then, install it using the command:
   mvn install:install-file -DgroupId=org.mortbay.jetty
-DartifactId=maven-jetty-plugin -Dversion=7.0.0pre3
-Dpackaging=maven-plugin -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
   mvn deploy:deploy-file -DgroupId=org.mortbay.jetty
-DartifactId=maven-jetty-plugin -Dversion=7.0.0pre3
-Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url]
-DrepositoryId=[id]

 org.mortbay.jetty:maven-jetty-plugin:maven-plugin:7.0.0pre3

from the specified remote repositories:
 central (http://repo1.maven.org/maven2)

 org.mortbay.jetty:maven-jetty-plugin:maven-plugin:7.0.0pre3

from the specified remote repositories:
 central (http://repo1.maven.org/maven2)

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Mon Sep 22 19:02:01 MST 2008
[INFO] Final Memory: 3M/7M
[INFO] ------------------------------------------------------------------------

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
luke w patterson added a comment -

Just to make sure the relocation metadata was correct, I modified your example

from

<plugins>
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>7.0.0pre3</version>
</plugin>
</plugins>

to

<dependencies>
<dependency>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>7.0.0pre3</version>
</dependency>
</dependencies>

and it downloaded fine.

Show
luke w patterson added a comment - Just to make sure the relocation metadata was correct, I modified your example from <plugins> <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>maven-jetty-plugin</artifactId> <version>7.0.0pre3</version> </plugin> </plugins> to <dependencies> <dependency> <groupId>org.mortbay.jetty</groupId> <artifactId>maven-jetty-plugin</artifactId> <version>7.0.0pre3</version> </dependency> </dependencies> and it downloaded fine.
Hide
Permalink
Jacob Briggs added a comment -

We've been stung by the same problem to correct the comment above:
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>7.0.0pre3</version>
</plugin>

to

<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-maven-plugin</artifactId>
<version>7.0.0pre3</version>
</plugin>

works, however the issue here is legacy poms and redirects. There appears to be a problem with maven's relocation functionality for plugin artifacts.

Show
Jacob Briggs added a comment - We've been stung by the same problem to correct the comment above: <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>maven-jetty-plugin</artifactId> <version>7.0.0pre3</version> </plugin> to <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>jetty-maven-plugin</artifactId> <version>7.0.0pre3</version> </plugin> works, however the issue here is legacy poms and redirects. There appears to be a problem with maven's relocation functionality for plugin artifacts.
Hide
Permalink
luke w patterson added a comment -

I should have given a more thorough explanation. I moved the requirement for org.mortbay.jetty:maven-jetty-plugin:7.0.0pre3 from <plugins> to <dependencies> just to verify that the relocation metadata was correct.

The download was successful when Maven saw maven-jetty-plugin as a <dependency> instead of a <plugin>.

Show
luke w patterson added a comment - I should have given a more thorough explanation. I moved the requirement for org.mortbay.jetty:maven-jetty-plugin:7.0.0pre3 from <plugins> to <dependencies> just to verify that the relocation metadata was correct. The download was successful when Maven saw maven-jetty-plugin as a <dependency> instead of a <plugin>.
Hide
Permalink
Wendy Smoak added a comment -

Another example on the user list: http://www.nabble.com/trouble-relocating-a-plugin-td20195960.html

Show
Wendy Smoak added a comment - Another example on the user list: http://www.nabble.com/trouble-relocating-a-plugin-td20195960.html
Hide
Permalink
Justin Edelson added a comment -

I had to revert the maven-metadata.xml file to remove the relocated version.

You can still reproduce the problem with:
mvn com.mtvi.plateng.maven:maven-hudson-plugin:2.0-alpha-2:add-job

Show
Justin Edelson added a comment - I had to revert the maven-metadata.xml file to remove the relocated version. You can still reproduce the problem with: mvn com.mtvi.plateng.maven:maven-hudson-plugin:2.0-alpha-2:add-job
Hide
Permalink
Joakim Erdfelt added a comment -

Seems to work in Maven 3.x

Here's a test project.
https://github.com/joakime/maven-llama-plugin-relocation

Just build from the top, and use the test-project to see it using the maven-llama-plugin.
Then uncomment the relocation in maven-llama-plugin/pom.xml, mvn clean install, and then execute the test-project again.

Show
Joakim Erdfelt added a comment - Seems to work in Maven 3.x Here's a test project. https://github.com/joakime/maven-llama-plugin-relocation Just build from the top, and use the test-project to see it using the maven-llama-plugin. Then uncomment the relocation in maven-llama-plugin/pom.xml, mvn clean install, and then execute the test-project again.

People

  • Assignee:
    Unassigned
    Reporter:
    Wendy Smoak
Vote (5)
Watch (6)

Dates

  • Created:
    Updated: