John Manko ;
users@netbeans.apache.org
Subject: [EXTERNAL] Re: Converting Java 8 to 17+, conflicts with modules
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
>From my experie
From my experience, minimize your direct Maven dependencies. Try to use
services as much as possible. For example. eclipselink should be a
runtime, not a compile time dependency and should be injected as service:
module-info.java:
requires jakarta.persistence;
uses jakarta.persistence
Hi John.
Check out this site:
https://www.digitalocean.com/community/tutorials/maven-dependency-tree-resolving-conflicts.
It should give you what you need to know.
Regards,
Brad.
On 11/11/23 06:20, John Manko wrote:
This might not be a purely Netbeans issue, but maybe NB has some
tooling to a
This might not be a purely Netbeans issue, but maybe NB has some tooling to
assist, or someone can answer a quick question.
I'm in the middle of converting Java 8 project to Java 17/21 (A little late in
the game, I know! I'm beholden to other forces beyond my control.), and I have
a library mo
