> Yeah, if you look at the patch it actually modifies the rename script so that
> on the main branch it is never modified. Basically adding a @VERSION@
> placeholder.
>
Understood; we also need to update a few doc references (on the main branch) in
anticipation of the release being a success.
> Anyways, the scripts take this into account, i have just never ran them
> through a full trial to test the commit back but its the same pattern as
> GeoServer and I just cribbed the scripts from there and stripped them down.
So the example pom.xml files in docs/user/tutorials need to reflect the release
version number; and the build/pom.xml and common.py also have a reference.
Jody
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
