caniszczyk/minerva

A Maven Tycho version of Athena

minerva's Issues

Inconsistent names of modules' directories

What naming scheme should be used for modules' directories? Original Minerva and a version generated with an archetype store submodules in directories with inconsistent naming scheme. Minerva uses bundleId while archetype uses artifactId only:

Only in minerva-eclipse-project-archetype/target/it/projects/minerva/minerva/: minerva.core
Only in minerva-eclipse-project-archetype/target/it/projects/minerva/minerva/: minerva.core.tests
Only in minerva-eclipse-project-archetype/target/it/projects/minerva/minerva/: minerva.doc
Only in minerva-eclipse-project-archetype/target/it/projects/minerva/minerva/: minerva-feature
Only in minerva-eclipse-project-archetype/target/it/projects/minerva/minerva/: minerva-repository
Only in minerva-eclipse-project-archetype/target/it/projects/minerva/minerva/: minerva.source-feature
Only in minerva-eclipse-project-archetype/target/it/projects/minerva/minerva/: minerva.ui
Only in minerva-eclipse-project-archetype/target/it/projects/minerva/minerva/: minerva.ui.tests
Only in .: org.aniszczyk.minerva.core
Only in .: org.aniszczyk.minerva.doc
Only in .: org.aniszczyk.minerva-feature
Only in .: org.aniszczyk.minerva-repository
Only in .: org.aniszczyk.minerva.source-feature
Only in .: org.aniszczyk.minerva.tests.core
Only in .: org.aniszczyk.minerva.tests.ui
Only in .: org.aniszczyk.minerva.ui

Which one should be used?

Archetype-ArtifactId: Inconsistency identifiers

What naming scheme should be used for the Artifact Ids ?

Eclipse displays the ArtifactID and not the project name for the maven projects... therefore, this identifier should be consistent for all the submodules!

At the present time, $artifactId variable is used to set the identifier for all submodules except for the 'core' and the 'ui' submodules.

IMHO, the identifier should be only set with the $bundleId variable:
${bundleId}.core
${bundleId}.core.test
${bundleId}-feature
and so on...

As result, the resource paths displayed in the IDE will become consistent.

[archetype] Child module b.tests.core of b/pom.xml does not exist

Eclipse project generated by archetype is incorrect: build fails with

[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project g:b:1.0-SNAPSHOT (/opt/src/b/pom.xml) has 1 error
[ERROR]     Child module /opt/src/b/b.tests.core of /opt/src/b/pom.xml does not exist
[ERROR] 

...but there is module b.core.tests.

Deploy archetype's -SNAPSHOT to public Maven repository

Hi Chris,

Minerva's archetype should be pushed to public Maven repository, either Eclipse or Maven Central, it doesn't matter. This will make it more visible to outside world and consumed without building from the source.

Add publishing support

Minerva should support publishing to the eclipse.org infrastructure

Add signing support

Minerva should have an example that supports the signing infrastructure at eclipse.org...