Hi,
finally managed to make both GeoTools and GeoServer build on OpenJDK7,
as a result the OpenJDK7 has been setup to start sending mails out to the
“extra builds” mailing lists:
https://groups.google.com/forum/#!forum/geoserver-extra-builds
https://groups.google.com/forum/#!forum/geotools-extra-builds
Btw, the windows build server has started to pay its dividends, the feature collection
cleanup patches missed an important bit to close some feature iterators,
both the gt2 and geoserver builds on Windows immediately started to crap out about
the issue and we were able to locate and fix it.
The OpenJDK7 will be useful instead for catching misuse of Treeset and
for tests that have execution order dependencies (that is, the work if you
run methodA, methodB, methodC, but fail if you run methodB, methodC, methodA)
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On 18/11/12 22:20, Andrea Aime wrote:
The OpenJDK7 will be useful instead for catching misuse of Treeset and
for tests that have execution order dependencies (that is, the work if you
run methodA, methodB, methodC, but fail if you run methodB, methodC,
methodA)
Great work, Andrea, much appreciated.
For extra credit, surefire:test also has the runOrder flag for running tests in alternating forward and reverse order or random order, and forkMode+threadCount for multithreaded testing to break weak code. Because these flags make builds even more unstable, they are not always a appropriate, but might be interesting for *-extra-builds.
Kind regards,
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
On Mon, Nov 19, 2012 at 7:35 AM, Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com> wrote:
On 18/11/12 22:20, Andrea Aime wrote:
The OpenJDK7 will be useful instead for catching misuse of Treeset and
for tests that have execution order dependencies (that is, the work if you
run methodA, methodB, methodC, but fail if you run methodB, methodC,
methodA)
Great work, Andrea, much appreciated.
For extra credit, surefire:test also has the runOrder flag for running tests in alternating forward and reverse order or random order, and forkMode+threadCount for multithreaded testing to break weak code. Because these flags make builds even more unstable, they are not always a appropriate, but might be interesting for *-extra-builds.
I am game enabling random test order provided someone will help me fix the resulting issues 
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it