-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relocating external dependencies in fat jar #27
Conversation
tomasbjerre
commented
Dec 17, 2016
- To avoid classpath collisions.
This is fine but lets move to Lets do the below instead. Think that should cover all pulled in deps and give a more expected shaded naming convention.
|
So se., ch. and bsh.* should not be relocated? |
I don't see either of those in the |
You are right =) Its not in there! |
Edited the code snippet above to add a |
@@ -1,5 +1,15 @@ | |||
shadowJar { | |||
mergeServiceFiles() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any particular reason you removed this line or just a typo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added it again!
@@ -8,6 +8,8 @@ out | |||
# OS generated files # | |||
###################### | |||
.DS_Store | |||
src/generated | |||
test-output |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume these are maven generated folders? Are you using maven somehow with this project?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That was probably just some files laying around. Originally generated by Eclipse. But I see Eclipse support was removed in fd13b17#diff-c197962302397baf3a4cc36463dce5ea maby you just relocate the libraries yourself?
} | ||
|
||
artifacts { | ||
archives shadowJar |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we including this artifacts
block? Shouldn't be necessary as we already define this within <project-root>/gradle/publishing.gradle
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
* To avoid classpath collisions.
I don't mind you adding in the maven/generated dirs. Can't remember exactly why I ripped that eclipse code out initially but I remember it causing problems within my workspace. In either event: feel free to add the generated dirs to the |
Ok I'll remember it if I need something else changed in this project! But it should be ready to be merged now right? |
Merged. @tomasbjerre thanks for the PR! FYI: not sure if you're looking for a new version to be put out with this change but I planned on doing another release by end of weekend. Waiting for 1 more expected PR to come in from a dev and then will release. |