Bug 502420 - Allow the use of groupId.artifactId for Bundle-SymbolicName
Summary: Allow the use of groupId.artifactId for Bundle-SymbolicName
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Tycho (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-28 09:42 EDT by Ben Zegveld CLA
Modified: 2021-04-28 16:52 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben Zegveld CLA 2016-09-28 09:42:16 EDT
I'm having a problem with the packaging of an eclipse bundle. I want to get an unique name for it without breaking the rules we have concerning the maven naming convention for groupId and artifactId. I ended up with the following artifactId: Presentation. The rest of the information that makes it unique is listed in the groupId. So as far as maven is concerned this is a valid uniquely identifiable result.

At some point I will most likely end up with multiple of the Presentation artifactIds. Now the org.eclipse.tycho:tycho-packaging-plugin:0.26.0:validate-id tells me that the Bundle symbolic name (that I set to match the maven representation of its groupId:artifactId) should be just the artifactId which would in this case be Presentation.

I also did some researching online and found out that maven's unique identification is GroupId:ArtifactId:Version, while for OSGI this is Bundle-SymbolicName:Bundle-Version. That got me wondering why tycho expects ArtifactId:Version while this is not by definition unique.

Would it be possible to allow a configuration setting so Tycho expects the combination of groupId and artifactId as the Bundle-SymbolicName, besides the default setting of artifactId.
Comment 1 Mickael Istria CLA 2021-04-08 18:07:38 EDT
Eclipse Tycho is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse/tycho/issues/ instead. If this issue is relevant to you, your action is required.
0. Verify this issue is still happening with latest Tycho 2.4.0-SNAPSHOT
  if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done
  if issue is still present when latest release:
* Create a new issue at https://github.com/eclipse/tycho/issues/
  ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  ** In the GitHub description, start with a link to this bugzilla ticket
  ** Optionally add new content to the description if it can helps towards resolution
  ** Submit GitHub issue
* Update bugzilla ticket
  ** Add to "See also" property (up right column) the link to the newly created GitHub issue
  ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  ** Set status as CLOSED MOVED
  ** Submit

All issues that remain open will be automatically closed next week or so. Then the Bugzilla component for Tycho will be archived and made read-only.