rename org.eclipse.osgi to org.eclipse.equinox.framework

[laeubi]

Currently we have the bundle (and it uses the name as artifact id as well) org.eclipse.osgi, while this historically might be a good choice it has become confusing over time and actually violates the Eclipse rules for project naming (and collides with https://projects.eclipse.org/projects/technology.osgi):

https://www.eclipse.org/projects/handbook/#resources-maven

I therefore like to suggest to take actions to migrate to a new name org.eclipse.equinox.framework, as a first step one could adjust the maven deployment to deploy it to a new artifact id and install a relocation pom:

https://maven.apache.org/guides/mini/guide-relocation.html

Compare for example:

• https://mvnrepository.com/artifact/org.apache.felix/org.apache.felix.framework
• https://mvnrepository.com/artifact/org.knopflerfish/framework

Also try to search on central for:

• felix framework (first hit)
  versus
• equinox framework (no results)

[merks]

The naming issue is a red herring because the OSGi project uses the org.osgi namespace:

https://github.com/osgi/osgi

Also, the Eclipse project happily used org.eclipse.anything whenever the mood strikes without regard whether "anything" is a project or not.

Of course lots of things depend on that bundle name:

So changing that seems a bit of a non-starter...

So that leaves the question of "confusion". I don't argue it's not a confusing name, though it seems not so confusing, but moving it is more likely to cause new confusion than the eliminate old confusion.

One current finds it here:

https://repo1.maven.org/maven2/org/eclipse/platform/org.eclipse.osgi/

Will changing that help someone or create work for someone and maybe create new confusion about the two places it can be found?

[laeubi]

Equinox has to use org.eclipse.equinox and OSGi project is allowed to use org.eclipse.osgi thats the rules regardles if they can use other group IDs, this will change see:

• Groupid for the OSGi Technology project osgi/osgi#596

beside that, I always need to remember that the Equinox Framework(!) does not named framework but "org.eclipse.osgi" that really confusing and makes it hard to use in maven.

[merks]

Apparently Equinox has used these:

[laeubi]

Yes as I said, for historic reasons and it actually violates the namespace rules, equinox has namespace org.eclipse.equinox so we better get rid of it (some of your mentioned things are already worked on or deprecated or both).

[merks]

I hope that the cure is not worse than disease that we have lived with for 20 years...

[tjwatson]

org.eclipse.osgi as a bundle name is considered API. Changing it will break an unknown (I think large) amount of things.

[laeubi]

org.eclipse.osgi as a bundle name is considered API. Changing it will break an unknown (I think large) amount of things.

Should not all packages be internal or exposing standard osgi api? So consumers better use import-package anyways.

[tjwatson]

Package names are different from bundle names. You want to change the bundle name, that is an API breaking change. Changing API package names (or not exporting Eclipse API packages) like org.eclipse.osgi.service.localization would also be a major breaking change.