jar, sources.jar and javadoc.jar should not have the same bundle symbolic name in MANIFEST.MF

Description

The following files of hibernate-core should have different (unique) bundle symbolic names in the MANIFEST.MF. Currently they have the identical name

Bundle-SymbolicName: org.hibernate.orm.core

  • hibernate-core-5.4.1.Final.jar

  • hibernate-core-5.4.1.Final-javadoc.jar

  • hibernate-core-5.4.1.Final-sources.jar

It is the same for hibernate-osgi

Bundle-SymbolicName: org.hibernate.orm.osgi

  • hibernate-osgi-5.4.1.Final.jar

  • hibernate-osgi-5.4.1.Final-javadoc.jar

  • hibernate-osgi-5.4.1.Final-sources.jar

It is the same for hibernate-hikaricp

Bundle-SymbolicName: org.hibernate.orm.hikaricp

  • hibernate-hikaricp-5.4.1.Final.jar

  • hibernate-hikaricp-5.4.1.Final-javadoc.jar

  • hibernate-hikaricp-5.4.1.Final-sources.jar

They should have different (unique) names. Our p2-repository-manager packagedrone[1] can't import files, if the bundle symbolic name is not unique.

All files are downloaded from maven central.

https://search.maven.org/search?q=g:org.hibernate%20AND%20a:hibernate-core%20AND%20v:5.4.1.Final
https://search.maven.org/search?q=g:org.hibernate%20AND%20a:hibernate-osgi%20AND%20v:5.4.1.Final

[1] https://www.eclipse.org/package-drone/

Environment

None

Activity

Show:
Guillaume Smet
February 7, 2019, 10:30 PM

I don't think we will change that. It's the default behavior of our build tools.

And it's not an issue for all the other package managers.

Assignee

Unassigned

Reporter

Tobi Hein

Fix versions

None

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Worked in

5.1.0

Affects versions

Priority

Minor
Configure