[FELIX-3031] maven3 deployment fails where maven2 works

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: maven-bundle-plugin-2.3.6
• Component/s: Maven Bundle Plugin
• Assignee: Stuart McCulloch
• Reporter: Markus Joschko
• Created: 11/Jul/11 15:31
• Updated: 02/Dec/11 15:44
• Resolved: 16/Oct/11 19:20

Description

I want to deploy a bundle to a remote obr. I have configured the
bundle-plugin to use the default repository (which is a
filebased repository). Everything worked fine with maven 2. Now that I
switched to maven 3 I get the following error:

[INFO] — maven-bundle-plugin:2.3.5:deploy (default-deploy) @ test —
[INFO] LOCK file:///var/www/repository/repository.xml
[INFO] Downloading repository.xml
[INFO] Computed bundle uri: http://localhost/repository/example/test/1.0-SNAPSHOT/test-1.0-20110711.152943-4.jar
[ERROR] file doesn't exist: file:/home/markus/.m2/repository/example/test/1.0-SNAPSHOT/test-1.0-20110711.152943-4.jar
[INFO] Writing OBR metadata
[INFO] Uploading repository.xml
[INFO] UNLOCK file:///var/www/repository/repository.xml

The bundle plugin tries to retrieve the jar file from my local
repository. However the maven deploy plugin has also picked up the
remote repository and deployed the bundle in that repository
and not in my local repository.
That's different to maven2. When building with maven2 the bundle is
deployed in my local and in my remote repository by the deploy
plugin.
No idea what has changed (maybe I miss some configuration here?), but
for me it looks like the bundle plugin should pick up the bundle from
the default deploy repository instead of the local repository?