Given this is potentially public facing server stuff, the security
updates flowing into Java7 also suggest moving to that version for Fuseki.
I've just updated Fuseki2 to Jetty9 and hence Java7.
Andy
On 07/02/14 14:46, Stephen Allen wrote:
I would say make the leap to Java 7. I'd have to think most people are
using it now (or they can start using it).
-Stephen
On Fri, Feb 7, 2014 at 9:10 AM, Andy Seaborne <[email protected]> wrote:
Jetty 9 and Tomcat 8 require Java7.
I'm wondering if for Fuseki(2) might we well go for Java7.
Fuseki1 is only delivered as a self-contained server but Fuseki2 has
WAR-style deployment. Tomcat 6 & 7 still running on Java6 (which is not a
good idea from a security point of view) might be the issue.
http://tomcat.apache.org/whichversion.html
http://wiki.eclipse.org/Jetty/Starting/Jetty_Version_Comparison_Table
Thoughts?
Andy
On 07/02/14 10:17, Andy Seaborne wrote:
Should we upgrade the versions of common dependences?
A check shows these are behind:
httpcomponents: 4.2.3 -> 4.2.6 (see JENA-576 about 4.3.*)
slf4j: 1.6.4 -> 1.7.6
log4j: 1.2.16 -> 1.2.17
jetty: 8.1.11 -> 8.1.14
lucene: 4.3.1 -> 4.6.1
solr 4.3.1 -> 4.6.1
spatial4j: 0.3 -> 0.4
commons-fileupload: 1.2.2 -> 1.3
For Jetty, Fuseki2 would be the time to move to the 9.1.* series.
anything else?
xerces and Junit are up-to-date.
Andy
