[
https://issues.apache.org/jira/browse/ACE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12999275#comment-12999275
]
Geert Schuring commented on ACE-129:
------------------------------------
Sorry, my second comment was not a reaction to yours, it sounds real sarcastic
this way and that was not the intention. I wrote the second comment before your
response to my first comment was shown.
I understand that you want to keep in line with the naming convention used by
other OSGI projects. My only point is that this is not the maven convention.
But because OSGi and Maven differ on some points its ok for me to choose either
one, as long as it's an explicit choice, and not some workaround to make it
easy to set the bundle symbolicname while the maven-bundle-plugin does that
correctly by default no mather which groupId/artifactId scheme we use.
Considering your comments I would like to suggest to use the artifactId you
suggested, and to remove the Bundle-SymbolicName instruction from the bnd
config since the maven-bundle-plugin's default value is equal to the artifactId
you're going to use.
> Use artifactId naming convention as used in Felix
> -------------------------------------------------
>
> Key: ACE-129
> URL: https://issues.apache.org/jira/browse/ACE-129
> Project: Ace
> Issue Type: Improvement
> Affects Versions: 0.8.0
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 0.8.0
>
>
> To be compliant with most OSGi projects, including Apache Felix, the
> artifactId of our bundles should look like:
> groupId: org.apache.ace
> artifactId: org.apache.ace.client.automation
> Like this, we will be able to directly use the artifactId in the
> Bundle-SymbolicName of the Felix maven-bundle-plugin.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
