Skip to content

Exclude overlap in dependency jars #255

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

Merged
merged 1 commit into from
Jun 1, 2020
Merged

Exclude overlap in dependency jars #255

merged 1 commit into from
Jun 1, 2020

Conversation

IceBlizz6
Copy link
Contributor

@oliemansm
Hello again, sry that i haven't been responsive lately after the last pull request.
Work got chaotic after the COVID situation.

I would like to present a more immediate fix to the underlying problem in this pull request.
The goal of this PR is not to make the project itself into modules, but rather to make it compatible with the module system.

Projects that are not made into modules can still be used by modules because they will normally be converted into automatic modules.

With graphql-java-servlet this is not possible (atleast not without heavy configuration) because of the overlapping classes/packages in the jar files that throw this process off.

#244
I go into details here on how the problem looks like with the current jar files and how this bnd edit will resolve conflicting packages.

I originally wanted to take it one step further (making this project itself into modules), but for the short term we should focus on making it compatible.

Exclude overlapping classes in jar files
@oliemansm
Copy link
Member

@IceBlizz6 That is indeed the more important issue to fix, thanks!

@oliemansm oliemansm merged commit 263fc86 into graphql-java-kickstart:master Jun 1, 2020
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