[
https://issues.apache.org/jira/browse/FELIX-5063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15395355#comment-15395355
]
Sébastien Gandon commented on FELIX-5063:
-----------------------------------------
HI JBO, any news on this ?
> Bundle-ClassPath directive does not accept entry parameters
> -----------------------------------------------------------
>
> Key: FELIX-5063
> URL: https://issues.apache.org/jira/browse/FELIX-5063
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-3.0.0
> Reporter: Sébastien Gandon
> Priority: Minor
>
> I need to create a manifest with an Bundle-ClassPath entry that contains
> parameters, but the *maven-bundle* plugin interprets the ';' as a ',' which
> is not what one would expected from an OSGI stand point.
> here is my instruction
> {code}
> <Bundle-ClassPath>{maven-dependencies},partner-${partner.version}.jar;mvn:org.talend.components.salesforce/partner/${partner.version}</Bundle-ClassPath>
>
> {code}
> here is what is generated
> {code}
> Bundle-ClassPath: force-wsc-35.0.0.jar,metadata-34.0.0.jar,json-simple-1
> .1.1.jar,javax.inject-1.jar,partner-34.0.0.jar,mvn:org.talend.component
> s.salesforce/partner/34.0.0
> {code}
> and we would have expected
> {code}
> Bundle-ClassPath: force-wsc-35.0.0.jar,metadata-34.0.0.jar,json-simple-1
> .1.1.jar,javax.inject-1.jar,partner-34.0.0.jar;mvn:org.talend.component
> s.salesforce/partner/34.0.0
> {code}
> Notice the semi-colon that was transformed into a colon.
> PS :
> here is an excerpt of the OSGI spec
>
> The Bundle-ClassPath manifest header must conform to the following syntax:
> Bundle-ClassPath ::= entry ( ',' entry )*
> entry ::= target ( ';' target )* ( ';' parameter ) *
> target ::= path | '.' // See
> 1.3.2
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
