Hi,
I've been looking a bit at Justin's work, so far so good!.
What I wanted to do was to alter the cite tests scripts so that they
would output
the contents of the target/VERSION.txt file contained in the zip files, so that
we can know exactly what was used in successfull tests.
Does not look like anything hard, but the cite tests output caught my
attention...
http://hudson.opengeo.org/hudson/view/cite/job/cite-wfs-1.1/208/console
...
GeoServer is online
Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad
version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:621)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
/home/tomcat/cite/tools
cp target/sessions/session.xml.wfs-1.1.0 users/geoserver/wfs-1.1.0/session.xml
cp: cannot create regular file
`users/geoserver/wfs-1.1.0/session.xml': No such file or directory
RETURN=0
Pinging GeoServer at http://localhost:11010/geoserver
curl: (7) couldn't connect to host
GeoServer is offline
Finished: SUCCESS
Err... success... not quite 
It seems there is some mismatch between the java version used to compile
and the one used to run... something 
(either the cite engine or geoserver)
The file that is running the tests is this one:
http://hudson.opengeo.org/hudson/view/cite/job/cite-wfs-1.1/ws/run.sh
As far as I can see all that's needed is a
cat geoserver/VERSION.TXT
to make it output all the revision numbers in Hudson console output.
Btw, looking into the generated jars I see the geotools jar MANIFEST.MF
reports the svn revision number:
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: tomcat
Build-Jdk: 1.5.0_22
Build-Timestamp: 19-Nov-2010 02:31
Project-Version: 2.7-SNAPSHOT
Svn-Revision: 36347
Class-Path: gt-data-2.7-SNAPSHOT.jar gt-main-2.7-SNAPSHOT.jar gt-api-2
.7-SNAPSHOT.jar jts-1.11.jar xercesImpl-2.7.1.jar gt-referencing-2.7-
SNAPSHOT.jar vecmath-1.3.2.jar commons-pool-1.5.4.jar gt-metadata-2.7
-SNAPSHOT.jar geoapi-2.3-M1.jar jsr-275-1.0-beta-2.jar geoapi-pending
-2.3-M1.jar jdom-1.0.jar
but the geoserver ones do not contain the
same customizations and basically contain only the standard maven generated
items:
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven
Built-By: tomcat
Build-Jdk: 1.5.0_22
Is this intended? Did not follow closely, maybe the GS build process
introduces some difficulties in customizing the jar file contents?
Anyways, some hiccups here and there but it seems once fixed we would be
in the position of saying "aah, revision x of geotools + revision y of geoserver
are release worthy, let's tag, package and release them!"
Well done!
Cheers
Andrea
-----------------------------------------------------
Ing. Andrea Aime
Senior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584962313
fax: +39 0584962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-----------------------------------------------------