maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Osipov <micha...@apache.org>
Subject Re: Maven Doxia and minimum Java versions
Date Tue, 15 May 2018 18:24:11 GMT
Am 2018-05-14 um 13:46 schrieb Stephen Connolly:
> Currently Maven core is 1.7 minimum...
> 
> I'd like to bump that to 1.8... but that's another story

By bumping I would require someone to make use of Java 8 features. 
Otherwise it is a useless contraint for everyone out there.

> On 14 May 2018 at 10:07, Graham Leggett <minfrin@sharp.fm> wrote:
> 
>> Hi all,
>>
>> I would like to clarify what the policy is on maven-doxia and the maven
>> project in general, and minimum java versions.
>>
>> With the XHTML5 work on Doxia, I have managed to keep all changes without
>> a requirement to upgrade any dependencies, until I got to
>> maven-doxia-sitetools and httpunit, which doesn’t understand any HTML5
>> tags. My current workaround is to simply test that HTML5 tags are present,
>> but ignore their type, and this seems good enough for now - no httpunit
>> upgrade needed.
>>
>> Upgrading httpunit to a version that supports HTML5 and doesn’t suffer
>> from bug https://sourceforge.net/p/htmlunit/bugs/1961/ means a minimum
>> java version of v1.8.
>>
>> What is the policy on java versions in maven-doxia? Is it intentionally
>> kept behind the curve so old code can be built, or is it acceptable to make
>> java 1.8 a minimum version?
>>
>> Regards,
>> Graham
>> —
>>
>>
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message