I'm just having the same issue trying to build the trunk. Is there any Jenkins build taking care of this? I mean, building the project for the first time
Cheers On Mon, Jan 14, 2013 at 9:14 AM, Simone Tripodi <[email protected]>wrote: > Salut Eric! > > > 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. > > all modules should depend to parent 1-incubating, no snapshots - no > specific reason why some of them are outdated, I will check them ASAP. > > > 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. > > > > yes it is a known m2e issue :( > > > > > As direct action to allow further hack in eclipse, what about bumping all > > modules to 3-incubating-SNAPSHOT parent? > > parent 2-incubating is still under vote on IPMC, once vote passes the > next step is updating the parent to that version. > > Thanks for reporting! > -Simo > > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > > On Mon, Jan 14, 2013 at 8:33 AM, Eric Charles <[email protected]> wrote: > > 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 >
