Andrea and Saul - I understand of where you speak :-) Looking through past email it does appear as if there is a reason to upgrade to maven 2.0.5 (martin had the initial inspiration, when we tried last month it was one of the reasons Cory and I had the build down for two days).
Cory had a fatal problem with Maven 2.0.6 - but from email I cannot tell what it was. I will ask Jesse if he knows more - until then we may ask someone to try it. For me to be "happy" I wanted confirmation that Maven 2.0.5 (or Maven 2.0.6) actually will work for our release at the end of the month. I have not gotten this confirmation - I suspect that Cory's fatal problem with Maven 2.0.6 was related to some step of the release process since he is good about checking into such things. I also suspect the recent thing that broke the build for me (introducing opengis nogenerics as a dependency of the root pom.xml was introduced to fix javadoc generation for either Maven 2.0.5 or Maven 2.0.6). I think like acuster I should shut up for the rest of the day and wait for the details to trickle out. Although if anyone has OSX it would be good to confirm what version of maven works. Cheers, Jody Farber, Saul (ENV) wrote: > In addition, why are we talking about 2.0.5? If we're going to upgrade, > shouldn't we upgrade to the LATEST maven? I.e. maven 2.0.6? > > --saul > > ________________________________ > > From: [EMAIL PROTECTED] on behalf of Andrea Aime > Sent: Tue 4/24/2007 11:31 AM > To: Jody Garnett > Cc: geotools-devel > Subject: Re: [Geotools-devel] Maven 2.0.5 is it a go? > > > > Jody Garnett ha scritto: > >> Hi Justin; you are the last guy with a build box right now - I would >> like to know if Maven 2.0.5 is officially a go. I think you will find a >> few other emails on the topic (hi Acuster) .... >> >> If so I would recommend we make a news announcement (rather then the >> current email from a week or so ago). >> >> For me the last sanity check on Maven 2.0.5 is if we can make a release >> from it - I already found one example yesterday where that was not the >> case. A geoapi nogenerics dependency had been added to the root pom.xml >> that conflicted with the exclusion of geoapi nogenerics in >> unsupported/geometry. >> > I probably lost what was the reason why we absolutely needed 2.0.5 > and could not sit on 2.0.4 > > Given maven upgrades track record of breaking our builds, we should be > very careful about requiring an upgrade. Was there a very compelling > reason for this upgrade? > > Cheers > Andrea > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > > > > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
