Hello,
I am curious if you, or anyone else, has found a solution for this issue? I
have the same problem and it is particularly annoying because it breaks my
Hudson builds.
Cheers,
Pieter
On Sep 10, 2010, at 14:50 , Bruno Harbulot wrote:
> Hello,
>
> I'm trying to use the "bundle" packaging and the maven-bundle-plugin in a
> multi-module project.
>
> The following is declared in the parent POM and in the sub-module POMs
> (although it might not be necessary):
>
> <plugin>
> <groupId>org.apache.felix</groupId>
> <artifactId>maven-bundle-plugin</artifactId>
> <extensions>true</extensions>
> <version>2.1.0</version>
> <configuration>
> <instructions>
>
> <Bundle-SymbolicName>${project.artifactId}</Bundle-SymbolicName>
> </instructions>
> </configuration>
> </plugin>
>
>
> When we were using the 'jar' packaging, "mvn package" was able to find
> dependencies between sub-modules. However, after switching to 'bundle', these
> modules can no longer be found using "mvn package". "mvn install" works (and
> once this has been done once, "mvn package" works after, of course).
> The problem is that it prevents "mvn package" to be done on clean
> installations (for continuous integration, for example).
> Has anyone experienced similar problems? Is there a workaround for this?
> (I'm using Maven 2.2.1, if it's relevant.)
>
> Best wishes,
>
> Bruno.
>
> ---------------------------------------------------------------------
> 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]
