On Fri, 10 Apr 2026 19:44:26 GMT, Marius Hanl <[email protected]> wrote:
> This PR is based on: https://github.com/openjdk/jfx/pull/1970 > The last commit of this PR can already be reviewed, but this PR will only be > merged after the previous PR was merged. > > This is the continuation of the split of the Maven publishing. > Since the `build.gradle` file had become so large, adding more Maven code was > out of the question in the past. > Thanks to the split, we can now quickly and easily add support for JavaFX > Sources, thereby significantly simplifying testing. > > This can be tested by: > > `./gradlew publishToMavenLocal -PMAVEN_PUBLISH=true -PMAVEN_VERSION=custom` > > This will create a JavaFX version named 'custom' in your `.m2` folder (under > `.m2/org/openjfx/javafx-XXX/custom`) > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai). I tested publishing to the local Maven repository on Windows with and without the MAVEN_VERSION parameter. It worked as expected. The POMs and JARs, including the sources, were copied into the Maven repository. If the MAVEN_VERSION parameter was supplied on the command line, this version was used for the Maven artifacts. Step 1: ./gradlew clean sdk javadoc Step 2.a: ./gradlew -PMAVEN_PUBLISH=true publishToMavenLocal Step 2.b: ./gradlew -PMAVEN_PUBLISH=true -PMAVEN_VERSION=XXX publishToMavenLocal **Just a notice** the javadocs are not copied to the Maven repository I plan to test it further and report if I find anything. @Maran23: Thank you for your efforts. ------------- PR Comment: https://git.openjdk.org/jfx/pull/2144#issuecomment-4236235056
