Did we get a Java 9 branch started? Seems like most of the issues are
around tooling not functionality of the product. If this is the case I
would expect the differences between the java9 branch and the master to be
contained in the pom.xml files.
On Wed, Oct 18, 2017 at 2:20 AM, Andy Seaborne
Claude - you can see branches that exist via the GH interface.
And, no, theer isn't one.
There is a jenkins job - it does not work, waiting in updates to roll
through. Taking over version mgt of the plugins from the ASF parent
seems to me like extra work for little benefit.
Unless there is
Not really an immediate need so much as just wondering how close our code
is to working under Java 9. I think it would also be nice to know when the
various tools we use are Java 9 ready and perhaps lend them a hand if need
be. More curiosity than anything else.
Claude
On Fri, Oct 20, 2017 at 3
Who manages the ASF parent pom.xml? INFRA? Perhaps we can help move it forward?
ajs6f
Claude Warren wrote on 10/20/17 11:18 PM:
Not really an immediate need so much as just wondering how close our code
is to working under Java 9. I think it would also be nice to know when the
various tools we
Apache Commons, I think.
Not INFRA.
On 21/10/17 04:13, aj...@apache.org wrote:
Who manages the ASF parent pom.xml? INFRA? Perhaps we can help move it
forward?
ajs6f
Claude Warren wrote on 10/20/17 11:18 PM:
Not really an immediate need so much as just wondering how close our code
is to wo
Jena, the codebase, passes the Java9 inspection tool so a release shoudl
run find with Java9.
It's just the maven build system that's lagging.
Working out where that is at would be a great help.
Andy
On 20/10/17 22:18, Claude Warren wrote:
Not really an immediate need so much as just won
