implementation & api dependencies don't copy

[nhajratw]

Newer gradle versions recommend using the implementation or api keywords instead of compile and runtime. Unfortunately, the plugin doesn't seem to pick up dependencies declared in that way.

https://docs.gradle.org/current/userguide/dependency_management_for_java_projects.html

[nintha]

Yep, generateApplicationManifest creates full files , but generateNativeInstaller only copys fxlauncher.jar to bundle.

Now, I use javapackager like it:

javapackager -deploy -native -outdir build -srcdir build/fxlauncher -appclass fxlauncher.Launcher -outfile myapp -name myapp -title myapp -vendor nintha

the batch can instead of generateNativeInstaller after run generateApplicationManifest.

Good luck

[TurekBot]

The CopyAppDependenciesTask is really short and sweet, so this shouldn't be too hard, right?

I'm a total noob when it comes to groovy, but it seems this might be fixed on this line:

project.configurations.runtime.resolvedConfiguration.resolvedArtifacts.each { artifact ->

Here's something helpful!

https://docs.gradle.org/current/userguide/java_library_plugin.html#sec:java_library_configurations_graph

Maybe this is something to be scheduled for version 2.0 when we break other things, too.

[TurekBot]

Ooh!

Maybe we can solve this using the default configuration!

Here's who lead me to that answer.

[nhajratw]

i can't tell what default configuration does -- from the graph though, it seems like runtimeElements is the correct one...

[TurekBot]

@nhajratw, I'm not sure, but according to this guy

the default configuration extendsFrom runtime, runtimeOnly, implementation