Am 2018-05-19 um 09:08 schrieb Sylwester Lachiewicz:
Hi,
i checked doxia-sitetools code and looks it will be possible to replace
httpunit with JSoup.
We already use Jsoup in other places and only require Java 7.
This sounds really promising. I love JSoup, used it already several
times. How much is that, can you give an estimate?
Michael
wt., 15 maj 2018 o 23:09 użytkownik Hervé BOUTEMY <[email protected]>
napisał:
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: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
