So off to the geoserver codebase next?
--
Jody Garnett
On 5 February 2015 at 08:58, Torben Barsballe tbarsba...@boundlessgeo.com
wrote:
Thanks Jody, that seems to have been it. mvn dependency:resolve-plugins
accounts for versions 2.1, 2.4, and (not previously observed) 2.5.
Torben
On Wed,
Thanks Jody, that seems to have been it. mvn dependency:resolve-plugins
accounts for versions 2.1, 2.4, and (not previously observed) 2.5.
Torben
On Wed, Feb 4, 2015 at 8:48 PM, Jody Garnett jody.garn...@gmail.com wrote:
I am going to guess that the other versions were downloaded as a part of
On Wed, Feb 4, 2015 at 8:02 PM, Torben Barsballe
tbarsba...@boundlessgeo.com wrote:
I am working on uppdating the commons-lang dependancy in geoserver (for
https://jira.codehaus.org/browse/GEOS-6868), and am starting with the
geotools commons-lang dependancies.
It looks like GeoTools
I am working on uppdating the commons-lang dependancy in geoserver (for
https://jira.codehaus.org/browse/GEOS-6868), and am starting with the
geotools commons-lang dependancies.
It looks like GeoTools currently pulls in several versions of commons-lang
(2.1, 2.3, 2.4) via transitive dependancies.
I am going to guess that the other versions were downloaded as a part of a
plugin.
You could use mvn dependency:resolve-plugins to check?
--
Jody Garnett
On 4 February 2015 at 17:05, Torben Barsballe tbarsba...@boundlessgeo.com
wrote:
I have dug into this deeper, and it appears that the top
I have dug into this deeper, and it appears that the top level geotools pom
is downloading a number of different versions of commons-lang, but is only
using the declared version. I have no idea why these extra versions are
being downloaded but not used.
Specifically, the following artifacts are
