How do I include a jar of a compiled subproject in a maven-capsule?

[fab1an]

I have my project depending on another subproject:

dependencies { compile project(':common') }

If I build a fatcapsule everything works, but if I build a maven-capsule the compiled common.jar is not included in my capsule, only my normal jar is.

[danthegoodman]

Looks like the plugin will have to be taught how to handle project dependencies for the maven capsule. I taught it how to handle file dependencies back in f80bfd4, and something similar should work for projects.

In the mean time, something like this should get you up and going, although I haven't tested it myself:

configurations.create('embedCommon')
dependencies {
  embedCommon project(':common')
}
task capsule(type: MavenCapsule){
  // your other settings go here
  embedConfiguration configurations.embedCommon
}

[thomaseizinger]

Is there a way to transitively only embed project dependencies?

[danthegoodman]

@thomaseizinger I don't quite understand what you're asking. Can you give me an example?

[thomaseizinger]

I have a project with 8 modules. One of them is an executable java application and depends on some of the other modules. These modules in turn depend on libraries from maven central and modules from my own project. (Which are not directly listed as dependency in the executable module, but the executable module of course transitively depends on those modules.)

What I would like to achieve now, is to create a dependency configuration that only contains the direct dependencies of my executable module. I don't want the configuration to include all transitive dependencies, as that would include libraries from maven central. I want capsule to download these upon startup of the application.

The question is, is there a way to create a dependency configuration that only contains non-maven-central dependencies but these transitively?

What I want to avoid is specifying all module dependencies in a separate dependency configuration by hand.