Details
Description
We tried to remove the "gt2-" prefix in module names, in order to have <artifactID> matching exactly the directory name. Such match allowed us to remove the <scm> section in all pom.xml files. We also though that a "gt-" prefix was redundant with the <groupId>org.geotools</groupId> declaration. However experience show that it leads to two problems:
- The "gt-" prefix do not appears in the manifest classpath when building a single module (MJAR-61).
- Name clash in eclipse projects when two projects are mounted using maven-eclipse-plugin (
MECLIPSE-119)
The path of less resistance seems to reinsert the "gt2-" prefix back in all module names. We would have to reinsert the <scm> section in all modules too, which is error prone. However we would revisit this issue if the above-cited Maven issue are fixed.
Issue Links
- depends upon
-
MJAR-61
Manifest classpath ignores the "real" JAR filenames specified in <finalName>
-
-
MECLIPSE-119
Allow custom project name for eclipse projects
-
-
MECLIPSE-251
Allows prefixing of eclipse project name
-
- is related to
-
GEOT-982
Reorganize the source directory structure for Maven 2 standard compliance
-