On 2/28/06, David Crossley <[EMAIL PROTECTED]> wrote: > Giacomo Pati wrote: > > David Crossley wrote: > > >Giacomo Pati wrote: > > >>David Crossley wrote: > > >>> > > >>>Would someone please help to get started with Maven. > > >>>Too many days have been wasted. > > >>> > > >>>I have today's Cocoon trunk. Installed Maven-2.0.2 > > >>> > > >>>$ cd cocoon-trunk > > >>>$ mvn -Dmaven.test.skip=true clean install > > >>>... watch thousands of warnings and stuff go by. > > >> > > >>I've very few WARNING messages (except those for old jar 'Not a v4.0.0 > > >>POM' ones, which come from 'legacy' Maven artifact. > > > > > >This was populating a brand new local repository. > > > > I've moved away my ~/.m2 directory as well just to see whethter I have > > the same problems as some of you guys had. > > > > It took quite awhile (~30 min) but I was able to compile hole trunk in > > one go. I have to admit that I'm using a Maven 2.1-SNAPSHOT build some > > weeks ago by myself (don't know if that has anything to do with it). > > > > I'm sitting here in the middle of Europe with quite a good Internet > > connectivity. > > > > >>The WARNIN message you've included above come IIRC from network problems > > >>Maven encountered during download of artifacts. Just redo again until > > >>Maven was able to resolve all dependency (and thus has donwloaded all > > >>artifacts). > > > > > >Yeah i have been doing that. Gets to a different place > > >each time. There are many warnings from various repos, > > >but it usually gets each from one of the alternates. > > > > Ok. Without having a ~/.m2 I got those lots of WARNING messages now > > as well. > > Sounds like i need to just keep banging away > with "mvn install".
David, I have tried what Reinhard described above four times now. 1-Failed, 2-Failed, 3-Success, 4-Failed. It seems to fail at different locations for different reasons each time. --tim
