[
https://issues.apache.org/activemq/browse/SM-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63255#action_63255
]
Lars Heinemann commented on SM-2008:
------------------------------------
It's quite easy to test this. Just checkout the source code of the Maven JBI
Plugin from the trunk and build it locally using mvn clean install.
Afterwards switch all pom files in your project to use the maven-jbi-plugin in
version 4.4-SNAPSHOT (thats the trunk)
Yes, please create an issue for the m3 incompatibility.
Regards
Lars
> jbi maven plugin: service assembly & attached artifact
> ------------------------------------------------------
>
> Key: SM-2008
> URL: https://issues.apache.org/activemq/browse/SM-2008
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
> Reporter: Kari J. Niemi
> Assignee: Lars Heinemann
>
> jbi maven plugin would seem the behave badly when creating a service
> assembly. At least when the pom file with packaging jbi-service-assembly
> contains only dependencies to jbi-service-units (and the project for that
> pom.xml does not contain any java code in src/main/java), the plugin first
> creates a jar, installs it as a _zip_, then creates the correct zip and
> installs it as an attached artifact.
> If I got it right from the plugins source code, it's contradicting the
> "correct way" that's referred here:
> http://maven.40175.n5.nabble.com/Missing-search-results-with-assembly-attached-artifacts-td131996.html
> "What happens in those cases is that you end up with empty jar, and a zip
> that has _same_ coordinates as main artifact, but only different extension.
> Since Nexus reads POM to figure out the packaging, it will think in these two
> cases it is "JAR"."
> I ran in to this problem when trying to package the service assebly using the
> maven-rpm-plugin. When using dependencies to package the rpm, it just keeps
> packing the jar whiles of the service assembly -not the zip file at all. I
> suppose it's because the jar & zip files have the same maven coordinates.
> With the BCs/SEs the zip file gets the classifier "installer", and with that
> I can get the BC/SE zip file to the rpm(but I'm also getting the jar there
> even if I'm setting the dependency type to zip...)
> maven 2.09,2.2.1,3 tried. latest beta of maven-rpm-plugin,
> jbi-maven-plugin:4.0,4.3...errrr....at least some combinations of these...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
