Hi Daniele,
don't know if you already solved this, but anyhow... I had the same issue
and tracked it down to a conflict in the xml-apis dependency.
I sorted it out in gs-main's pom.xml like this:
org.geoserver
gs-ows
xml-apis
xml-apis
xml-apis
On Mon, Oct 19, 2015 at 10:06 AM, Stefano Costa <
stefano.co...@geo-solutions.it> wrote:
> I have not done a full build to confirm this change doesn't break anything
> else: if it doesn't break the build, might be worth to make a permanent fix?
>
Looks like a good plan to me
Cheers
Andrea
--
+1 from me too :)
On Mon, Oct 19, 2015 at 10:17 AM, Andrea Aime
wrote:
> On Mon, Oct 19, 2015 at 10:06 AM, Stefano Costa <
> stefano.co...@geo-solutions.it> wrote:
>
>> I have not done a full build to confirm this change doesn't break
>> anything else: if it
After playing with this for a while, I realized it was enough to specify
the xml-apis version in the dependencyManagement section of the parent POM.
PR is here:
https://github.com/geoserver/geoserver/pull/1275
On Mon, Oct 19, 2015 at 12:12 PM, Daniele Romagnoli <
Hi List,
while checking all requirements for GSIP-134 (sufficient test coverage to
migrate module from community to extension) I run the cobertura plugin on
the modules and I got several errors/exceptions.
Before starting investigating on issues in these modules I simply did a
"mvn