Sigh… just after i hit go on the release announcements 
It looks like hudson did indeed complain:
http://hudson.opengeo.org/hudson/job/geoserver-2.2.x/79/
This is my bad… i grabbed a revision with this issue and the release scripts don’t run tests (maybe they should).
Anyways, that said, it looks like this wasn’t an actual bug? Just an issue with tests? So no need to rebuild artifacts or anything?
I agree it is annoying to note have 2.2 build, if you want me to cherry pick the change onto the release branch on the server and retag it i can.
On Fri, Sep 21, 2012 at 7:42 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:
Hi,
I was building the 2.2.0 tag (cause I needed those jars for another project)
and found out the wms module fails to build due to the changes
occurred in GEOT-4263 (which is also in geotools 8.2)
I fixed those on trunk (it’s a regexp that needs to be changed inside a zip
file for a mosaic test) and the build went fine.
I did not think about backporting it, but wondering, why in the world
Hudson did not complain?
If people try to checkout and build 2.2 it will fail, which does not look too good…
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
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.