Thanks Michael :-)
We have a successful test - and two mac developers down (sigh!). So
we are now sure it is the new Java version that caused this; as far as
I know Mac does not really provide release notes so we are going to
get a bit of a guessing game to determine what is wrong.
So my next qu
Did the system update (java 1.5.0_19), now there are failed tests for
the shapefile module.
So that was a useful update :-(
Michael
--
___
Geotools-devel mailing list
Geotools-
mvn -Dall clean install worked for trunk (after I remembered to switch
back from the process branch which currently breaks a couple of
modules)
That was with:
osx 10.5.7
java 1.5.0_16
mvn 2.1.0
I'll try it again when the system update is installed.
Michael
--
Oops... Just after sending the last email I checked system update and
I don't have the latest Apple Java. I've got 1.5.0_16 rather than
1.5.0_19.
I'll try building before and after installing the os update.
Michael
--
_
I have osx 10.5.7 with all current updates and maven 2.1.0.
Just updating now then I'll try a build from the command line.
Michael
--
___
Geotools-devel mailing list
Geotools-d
Nope:
A couple of clarifications ...
- I did ask if Russell had read the developers guide; since he was
already building with maven to work with Ben's team; and had the
geotools configuration stuff sorted out I thought we would be okay
- I gave him the link to the how to support your module; whic
A bit more investigation:
The tests still work for justin; the only difference is between our env was:
- I grabbed the latest system update from Apple - which includes a new
Java update
- I was using Maven 2.1.0
Can anyone else with the above configuration give trunk a go?
Jody
On Sat, Jun 27,
> It would be bad too... anyone with a Mac that can investigate? Jesse? ;-)
I've been building 2.6-SNAPSHOT with and without tests on a mac with JDK 1.5.
But do you only get the errors with your local patched files Jody ?
Michael
-
