We\'re trying to build a client jar that includes unpacked dependent jar\'s. And the manifest should have class-path
entries to the dependent jars. T
Indeed, assembling using jar-with-dependencies
causes maven to unpack all the dependencies as ${assembly.dependencySets.dependency.unpack}
is set to true
in the corresponding assembly descriptor.
A simple fix would be to provide an assembly descriptor similar to the jar-with-dependencies.xml
and modify ${assembly.dependencySets.dependency.unpack}
to false
, like this:
EDIT: For an unknown reason, the behavior when using
is not exactly the same and it seems necessary to add
to the fileSet or you don't get the expected result.
uberjar
jar
false
false
runtime
${project.build.outputDirectory}
/