javapackager drop-in resources classpath

[TurekBot]

I've used the javapackager in other projects before, so I'd like to say I kind of know what I'm talking about—kind of.

The idea is convention over configuration. You put the drop-in resources in a certain spot and if they're where the javapackager expects them, it uses them instead of the default.

It appears, however, that the fxlauncher-gradle-plugin is missing an important step mentioned in the javapackager documentation: setting up the classpath (to match the gradle project structure).

In the documentation there's an example of setting up the classpath with an Ant task. We just need to do it with gradle... right?

I'm under the impression that putting the package directory right in the root of the project goes against the gradle project structure. But I'm closer to a gradle noob than I am a gradle expert. @aalmiray, you know a thing or two. Can you weigh in on where the package directory should be?

In the javafx-gradle-plugin, they've configured it to sit right next to the java directory

│    
└───src
    ├───main
    │   ├───deploy
    │   │   └───package
    │   │       └───windows
    │   ├───java
    │   └───resources
    └───test
        ├───java
        └───resources

To conform to how a gradle project should be, is that right? Or should it be elsewhere?

[TurekBot]

Any thoughts on this?