[
https://issues.apache.org/jira/browse/MARCHETYPES-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17798526#comment-17798526
]
ASF GitHub Bot commented on MARCHETYPES-76:
-------------------------------------------
judovana commented on PR #18:
URL: https://github.com/apache/maven-archetypes/pull/18#issuecomment-1862469353
> And why do we need to move all the tests back to 1.7 ?
Well the default is now 1.8, it soudned liek nonsense to keep "bump" to 1.8.
There is already test which demonstrate that you can bump it up from default
(to 11), to modular jdk,
The renamed test was demonstrating bump up, to non modular jdk. Unluckily
there is no more non-mudular jdks when jumping up, so I kept the test to
demonstrates that you can still use legacy 1.7, non modular if you insists.
Considering the next minimal JDK with next LTS will be some JDK12 or so, the
test down, to non modular jdk will be still valid.
If you have nay issues, I will revert the test change, or adjsut.
> maven-archetype-quickstart generates EOLed maven.compiler setup
> ----------------------------------------------------------------
>
> Key: MARCHETYPES-76
> URL: https://issues.apache.org/jira/browse/MARCHETYPES-76
> Project: Maven Archetype Bundles
> Issue Type: Bug
> Reporter: jiri vanek
> Priority: Major
>
> The default imput to #compilerProperties is 1.7, which is making any
> generated project to be not buildable with fresh jdk21. The default should
> be1.8. Where jdk8 is still live and jdk21 is still comaptible with it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
