Skip to content
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

Shadow jar #184

Merged
merged 4 commits into from
Oct 22, 2021
Merged

Shadow jar #184

merged 4 commits into from
Oct 22, 2021

Conversation

kkocel
Copy link
Contributor

@kkocel kkocel commented Jul 6, 2021

This will shadow plugin dependencies, preventing them from clashing with other plugins that depend on grgit / jgit.

This hurts this library since people are forced to choose one lib instead of using two - see: allegro/axion-release-plugin#357 (comment)

@tha2015
Copy link
Collaborator

tha2015 commented Jul 20, 2021

Thanks for the PR. I deployed to my local maven repository (using ./gradlew clean publishToMavenLocal, verified the generated pom.xml file, and found the generated pom.xml still contains the dependency. Do you think it is an issue or it will be gone when deploying to remote repository?

@kkocel
Copy link
Contributor Author

kkocel commented Jul 20, 2021

@tha2015 please note that dependency is inruntimescope. So it should not be an issue.
Generated jar has dependencies shadowed and bundled:

Screenshot 2021-07-20 at 11 38 56

Anyway, I asked if runtime dependency is required: GradleUp/shadow#694

@tha2015
Copy link
Collaborator

tha2015 commented Jul 20, 2021

It is a good thing that this plugin will not be impacted by other plugins because it will use the repackaged dependencies only. But I guess the runtime dependency might still have some impact to other plugins which sharing the same dependency but with an older version?

@kkocel
Copy link
Contributor Author

kkocel commented Jul 20, 2021

I guess that in such cases version resolution will kick in. Many other plugins are shadowing their dependencies in order to avoid such situations. ihmo after this PR situation will be better than before.

@kkocel
Copy link
Contributor Author

kkocel commented Jul 22, 2021

@tha2015 I asked question on SO how to get rid of dependency: https://stackoverflow.com/questions/68470193/exclude-dependency-from-pom-using-maven-publish-plugin

@kkocel
Copy link
Contributor Author

kkocel commented Jul 26, 2021

@tha2015 I added the configuration that disables runtime dependencies from pom and module.json

@kkocel
Copy link
Contributor Author

kkocel commented Oct 22, 2021

@tha2015 I made all the changes requested. Can this PR be merged?

@tha2015
Copy link
Collaborator

tha2015 commented Oct 22, 2021

@tha2015 I made all the changes requested. Can this PR be merged?

Hi @kkocel ,
Very sorry for the delay and thanks for your patience. I've been super busy lately but everything is better now. I will release it soon.
Thanks,
Thai

@tha2015 tha2015 merged commit 8bd1bf4 into n0mer:master Oct 22, 2021
@kkocel
Copy link
Contributor Author

kkocel commented Nov 23, 2021

@tha2015 @n0mer Kindly ask when you plan to create a new release?

@tha2015
Copy link
Collaborator

tha2015 commented Nov 23, 2021 via email

@tha2015
Copy link
Collaborator

tha2015 commented Feb 7, 2022

Hi @kkocel ,
FYI. Version 2.4.0 has been released with this PR. Thanks for your patience.
-Thai

@kkocel
Copy link
Contributor Author

kkocel commented Feb 7, 2022

thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants