just 0,02 E. :
- if you have multiple JDK
- give a try to maven toolchain mechanism
so every project can have the right set of java tools
(e.g. compiling for an ancient jdk not supported anymore on recent javac).
Cheers,
Davide
(31 javac on \develop\java - none of then "truly" installed -
I suspect that would work with Maven, but our projects are using Ant qand
there it's using the project.properties file and build.xml/build-impl.xml.
For those it's easy to set the project to use the ""JDK_1.8" defined java
platform, but it's not easy to do this in a global way, since the actual
de
If I understand you correctly.
This is what I do then I know the jdk dependencies for the particular
project.
pom.xml
I have copied and pasted relevant pom.xml tags for you to look at.
create a pom.xml template for across the board uniformity.
1.8
1.8
maven-compiler-pl
I agree that projects should explicitly state the JDK platform to use.
The problem is if I define a Java Platform through Tools->Java Platforms
(e.g. JDK 1.8), this ends up being defined in build.properties in the
NetBeans userdir (%APPDATA%\Roaming\NetBeans\12.2).
That means all developers and o
I think you guys are barking up the wrong tree with defaulting.
For each project you should individualise instead of using default because
each project is individual, so you are assured of same libraries and
config environment
.This will reduce the risk of incompatibility issues between developme
