[
http://jira.codehaus.org/browse/MECLIPSE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208501#action_208501
]
Jake Cobb commented on MECLIPSE-246:
------------------------------------
It would be better to allow this to be a direct override, such that the use
case described here would be:
{code:xml}
<bundleSymbolicName>${project.groupId}.${project.artifactId}</bundleSymbolicName>
{code}
Or perhaps a general mechanism for the plugin's MANIFEST.MF along the lines of:
{code:xml}
<manifest>
<Bundle-SymbolicName>${project.groupId}.${project.artifactId}</Bundle-SymbolicName>
<Bundle-Name>A Custom Name</Bundle-Name>
<!-- etc as needed -->
</manifest>
{code}
> Add a switch to use ${groupId}.${artifactId} as Bundle-SymbolicName in PDE
> mode
> -------------------------------------------------------------------------------
>
> Key: MECLIPSE-246
> URL: http://jira.codehaus.org/browse/MECLIPSE-246
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: PDE support
> Affects Versions: 2.3
> Reporter: Markus Wiederkehr
>
> Currently only the artifact ID is used as bundle name in
> META-INF/MANIFEST.MF. It should be possible to use the combination of group
> ID and artifact ID instead.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
