Re: [Geotools-devel] failure building on ares (jjtree-javacc:jar:11-SNAPSHOT)

Switching to the Maven mojo would be great (the less custom build code we have around the better). Jody Garnett On Mon, Aug 18, 2014 at 7:03 AM, Jim Hughes wrote: > Hi all, > > I'm generally interested in the CQL parser. Is switching to the Maven > mojo project something I could contribute i

Re: [Geotools-devel] failure building on ares (jjtree-javacc:jar:11-SNAPSHOT)

Hi all, I'm generally interested in the CQL parser. Is switching to the Maven mojo project something I could contribute in a few weeks? (I'd be doing it on personal time.) Jim On 08/16/2014 03:57 AM, Andrea Aime wrote: On Sat, Aug 16, 2014 at 7:46 AM, Jody Garnett

Re: [Geotools-devel] failure building on ares (jjtree-javacc:jar:11-SNAPSHOT)

First try at a fix didn't work. Trying something else but I have to run out for the day. I'll try to do what I can from my phone but this will probably have to wait until Sunday afternoon my time to fix. Sorry guys. On Sat, Aug 16, 2014 at 8:43 AM, Justin Deoliveira < [email protected]> w

Re: [Geotools-devel] failure building on ares (jjtree-javacc:jar:11-SNAPSHOT)

Hey guys, This is an issue with repository settings. I left the "unique snapshots" feature turned on and then later turned it off. I'm going to clear out the repo and start seeding it again. Sorry for the inconvenience. -Justin On Sat, Aug 16, 2014 at 1:57 AM, Andrea Aime wrote: > On Sat, Au

Re: [Geotools-devel] failure building on ares (jjtree-javacc:jar:11-SNAPSHOT)

On Sat, Aug 16, 2014 at 7:46 AM, Jody Garnett wrote: > I assume we have tried http://mojo.codehaus.org/javacc-maven-plugin/ >> > Don't know we did. Afaik the javacc plugin we use was developed before that mojo project existed. The mojo one works btw, I use it in GeoServer for some bits of the WC

Re: [Geotools-devel] failure building on ares (jjtree-javacc:jar:11-SNAPSHOT)

> > 5) And a javadoc build - which is the one failing > Running the same command locally works: mvn -f modules/pom.xml javadoc:aggregate ... [INFO] [INFO] BUILD SUCCESS [INFO]

Re: [Geotools-devel] failure building on ares (jjtree-javacc:jar:11-SNAPSHOT)

Kicking a few builds on ares to see if I can watch the failure .. within a single job we have: 1) Initial build which I expected [INFO] [INFO] BUILD SUCCESS [INFO]

[Geotools-devel] failure building on ares (jjtree-javacc:jar:11-SNAPSHOT)

Branches build locally without issue, assume I have a 11-SNAPSHOT in my local maven repository, and thus am not getting caught out over timestamps. Ares reports: *[ERROR] Plugin org.geotools.maven:jjtree-javacc:11-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact

Re: [Geotools-devel] failure releasing from hudson?

On Mon, Nov 12, 2012 at 10:23 AM, David Winslow wrote: > Looks like something went awry when uploading to Sourceforge: > > rsync: mkdir "/home/pfs/project/g/ge/geotools/GeoTools 9 Releases/9.0-M0" > failed: No such file or directory (2) > rsync: connection unexpectedly closed (9 bytes received so

Re: [Geotools-devel] failure releasing from hudson?

Looks like something went awry when uploading to Sourceforge: rsync: mkdir "/home/pfs/project/g/ge/geotools/GeoTools 9 Releases/9.0-M0" failed: No such file or directory (2) rsync: connection unexpectedly closed (9 bytes received so far) [sender] rsync error: error in rsync protocol data stream (c

Re: [Geotools-devel] failure releasing from hudson?

A case of RTFM: the next stage geotools-release-publish has done the trick :-) > One thing I did *not* see was it deploy anything …. checking: > - http://download.osgeo.org/webdav/geotools/org/geotools/gt-cql/ > > Do not see a 9.0-M0 - what did I miss? > > -- > Jody Garnett -

Re: [Geotools-devel] failure releasing from hudson?

Hit it again: http://hudson.opengeo.org/hudson/view/geotools/job/geotools-release/50/console And this time it made it through to SUCCESS Result is here: - http://gridlock.opengeo.org/geotools/release/9.0-M0/ One thing I did *not* see was it deploy anything …. checking: - http://download.osgeo

[Geotools-devel] failure releasing from hudson?

Not sure what to make of that? http://hudson.opengeo.org/hudson/view/geotools/job/geotools-release/49/console HEAD is now at a66287b Close iterators left open by CollectionDataStore getCount and getBounds methods as per GEOT-4306 Previous HEAD position was a66287b... Close iterators left open

Re: [Geotools-devel] Failure on win 64

Oops. Forgot to commit a file for GEOT-2816. Committed now so build should be back momentarily. If not please feel free to roll back the changes and I will fix the issue tomorrow. Apologies for the outage and thanks for the patience :) On Sun, Mar 6, 2011 at 1:05 PM, Andrea Aime wrote: > On Sun,

Re: [Geotools-devel] Failure on win 64

On Sun, Mar 6, 2011 at 7:30 PM, Simone Giannecchini < [email protected]> wrote: > Dear All, > I am seeing a failure on trunk in the following test: > > testLookupWithExtendedClasspath(org.geotools.factory.FactoryRegistryTest) > > I am attaching the relevant report if it helps. >

[Geotools-devel] Failure on win 64

Dear All, I am seeing a failure on trunk in the following test: testLookupWithExtendedClasspath(org.geotools.factory.FactoryRegistryTest) I am attaching the relevant report if it helps. Regards, Simone Giannecchini --- Ing. Simone Giannecchini

Re: [Geotools-devel] Failure!

I asked 3 months ago what people were using; since you managed to make a release using 2.0.7 - 2.0.8 can I update the developers guide to reflect one of these versions? The message comes from not being able to deploy every other month during the Maven 2.0.4 - 2.0.5 transition. Perhaps it is mor

Re: [Geotools-devel] Failure!

Jody Garnett ha scritto: > Andrea Aime wrote: >>> Dropping back to Java 5 results in different math apparently, doing >>> so now... >> Hum is that 2.4.1 that you're talking about? If so, it's supposed to >> be built with java 1.4.2, did we ever committed to make it buildable >> with other java ver

Re: [Geotools-devel] Failure!

Here is the details: > C:\java>java -version > java version "1.6.0_03" > Java(TM) SE Runtime Environment (build 1.6.0_03-b05) > Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode) Jody - This SF.net email is sponsored

Re: [Geotools-devel] Failure!

Jody Garnett a écrit : > To be clear this is an accuracy issue that only occurs: > - on Athlon hardware > - using Java 6 Using a 32 or 64 bits JVM? You can get this info with java -version. Martin - This SF.net email

Re: [Geotools-devel] Failure!

Andrea Aime wrote: >> Dropping back to Java 5 results in different math apparently, doing >> so now... > Hum is that 2.4.1 that you're talking about? If so, it's supposed to > be built with java 1.4.2, did we ever committed to make it buildable > with other java versions? Now we did not; but I am

Re: [Geotools-devel] Failure!

Jody Garnett ha scritto: > I am getting my "usual failure" out of the ScriptTest ... >> Running org.geotools.referencing.ScriptTest >> Tests run: 14, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.5 >> sec <<< FAILURE! > Details: >>

[Geotools-devel] Failure!

I am getting my "usual failure" out of the ScriptTest ... > Running org.geotools.referencing.ScriptTest > Tests run: 14, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.5 > sec <<< FAILURE! Details: > --- > Test set: o

[Geotools-devel] Failure while building a 2.2.M1 release

It sound like that the "maven createRelease" target is incomplete. The javadoc is truncated, but I think that it was already truncated before while unoticed. I tried to unzip geotools-src-2.2.M1.zip and invoke "maven build" in a clean directory but get build failure in main. The "modified-src"