maven-example | example Maven project which uses macros | Build Tool library

mvn exec:java -Dexec.mainClass=com.zenjava.examples.hellojfxmaven.HelloJavaFxAndMavenApp seems to work just fine when I clone the project, build and run it.

From the error message it looks like you have a redundant mvn there (i.e., you've run mvn mvn exec:java -Dexec.mainClass=com.zenjava.examples.hellojfxmaven.HelloJavaFxAndMavenApp. Remove the duplicate mvn and you should be fine.
One possible cause for this I could think of is if you're not running Maven from the command line, but from some tool/IDE. In this case, the tool itself already calls mvn and just expects the arguments (i.e., exec:java -Dexec.mainClass=com.zenjava.examples.hellojfxmaven.HelloJavaFxAndMavenApp).

Ok, I've lost the whole day digging this topic.

Short answer: it's not possible.

You can use add-exports and add-opens to get access to the com.sun.javafx.scene.control.skin.resources, but it will only work if you are not using named modules, in other words, your app must not be modularized.

What you are seeing is the expected behavior of Maven unique snapshots (as written by JF Meier in the comments).
Maven is using a high resolution timestamp to uniquely identify the snapshot version (this is the only supported snapshot type since Maven 3).

By moving the dependency to the top of my pom I was able to eliminate the conflict. Seemed like there was a conflict with the test ng dependencies.

Scala has its own runtime libraries above JVM. A compiled Scala .class has imported some classes from Scala runtime libraries. When you try to run a Scala .class file, you need to append the Scala runtime to the classpath.

If you are running inside IntelliJ IDEA, the Scala Plugin will automatically do this, but when you run java from command line, you should do this yourself.

If you are using Maven, then you can add a . From Scala Docs -> Scala with Maven -> Creating a Jar:

I had some similar issue and I switched to basics. If you are using jfrog(which you should) you can simply use the API(https://www.jfrog.com/confluence/display/RTF/Artifactory+REST+API) and hit it with curl, eg:

curl -u ${username}>:${password}@ -X PUT \"${mavenRepo}/${relativeMavenPath}/${serviceName}/${serviceTag}/${serviceName}-${serviceTag}.jar\" -T ${your-jar-name}.jar

Run this command in the directory where your jar exists.

This has not much to do with the plugin I believe. Module joda.time in your case seems to be an automatic module.

The jlink tool does not support linking of automatic modules because they can rely on the arbitrary content of the classpath, which goes against the idea of a self-contained Java runtime.

So there are two ways to fix this probably :-

• (you don't own the jar) Temporarily go ahead create a module-info.java[you could use jdeps tool for it] and update the jar[using jar tool] with the corresponding compiled class as in projects under Java 9.

• (you own the dependency) Permanently migrate the jar to Java 9 itself, where it would consist of the module-info.class by itself after being compiled and packaged.

NOTE: there is a bug in artifactory 6.5.x, which was resolved in version 6.5.2, that prevents filtered resource to be correctly processed.

${security.getCurrentUsername()} is an usage of a filtered resource, which in artifactory allows to treat text files as filtered via FreeMarker templates.

When you download the settings.xml file in the artifactory UI, the ${security.[]} fields would have been replaced with your currently logged username and encrypted password (if that bug was not present). Because of the bug, or if you copy/paste the text content instead of downloading, the settings.xml will contain those literal unreplaced strings, and maven would not replace them because they do not exist in the maven build context.

As shown in the video you linked, you need to click the download snippet link, instead of copying the text; otherwise, you can copy/paste the text and then you need to type your artifactory username and password in it.

Thanks to JBaruch i realised it should have been: