[
https://issues.apache.org/jira/browse/SM-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987397#action_12987397
]
Kari J. Niemi commented on SM-2027:
-----------------------------------
Primary & secondary artifacts explained:
http://www.sonatype.com/people/2008/05/misused-maven-terms-defined/
I suppose for jbi components(SE&BC), jbi-maven-plugin produces
-the jar as a primary artifact with empty classifier
-and then the zip as a secondary artifact with "installer" classifier.
If you need to pick only the jar using a pure maven dependency, I'm not sure if
you can use the empty classifier (I've also noticed that type=jar would not
work, because the type is of course jbi-component).
> jbi-maven-plugin, jbi.xml generation, missing jbi-component lib in
> bootstrap-class-path
> ---------------------------------------------------------------------------------------
>
> Key: SM-2027
> URL: https://issues.apache.org/jira/browse/SM-2027
> Project: ServiceMix
> Issue Type: Bug
> Components: tooling
> Affects Versions: jbi-maven-plugin-4.3
> Environment: unrelated
> Reporter: Alexis Lahouze
> Attachments: bootstrap_classpath_element.diff
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> I tried to extend an existing Servicemix Component (servicemix-http).
> So, I added a dependency to this component.
> When I started Servicemix, I got an error "ClassNotFoundException:
> org.apache.servicemix.http.HttpBootstrap" (or anything like that)
> I had a look at my generated jbi.xml, and I saw that path-element for
> servicemix-http was missing.
> I checked out jbi-maven-plugin from the svn trunk, and noticed that
> generation of path-elements was different between component and bootstrap.
> Only jar type was accepted for bootstrap.
> At line 95, I replaced the test "jar".equals(...) by !info.isSharedLibrary()
> and it worked.
> I attached my patch.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
