I'm sorry being short at the first.
In general specifying version in build is a bad practice. The version is
not a property of a build process, as long as you have the code in hand
you should keep that "versionless". Version is a property of the release
process.
The build process shall be merely responsible to create an executable
(reusable) package from the source code.
The release process shall be responsible to:
1. Get a specific source code
2. Assign a version to the release
3. Create a versioned executable (reusable) package using the build
process
4. Tag the sources
5. Upload the versioned packages to a binary repository for further use
Due to some initial technical limitation Maven made version a required
part of their build. That would result a lot of workarounds to put in
place, like SNAPSHOT versions, a specific step in maven projects to
change the version in each and every pom.xml in the project before
release, etc.
In Gradle version is optional.
The best use of the version property is:
./gradlew -Pversion=1.2.3 clean build
when the release comes.
OpenJFX project had a problem with it as they generated second precision
version for their artifacts, so when the dependencies were resolved in
different times they would reference different jars, so NetBeans was not
able to connect the dependencies between modules with versions crested a
few seconds apart.
I would check the project properties for classpath.
Also make sure that the Tools > Options > Java > Gradle > Experimental >
Enable 'lazy' Source Group Initialization is turned off.
You may test NetBeans 12.5-beta1
On 8/20/21 10:43 PM, Andreas Reichel wrote:
Greetings.
On Fri, 2021-08-20 at 18:52 -0700, Laszlo Kishalmi wrote:
Try to get rid of the version specification.
I have tried that just because I am desperate and ready to grab any straw.
Unfortunately it did not change anything -- and why should it.
What you are doing there is a bad practice.
Says who and why. Please elaborate.
Best regards
Andreas
