Jody Garnett wrote:0
> Today however I am stuck on a JAI error message (the usually RangeSet
> failure that indicates JAI is unhappy as covered by our Developers
> Docs). Problem is I have not changed my development environment at all,
> the test passes in eclipse ... it seems to be that we are
Andrea Aime wrote:
> We can try a few options, before calling the trunk on trunk experiment
> failed and go back to the old way of doing things.
> One would be to build a sort of "hall of shame" with a score that
> goes up for each developer that breaks the build.
> Another is stronger, but I guess
Well I am shamed right now.
But I still need help figuring out where this JAI break occurred from ...
Talking to Justin he has it building better with the "nojai" profile
(just added the docs to the root pom.xml), and is now stuck on some CRS
failure - I am going to follow in his footsteps and h
Justin Deoliveira ha scritto:
> Activating the nojai profile makes it go away. But this leads to more
> problems in the referencing module. The following tests fail:
>
> testEnvelopeTransformation(org.geotools.referencing.CrsTest)
>
> testTransverseMercator(org.geotools.referencing.operation.pr
Jody Garnett wrote:
> I best back out my work from yesterday ... and see if we can isolate
> what caused this JAI problem.
Peculiar indeed...
I've rolled back to r25003 but still get:
modules/library/metadata/target/surefire-reports/org.geotools.factory.GeoToolsTest.txt
Thanks Justin ...
I best back out my work from yesterday ... and see if we can isolate
what caused this JAI problem.
Jody
Justin Deoliveira wrote:
> Activating the nojai profile makes it go away. But this leads to more
> problems in the referencing module. The following tests fail:
>
> testEnv
Activating the nojai profile makes it go away. But this leads to more
problems in the referencing module. The following tests fail:
testEnvelopeTransformation(org.geotools.referencing.CrsTest)
testTransverseMercator(org.geotools.referencing.operation.projection.SouthOrientedTest)
testKrovak(or
I can verify the RangeSet problem, on my local box and our build server.
Jody Garnett wrote:
> So here is the deal - yesterday evening I went to build trunk ...
>
> And found that Manven 2.0.5 was required! (Cory has now backed out that
> change)
>
> I however screwed up I committed the my code
So here is the deal - yesterday evening I went to build trunk ...
And found that Manven 2.0.5 was required! (Cory has now backed out that
change)
I however screwed up I committed the my code in modules/library/
And have since found out that the epsg-wkt plugin is unhappy with my
changes.
