Opened 15 months ago

Closed 15 months ago

Last modified 15 months ago

#2181 closed defect (invalid)

JCP and Jetty are outdated inside I2P

Reported by: anonymous maybe Owned by:
Priority: minor Milestone: undecided
Component: unspecified Version: 0.9.33
Keywords: Cc:
Parent Tickets:

Description

JCP latest version:-

https://jcp.org/aboutJava/communityprocess/final/jsr369/index.html

Jetty latest version:-

https://www.eclipse.org/jetty/download.html

while inside I2P:-

 I2P version:	0.9.33-0-1ubuntu1
Java version:	Oracle Corporation 1.8.0_151 (OpenJDK Runtime Environment 1.8.0_151-8u151-b12-1-b12)
Wrapper version:	3.5.30
Server version:	9.2.23.v20171218
Servlet version:	Jasper JSP 2.3 Engine
JSTL version:	standard-taglib 1.2.5
Platform:	Linux amd64 4.9.56-21.pvops.qubes.x86_64
Jcpuid version:	3
Processor:	Haswell Core i3/i5/i7 model 60 (coreihwl)
Jbigi:	Locally optimized native BigInteger library loaded from file
Jbigi version:	4
GMP version:	6.1.2
Encoding:	UTF-8
Charset:	UTF-8
  • Server version: 9.2.23.v20171218
  • Servlet version: Jasper JSP 2.3 Engine

Subtickets

Change History (2)

comment:1 Changed 15 months ago by anonymous maybe

ZZZ replied in IRC chat regarding This Ticket:-

<zzz> the jcp link you posted is to a specification, not to software.
<zzz> and re: jetty, they move very quickly, and each new series is incompatible. The 9.2.x branch just recently went EOL, no need to panic
<zzz> also, we can't move to 9.4, because it isn't in debian yet afaik
<zzz> you can't just find the highest version of something and then yell 'panic, you're out of date'. It's a lot more complex than that

so i will close it as invalid

Last edited 15 months ago by anonymous maybe (previous) (diff)

comment:2 Changed 15 months ago by anonymous maybe

  • Resolution set to invalid
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.