[ARCH-67] Update the java version property in generated pom files Created: 25/Mar/19 Updated: 08/Mar/21 Resolved: 08/Mar/21 |
|
| Status: | Closed |
| Project: | Archetypes |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | Richard Gange | Assignee: | Unassigned |
| Resolution: | Resolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
Java 8:
Maybe update it to 10? |
| Comments |
| Comment by Mikaël Geljić [ 25/Mar/19 ] |
|
Java version in pom files is both used for source—compiling according to a certain language level—and target version, which bytecode level is generated (hence which lowest-compatible Java runtime you can use). We still want to keep Magnolia compatible with Java 8 runtime for the short-term at least. JDK 11 is not adopted that fast atm, it will take a bit more time to stabilize. Regarding JDK support & updates, it's mostly about where Magnolia runs. It runs on Java 11, so then the ball is on users' side. Of course, module developer may freely upgrade javaVersion in the pom file according to his/her needs, target JRE, etc. |
| Comment by Richard Gange [ 25/Mar/19 ] |
|
As far as I knew you can compile and run Magnolia on Java 10. Keeping Magnolia compatible with Java 8 makes sense. I was just suggesting that it might be time to update the property. At some point we will need to do that so at least we have the issue recorded. |
| Comment by Mikaël Geljić [ 25/Mar/19 ] |
|
Build-time compatibility highly depends on the module; which 3rd-party libs, testing libraries, maven plugins it uses. |
| Comment by Richard Gange [ 08/Mar/21 ] |
|
Cont'd on BUILD-303 |