[FELIX-1039] Inconsistency packaging vs. type

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: maven-bundle-plugin-2.0.0
• Fix Version/s: maven-bundle-plugin-2.3.5
• Component/s: Maven Bundle Plugin
• Environment: Maven-2.1.0
• Assignee: Stuart McCulloch
• Reporter: Thomas Diesler
• Created: 15/Apr/09 08:35
• Updated: 11/Oct/11 17:09
• Resolved: 24/Jun/11 13:28

Description

The Maven Bundle Plugin uses

<packaging>bundle</packaging>

Scenario #1 - dependency uses type=bundle

<dependency>
<groupId>org.jboss.osgi</groupId>
<artifactId>jboss-osgi-common</artifactId>
<version>${version}</version>
<type>bundle</type>
</dependency>

with type=bundle the the dependency is resolved correctly from the the build reactor.
'mvn package' succeeds. Note, the artefact is not yet in the local repository.

Scenario #2 - dependency uses unspecified type

<dependency>
<groupId>org.jboss.osgi</groupId>
<artifactId>jboss-osgi-common</artifactId>
<version>${version}</version>
</dependency>

'mvn package' fails if the artefact is not yet in the local repository
'mvn install' succeeds

Scenario #3 - the dependent bundle is not part of the reactor build

'mvn package' or 'mvn install' will always fail when the dependency is declared with type=bundle

Fazit:

If you declare the dependency with type=bundle, the dependency cannot be resolved from the repository.
If you don't declare a dependency type, the dependency can only be resolved from the repository. 'mvn package' will fail if the dependency is not in the repository.

Workaround:

Don't use type=bundle in the dependency and always install. i.e. 'mvn install'