From: Combe, C. <C....@na...> - 2006-09-19 11:24:03
|
Hi, my build problems with GO-1 were my own stupid fault, I had things in the GO-1 module that shouldn't of been there... colin > -----Original Message----- > From: geo...@li...=20 > [mailto:geo...@li...] On=20 > Behalf Of Combe, Colin > Sent: 15 September 2006 09:51 > To: geo...@li... > Subject: Re: [Geotools-gt2-users] i can't build when everyone=20 > else can :-( >=20 > Apologies if this appears as a reposting - I'm sending it=20 > again because it looks like my first attempt didn't make it=20 > onto the list. >=20 > In short, upgrading from maven 2.0.2 to 2.0.4 fixed most of=20 > my problems but I still have a problem with the GO-1 module=20 > breaking the build, errors attached, >=20 > What normally happens with the GO-1 implementation module?=20 >=20 > Regards, > colin > =20 >=20 > > -----Original Message----- > > From: Combe, Colin=20 > > Sent: 11 September 2006 17:05 > > To: 'Martin Desruisseaux' > > Cc: geo...@li... > > Subject: RE: [Geotools-gt2-users] i can't build when everyone=20 > > else can :-( > >=20 > > Hi, > > Again, thanks for response. > > =20 > > You suggested checking whether I was using maven 2.0.4. > > I was using 2.0.2 and upgrading to 2.0.4 seems to have fixed=20 > > the problems. > >=20 > > However, the build still does not get all the way to=20 > > completion - the GO-1 implementation module fails to compile. > > I don't find this that surprising as I know it's work in=20 > > progress but I'm a bit confused by the fact the cruise=20 > > control build results seem to show it compiling (e.g.=20 > > http://geo.openplans.org:9090/buildresults/geotools?log=3Dlog200 > > 60910110928Lbuild.14).=20 > >=20 > > What normally happens with the GO-1 implementation module?=20 > > The errors it produces on my machine are attached. > >=20 > > Martin, in answer to your other questions, svn status confims=20 > > no pom.xml files are modified on my machine, I am using the=20 > > latest code from trunk and I don't have anything weird in=20 > > $JAVA_HOME/jre/lib/ext. > >=20 > > Cheers, > > colin > >=20 > > =20 > >=20 > > > -----Original Message----- > > > From: Martin Desruisseaux=20 > [mailto:mar...@ge...]=20 > > > Sent: 08 September 2006 16:00 > > > To: Combe, Colin > > > Cc: geo...@li... > > > Subject: Re: [Geotools-gt2-users] i can't build when everyone=20 > > > else can :-( > > >=20 > > > Combe, Colin a =E9crit : > > > > I've tried deleting the contents of the m2/repository=20 > > > directory but I'm still struggling.=20 > > >=20 > > > The message attached in yours email suggests that the=20 > > > referencing module was=20 > > > compiled and installed like usual, so I don't know why other=20 > > > modules like=20 > > > renderer don't find it... > > >=20 > > > Just a few questions poping up from my mind: > > >=20 > > > * Does "mvn --version" tell you that you are using Maven 2.0.4? > > >=20 > > > * Does "svn status" tell you that no pom.xml files are=20 > > > modified on your machine? > > >=20 > > > * Are you building latest code from trunk? > > >=20 > > > * Do you have any unusual jar in your $JAVA_HOME/jre/lib/ext=20 > > > directory? I mean > > > any Jar that may duplicate a Maven dependency? I ask this=20 > > > question because a > > > trouble that I had recently with the Maven build was=20 > > > actually caused by an > > > old JAR file in jre/lib/ext overriding a Maven dependency. > > >=20 > > > Martin > > >=20 >=20 |