`runShadow` task does not work if using `shadow` configuration for external libs #94

johnrengelman opened this Issue Sep 8, 2014 · 1 comment


None yet
1 participant

johnrengelman commented Sep 8, 2014

The runShadow task is using the output of the shadowJar task as the argument to java -jar .... This resolves to a path in build/libs but that is not where the shadow configuration jars are copied to. Thus, any dependent libraries (like encryption libraries) are not available.

Instead, runShadow should depend on installShadowApp since that task will write the -all jar and the dependent jars from the shadow configuration to the build/installShadow/<project-name>/lib directory and the argument path should be in the location in that directory. That way, dependent jars that are included in the manifest Class-Path attribute will be in their correct relative locations.

@johnrengelman johnrengelman added the bug label Sep 8, 2014

@johnrengelman johnrengelman added this to the 1.1.2 milestone Sep 8, 2014


This comment has been minimized.

Show comment
Hide comment

johnrengelman commented Sep 9, 2014

Fixed by 79d5d35

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment