maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé BOUTEMY <herve.bout...@free.fr>
Subject Re: Maven Doxia and minimum Java versions
Date Wed, 16 May 2018 05:01:21 GMT
Le mercredi 16 mai 2018, 00:06:43 CEST Gary Gregory a écrit :
> From a user's POV, what I care ATM is being able to build sites with Java 9
> so I can create searchable Javadoc pages...
I like this idea

IMHO, requiring higher Java version to build components is not an issue: what 
is important is to avoid requiring such version for end users

build with Java 9 "-release 7" seems perfect
then being able to build and run maven-site-plugin with Java 7 only

Regards,

Hervé

> 
> Gary
> 
> On Tue, May 15, 2018 at 3:08 PM, Hervé BOUTEMY <herve.boutemy@free.fr>
> 
> wrote:
> > I'm maintaining Doxia and maven-site-plugin for a long time, trying to
> > keep
> > the prerequisites (for end users particularly) as low as possible when I
> > don't
> > have a strong win on upgrading.
> > 
> > Currently, maven-site-plugin (which is what users see, without knowing
> > much
> > about Doxia) requires Java 6 only.
> > With Doxia 1.8 / maven-site-plugin 3.7, in fact, there is a little trick:
> > one
> > Doxia module (Markdown) requires Java 7, because of the library used, and
> > I
> > documented how one can downgrade this module if he strictly require to use
> > maven-site-plugin 3.7 with Java 6.
> > But for sure, when building maven-site-plugin, I didn't try to add a
> > profile
> > to be able to build with Java 6: Java 7 is required to build maven-site-
> > plugin.
> > 
> > Honestly, for Java 6, maven-site-plugin 3.7 is the last version: now it's
> > time
> > to drop it and require Java 7 if you want newer version of the plugin.
> > 
> > Then I'm full ok to upgrade Doxia requirement for Doxia 1.9 and
> > maven-site-
> > plugin 3.8 to Java 7.
> > 
> > 
> > On httpunit, AFAIK it's only for Doxia tests during its build: I don't
> > have
> > any issue with building Doxia with Java 8 to produce jar that require Java
> > 7
> > only.
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le lundi 14 mai 2018, 11:07:39 CEST Graham Leggett a écrit :
> > > 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





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


Mime
View raw message