Avoid remote import in XSL file

[gunnarmorling]

In https://github.com/pressgang/pressgang-tools/blob/master/pressgang-xslt-ns/src/main/resources/xslt/org/jboss/pressgang/xhtml.xsl there is a remote import to another XSL file on SourceForge. Ideally, this should be replaced with a local copy of that file to avoid issues during outages as the recent SF downtime.

[ge0ffrey]

jdocbook-core (which is used by the maven and gradle plugin) automatically do that: they notice the url, replace it with their local copy (if the versions match!) and do not use the internet to build.
That being said, there were issues with that: but I know it works well with the latest maven plugin, the latest pressgang tools, etc. See the pressgangs-tools-example here, or the optaplanner-docs build (which inherits from kie-parent-metadata).

[gunnarmorling]

Thanks for your reply, Geoffrey! We had at least one case where this didn't work as per @hferentschik's report: http://lists.jboss.org/pipermail/hibernate-dev/2015-July/013117.html. Maybe we are not on the latest versions, though. Need to check that.

[hferentschik]

FYI, this was part of the ORM documentation build. This uses the gradle docbook plugin - https://github.com/gradle/gradle-jdocbook which in turn seems to use version 1.1.0 of jdocbook-core - https://github.com/gradle/gradle-jdocbook/blob/master/build.gradle#L58. Would that version be obsolete? Maybe it is a question of upgrading the version used in the gradle plugin?

[ge0ffrey]

The gradle plugin should define the jdcobook-core version, your pom only need to use the correct (=latest) gradle plugin version and presggang-* version, to make sure to have a combination that works offline.

[ge0ffrey]

cc @psiroky

[hferentschik]

FYI - gradle/gradle-jdocbook#21

[ge0ffrey]

Thanks, Closing the issue on this side.