More issues including a logging implementation.
Setting to "<scope>test" in the parent, then adding it as <scope>compile
does not seem to work with some plugins.
On 27/09/18 17:40, Andy Seaborne wrote:
FYI
First attempt didn't work out.
The apache-jena/lib/ didn't have slf4j-log4j or log4j jar files.
This is because these are now "<optional>true" in the parent (JENA-1595)
so apache-jena (the distribution) does not pick them up.
Misspoke.
JENA-1595 was going from "optional" to "<scope>test"
Setting to "<scope>test" in the parent, then adding it as <scope>compile
does not seem to work with some plugins - even when dependency:tree
shows the jars to be :compile, they do not get included the combined war
file. Maybe I haven't got the setting right but my current guess is
that inheritance and dependency interact, with inheritance overriding
dependency. And "<scope>runtime" causes the shade plugin to crash with
an NPE.
At this point, I'll back out JENA-1595 and try to get something working
for the release that is safe, possibly with over some dependency
leakage. After release, I can try other ways of managing the logging
for cmds/war/fulljar and also the tests at the moment they look like
they need time to validate.
Andy
They ought to be not-optional in jena-cmds which does need a definite
choice of logging so it can ensure it is initialized.
The Fuseki module and package changes did work in RDF Delta. It is
change; I don't know of anyone who depends on them as deeply as this
code does although part of the reason for the changes is to enable
better extensibility; RDF Delta is not special.
Andy
On 27/09/18 11:37, ajs6f wrote:
+1
ajs6f
On Sep 27, 2018, at 6:14 AM, Andy Seaborne <a...@apache.org> wrote:
I'm going to start the 3.9.0 release process.
Andy
