Skip to content

Maven Dependency Improvements #502

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
May 11, 2018
Merged

Maven Dependency Improvements #502

merged 1 commit into from
May 11, 2018

Conversation

nebhale
Copy link
Member

@nebhale nebhale commented May 11, 2018

Previously, an update the build system resulted in the Maven dependencies being aggressively calculated, before each project add dependencies to itself. This change updates the ordering of this calculation such that it happens after each project configures itself. In addition, this change goes through each project and ensures that the dependencies are scoped appropriately in order to achieve the a minimal and accurate Maven POM.

Sample of the generated POMs

Previously, an update the build system resulted in the Maven dependencies
being aggressively calculated, before each project add dependencies to itself.
This change updates the ordering of this calculation such that it happens
after each project configures itself.  In addition, this change goes through
each project and ensures that the dependencies are scoped appropriately in
order to achieve the a minimal and accurate Maven POM.

[#463][#498]
@rdegnan rdegnan merged commit bf14aa3 into rsocket:1.0.x May 11, 2018
@nebhale nebhale deleted the 498-maven-dependencies branch May 11, 2018 19:21
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