The build schedule is the following
geoserver-trunk,geoserver-2.x, geotools-trunk, geotools-2.6.x with
java 5 and java 6,32 and 64 bit giving a total of 16 build attempts
(mostly unsuccessful) every day.
SUN SDK is used Monday and Thirsday
IBM SDK is used Tuesday and Friday
OPEN JDK (only jav
On 14/09/10 13:59, Andrea Aime wrote:
> Sigh, that was my fault, sorry.
> Was on a notebook on foss4g and only had java 6, did not notice.
> I assumed the build bot would catch any issue, but it did not happen.
This was bound to happen to developers making many commits. :-)
> Btw, dreaming aloud
On 14/09/10 20:03, Justin Deoliveira wrote:
> Ben any chance we can get your builtbot to email the developer list when a
> build fails? It would be nice in cases like these where the primary build
> server misses stuff. Although I admit you serve has a pretty effective proxy
> for your build bot
Very strange. I remember setting up the new hudson to use java 5 for the
builds. But looking now that config is gone... Anyways, minus the demons on
the build server playing tricks on me the intention has always been to
compile java 5 as our baseline. So I will change it back.
Ben any chance we ca
Ben Caradoc-Davies ha scritto:
> The GeoTools trunk build has been failing under Java 5 since r36183 when
> the Java 6 API was used in:
> modules/library/render/src/main/java/org/geotools/renderer/style/ShapeMarkFactory.java
>
> This was a trivial API change: Java 6 added methods taking double ar
The GeoTools trunk build has been failing under Java 5 since r36183 when
the Java 6 API was used in:
modules/library/render/src/main/java/org/geotools/renderer/style/ShapeMarkFactory.java
This was a trivial API change: Java 6 added methods taking double args.
The fix was similarly trivia (conver
