All great advice. I was able to solve the compile issue using the following,
but I'll need to refine my deps and module declarations. Each of these were
added explicitly because they're used, include several classes/packages from
org.eclipse.persistence.*.
jakarta.inject
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
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
