launcher | Application launcher | Runtime Evironment library

As per documentation, SpringApplication converts any command line option arguments (that is, arguments starting with --, such as --server.port=9000) to a property and adds them to the Spring Environment.

-D works when running via maven. Try: java -jar application.jar --spring.config.location=file:///C://your//path//config.yml.

Via maven: mvn spring-boot:run -Dspring.config.location="file:///C://your//path//config.yml"

You are violating the JPA spec by accessing the persistence context in a lifecycle listener.

See the JPA Specification 4.2 Section 3.5.2

In general, the lifecycle method of a portable application should not invoke EntityManager or query operations, access other entity instances, or modify relationships within the same persistence context. A lifecycle callback method may modify the non-relationship state of the entity on which it is invoked.

"a portable application should not" is the specification way of saying: Don't do that, anything might happen. Maybe the world ends.

The fix is not to do that. Maybe be preloading the currently logged in user and reference it so you may access it in your entity listener and do not set a reference to the user, but simple store its id or similar.

As it was described in the reference:

When creating the NavHostFragment using FragmentContainerView or if manually adding the NavHostFragment to your activity via a FragmentTransaction, attempting to retrieve the NavController in onCreate() of an Activity via Navigation.findNavController(Activity, @IdRes int) will fail. You should retrieve the NavController directly from the NavHostFragment instead.

Looks like you should use

The log shows that the ResourcesPlugin is being found but its plug-in activator is getting a null pointer exception when it tries to get the IContentTypeManager.

The content type manager is provided using OSGi declarative services but you have not included org.apache.felix.scr which deals with this.

So at a minimum you need to include org.apache.felix.scr and start it in the section:

the latest library guide does not contain any "credentials" in the configuration. try removing this piece at all, it shouldn't be there

Just realized what the issue was: don't use http://mylittleserver.com as host but just mylittleserver.com - that fixes it!

On macOS (same should be true for other platforms AFAIK), when one right- clicks a file and chooses "open with -> Application", the application will be fired up and the path to the file will be given as an argument.

This is not the case for application bundles on macOS. You have to use the startup notification API. This also works for single instance mode on Windows and Linux, where only the first invocation will pass the file path as an argument to the main method.

The startup listener API uses java.awt.Desktop.setOpenFileHandler under the hood which only works if you register a file association. From the documentation on that method:

Please note that for Mac OS, notifications are only sent if the Java app is a bundled application, with a CFBundleDocumentTypes array present in its Info.plist.

For a method to add a file association for all file types, see this blog post:

https://www.cocoanetics.com/2013/01/open-in-all-files/

In the launcher wizard, under Executable info-> macOS options, you can add an arbitrary fragment to the Info.plist file.

match each only works if the right-hand-side is a JSON array - which is clearly not the case here.

On January 15, 2020 the Maven Central repository disabled access through HTTP (cf. Sonatype blog).

While recent version of Maven have the correct URL for Maven Central in their Super POM older ones might still use the HTTP URL. Upgrade your Maven installation or check whether your didn't override the Maven Central repository in your settings.xml file.

The repository configuration should look like this: