An alternative is to downgrade git-commit-id-plugin to a 2.1.x that 
works with Maven 3.0.x, if such a version exists.

Kind regards,
Ben.

On 20/03/16 12:58, Ben Caradoc-Davies wrote:
> Ooh, I broke GeoSolutions (Maven 3.0.5) as well. Sorry about that.
>
> Would you guys prefer to upgrade Maven (and make Maven 3.1.1+ a hard
> requirement) or should I revert my pom changes?
>
> Kind regards,
> Ben.
>
> On 20/03/16 12:24, Ben Caradoc-Davies wrote:
>> OK, so I have broken all the builds (master, 2.8.x, and 2.7.x). We can
>> either:
>>
>> (1) upgrade ares to Maven 3.1.1 or later (requires Boundless assistance
>> (I use and recommend Maven 3.3.9 (latest stable))), or
>>
>> (2) downgrade git-commit-id-plugin to 2.0.4 and build nightlies with
>> -Xmx2048m
>>
>> No good deed goes unpunished.
>>
>> Kind regards,
>> Ben.
>>
>> On 20/03/16 11:52, Ben Caradoc-Davies wrote:
>>> Concurrent git-commit-id-plugin looks like the culprit. Local tests
>>> suggest upgrading from 2.0.4 to 2.2.0 (with major jgit dependency
>>> version upgrade) fixes the problem.
>>
>

-- 
Ben Caradoc-Davies <[email protected]>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to