Hi Benson,
Benson Margulies wrote:
> I've hit a problem with Maven 3.2.5 and the karaf-maven-plugin.
>
> One module builds a Karaf feature with the karaf maven plugin; this
> produces:
>
> <dependency>
> <groupId>${project.groupId}</groupId>
> <artifactId>rosapi-features</artifactId>
> <version>${project.version}</version>
> <classifier>features</classifier>
> <type>xml</type>
> <scope>runtime</scope>
> </dependency>
>
> The packaging of this project is 'feature' to use the karaf-maven-plugin.
>
>
> The second module consumes it, via the dependency above. It also uses
> the karaf-maven-plugin with a different packaging to make the karaf
> assembly.
>
> When I try to run release:prepare, I fail, because the features.xml
> file is not, apparently, resolved correctly from the reactor. Does
> anyone here on the Maven side have any suggestions before I try to
> dive into the Karaf side? Of course, it works fine when I am _not_
> running the release plugin.
I assume the modules have a shared parent with the same version. Declare the
artifact in a dependencyManagement section of the parent (don't use a
property for the version there - the release plugin will handle it) and drop
the version when you declare the dependency in the modules.
While your approach should have worked in the first place, we had less
problems with this solution.
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
