Modify ↓

Opened 4 weeks ago

Last modified 2 days ago

#24941 new enhancement

[patch] Compile JMapViewer as Java 11 target

Reported by: gaben Owned by: team
Priority: normal Milestone: 26.12
Component: JMapViewer Version:
Keywords: java11 Cc: stoecker

Description

I realised that JMapViewer is still being compiled as a Java 8 target. Should I update it to Java 11, given that the Java 17 update is imminent? Or should I leave it as it is and switch to Java 17 once the core switch has been implemented? Or should it stay at Java 8?

This would tidy up the build scripts, as there are some hacks for pre-Java 11. E.g. the two-pass compile in Ant.

Attachments (1)

24941-1-java11.patch​ (192.9 KB ) - added by gaben 2 weeks ago.
Java 11 bump plus cleanup, Maven _should be_ (fingers crossed) as good as Ant

Download all attachments as: .zip

Change History (5)

comment:1 by stoecker, 4 weeks ago

I'd vote for Java 11.

by gaben, 2 weeks ago

Attachment: 24941-1-java11.patch​ added

Java 11 bump plus cleanup, Maven _should be_ (fingers crossed) as good as Ant

comment:2 by gaben, 2 weeks ago

Keywords: java11 added
Summary: Compile JMapViewer as Java 11 target → [patch] Compile JMapViewer as Java 11 target

comment:3 by gaben, 2 weeks ago

Milestone: → 26.11

comment:4 by stoecker, 2 days ago

Milestone: 26.11 → 26.12

Milestone renamed

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user.
Next status will be 'needinfo'. The owner will be changed from team to gaben.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from team to anonymous. Next status will be 'assigned'.

Add Comment
E-mail address and name can be saved in the Preferences .
Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.