[
https://issues.apache.org/jira/browse/SM-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996795#comment-12996795
]
Alexis Lahouze commented on SM-2027:
------------------------------------
1/ yes
2/ yes
3/ yes
4/ yes
My dependency was defined in the jbi.xml when I set <type>jar</type> and
<classifier></classifier> with the version 4.5 of the plugin.
> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
