Hi,
what I gather from the poll is that nobody is still using
an old version of SVN client, and actually everybody but me
is on 1.6.
So I guess it's possible to use the relative externals that
Ben was proposing, in order to get the maintenance benefit
he cited (no need to maintain those when we cut a branch or
we do branched development).
Is there any other concern left against this change?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
I think it will be quite welcome. Thanks to you guys to seeing it through.
Andrea Aime wrote:
Hi,
what I gather from the poll is that nobody is still using
an old version of SVN client, and actually everybody but me
is on 1.6.
So I guess it's possible to use the relative externals that
Ben was proposing, in order to get the maintenance benefit
he cited (no need to maintain those when we cut a branch or
we do branched development).
Is there any other concern left against this change?
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
On 12/11/09 01:21, Andrea Aime wrote:
Is there any other concern left against this change?
Is the OpenGeo Hudson using svn 1.5 or later?
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
Ben Caradoc-Davies ha scritto:
On 12/11/09 01:21, Andrea Aime wrote:
Is there any other concern left against this change?
Is the OpenGeo Hudson using svn 1.5 or later?
Very good question. Hudson is using its own SVN plugin,
version 1.6, which uses a pure java svn client:
http://wiki.hudson-ci.org/display/HUDSON/Subversion+Plugin
Looking at the server is seems the following jar is in use:
/WEB-INF/lib/svnkit-1.3.0-hudson-2.jar
which according to this page:
http://svnkit.com/download.php
supports all features of svn 1.6.2.
I guess there is an easy way to make sure:
add a new relative link just for the sake of testing,
commit, look at what happens on the build server by inspecting the
console output of the first build.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
There being no objections, and given the large maintenance benefits, I have converted all internal svn:externals to the svn >=1.5 relative format on 2.0.x and trunk. This means that an svn client of version 1.5 or later, or compatible, is required to checkout GeoServer.
This change was applied in r13650 on 2.0.x and r13651 on trunk.
There is still one absolute external: app-schema test-data from GeoTools. I should document the need to update this for every branch/tag, although in practice updating on branches is most important, as the tag is typically close to head of branch when we build it. Because it is an extension, you should make the maintainer fix it. 
Kind regards,
Ben.
On 12/11/09 01:21, Andrea Aime wrote:
Hi,
what I gather from the poll is that nobody is still using
an old version of SVN client, and actually everybody but me
is on 1.6.
So I guess it's possible to use the relative externals that
Ben was proposing, in order to get the maintenance benefit
he cited (no need to maintain those when we cut a branch or
we do branched development).
Is there any other concern left against this change?
Cheers
Andrea
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia