Change artifactId to "dkpro-core-XXX"

[reckart]

For quite some time, DKPro has used OSGi-style artifact IDs. However, we never got around
to really turn our JARs into OSGI bundles. Since the artifactIds are quite long, I
think it's time to change them to a more Maven-like format:

dkpro-core-api-XXX-asl
dkpro-core-io-XXX-asl
dkpro-core-XXX-asl
etc.

• rename all modules and packages that do not contain types (to maintain type name compatibility)
• introduce empty proxy artifacts under the new names that depend on the artifacts using the old names, specifically for artifacts containing types

---

Original issue reported on code.google.com by richard.eckart on 2013-08-02 16:46:13

[reckart]

(No text was entered with this change)

Original issue reported on code.google.com by richard.eckart on 2013-08-11 17:26:05

• Labels removed: Milestone-1.5.0

[reckart]

(No text was entered with this change)

Original issue reported on code.google.com by richard.eckart on 2013-12-19 01:58:29

[reckart]

(No text was entered with this change)

Original issue reported on code.google.com by richard.eckart on 2014-08-06 20:36:49

• Labels added: Milestone-1.7.0

[reckart]

(No text was entered with this change)

Original issue reported on code.google.com by richard.eckart on 2014-10-02 12:37:04

• Labels added: Milestone-1.8.0
• Labels removed: Milestone-1.7.0

[reckart]

(No text was entered with this change)

Original issue reported on code.google.com by richard.eckart on 2014-11-28 22:06:47

• Labels added: Milestone-2.0.0
• Labels removed: Milestone-1.8.0

[reckart]

I am considering changing the module names to the short variants already for the 1.8.0 release for the benefit of easier navigation on github and leaving the package names and artifact IDs as is for the moment. Does anybody have any thoughts on this?

[daxenberger]

ok from my side.

[zesch]

Ok here too
Johannes Daxenberger notifications@github.com schrieb am Mo., 28. Dez.
2015 um 15:06:

ok from my side.

—
Reply to this email directly or view it on GitHub
#186 (comment).

[reckart]

I would like to start this before 2.0.0:

• rename all modules and packages that do not contain types (to maintain type name compatibility)
• introduce empty proxy artifacts under the new names that depend on the artifacts using the old names, specifically for artifacts containing types

[Horsmann]

Wouldn't it be the cleaner way to simply rename everything and re-upload things into the artifactory under the new package name rather than introducing an additional proxy layer?
I would say if you change from say 1.8.0 to 1.9.0 you can expect from the user that he/she updates the imports of the types that are being used?

[reckart]

The package names in an artifact should reflect the groupId/artifactId to avoid potential conflicts between multiple artifacts under different IDs containing the same classes. So I only want to move the classes to artifacts under new names when also the package names change. However, for UIMA-types, the classname is a part of the UIMA type name and changing that will break lots of things, in particular related to loading existing XMI/bincas files. Those files are what I am worried about, not the imports in Java classes.

[reckart]

Ok, so I see no objections and nobody screaming, so I'll continue with this slow migration to the new names.

[reckart]

All packages and groupId/artifactIds have been changed.

The packages for the UIMA JCas classes remain the same though!