Hi,
1. cli
Building trunk from cli with 'mvn clean install' gives here:
Failed to execute goal on project
org.apache.onami.autobind.configuration:... Could not find artifact
org.apache.onami:org.apache.onami.parent:pom:1-incubating-SNAPSHOT in
apache.snapshots (http://repository.apache.org/snapshots) -> [Help 1]
Any reason why some modules depend still depend on version 1 of parent.
Why not having all trunk modules following the latest parent? If there
are any reasons to stay on version 1, at least that version 1 should be
available in the snapshot repo.
2. eclipse
I imported trunk in m2eclipse (latest version from eclipse.org) and got
some red cross on the pom.xml:
org.codehaus.plexus.archiver.jar.Manifest.merge(org.codehaus.plexus.archiver.jar.Manifest)
I bumped a failing module to use the 3-incubating-SNAPSHOT, commented in
that parent pom the maven-jar-plugin configuration (where it says to
build the MANISFEST.MF, and module became green. I had that kind of
issue on other projects with m2eclipse, so I guess this is more a bug on
the m2eclipse side. However, I think onami should play fine with m2eclipse.
As direct action to allow further hack in eclipse, what about bumping
all modules to 3-incubating-SNAPSHOT parent?
Thx, Eric
