Yes, thank you, but I know that. My project is still on 8.x path until I
migrate to Jakarta EE.
But for the sake of a reproducible test case, it doesn't matter if TomEE
9.x or 10.x, it just have to be at least 9.x so that the source level is
greater than 8.
The web application doesn't have to do anything. Just create the
project, open it in Netbeans and wait... the lines with "Even though the
source level of ....." will start coming into the messages.log file of
Netbeans.
cu
Jens
Am 06.06.2025 um 17:23 schrieb Maciej Jaros:
You should use Tomcat 9. T10 is not compatible with non-jakarta apps.
https://tomcat.apache.org/whichversion.html#:~:text=Tomcat%209%20is%20the%20last%20major%20Tomcat%20version%20supporting%20Java%20EE
There is conversion tool if you want to try Jakarta (converts
imports), but as you probably know that probably also requires
upgrading Spring, Hibernate etc and probably rewriting most of DAO and
Security...
Cheers,
Maciej Nux
Jens Zurawski (2025-06-06 14:45):
Oh, I can give a simple test case :-)
- just take a freshly installed NB 26 (or at least with a new and
empty userdir),
- create new Project "Java with Maven -> Web Application"
- assign a server (I'm using a TomEE 10.01 installation with Jakarta
EE 10)
- save project
wait some seconds, and et voila, in the message.log you can see:
INFO [org.netbeans.ui.maven.project]: A Maven project was opened. Appending the
project's packaging type.
INFO [org.netbeans.ui.metrics.maven]: USG_PROJECT_OPEN_MAVEN
INFO [org.netbeans.ui.metrics.projects]: USG_PROJECT_OPEN
INFO [org.netbeans.ui.indexing]: Indexing finished, indexing took 942 ms.
INFO [org.netbeans.ui.indexing]: Indexing started, time from last indexing 0 ms.
INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Resolving
dependencies took: 36 ms
Even though the source level of
E:\test\Netbeans\mavenproject1\src\main\java;E:\test\Netbeans\mavenproject1\src\main\webapp;E:\test\Netbeans\mavenproject1\src\main\resources
is set to: 11, java.util.zip.CRC32C cannot be found on the system module path:
WARNING [null]: Last record repeated 6 more times.
WARNING [null]: Last record repeated 2 more times.
Nothing else has to be done to get these lines (at least on my system)
Hope this helps?
cu
Jens
Am 06.06.2025 um 14:27 schrieb Jens Zurawski:
Sadly, this doesn't help either.
I've also tried with a complete fresh NB 26 without importing
settings from old installations. Still the messages are coming.
Unfortunately I'm currently not able to produce a simple test case
to reproduce this with a simple maven application.
Anything I can provide to give more insight?
cu
Jens
Am 06.06.2025 um 13:50 schrieb Neil C Smith:
On Fri, 6 Jun 2025 at 12:28, Jens Zurawski<j...@diegurus.de> wrote:
<artifactId>maven-compiler-plugin</artifactId>
<version>3.14.0</version>
<configuration>
<source>17</source>
<target>17</target>
<compilerArguments>
<endorseddirs>${endorsed.dir}</endorseddirs>
</compilerArguments>
</configuration>
Possibly try changing that to just
<configuration>
<release>17</release>
</configuration>
Endorsed dirs isn't supported by JDK 9+, so I wonder if this is
causing the messages.
Best wishes,
Neil
