[
https://issues.apache.org/jira/browse/FELIX-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614047#action_12614047
]
Ken Paulsen commented on FELIX-636:
-----------------------------------
Thanks for the clarification! Your explanation makes sense and describes how
it is functioning.
I agree w/ Sahoo, it would be nice if it were documented with the
maven-bundle-plugin-bnd.html documentation.
Thanks!
Ken Paulsen
> Bundle-SymbolicName is generated incorrectly
> --------------------------------------------
>
> Key: FELIX-636
> URL: https://issues.apache.org/jira/browse/FELIX-636
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-1.4.1
> Environment: Ubuntu
> Reporter: Ken Paulsen
> Attachments: pom.xml
>
>
> I have the following in the pom.xml:
> <groupId>org.glassfish.jsftemplating</groupId>
> <artifactId>jsftemplating</artifactId>
> After I build, I get the following in the MANIFEST.MF:
> Bundle-SymbolicName: org.glassfish.jsftemplating
> Notice it only has 1 "jsftemplating" in the symbolic name. If I change the
> artifactId to something else and make no other changes, I get the expected
> results. For example, if I put this in the pom.xml:
> <groupId>org.glassfish.jsftemplating</groupId>
> <artifactId>jsft</artifactId>
> I get this in the MANIFEST.MF:
> Bundle-SymbolicName: org.glassfish.jsftemplating.jsft
> Notice now both the full groupId AND artifact id appear in the symbolic name.
> This is what I expected to see.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
