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

Better range resolve #120

Merged
merged 1 commit into from May 11, 2015
Merged

Conversation

mkristian
Copy link
Contributor

No description provided.

@@ -14,7 +14,7 @@ apply from: 'gradle/integration-tests.gradle'


group = 'com.github.jruby-gradle'
version = '0.1.16'
version = '0.1.17'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The version out already is 0.1.17, this should be 0.1.18 at least

gradle just picks the latest and newest version when there are conflicting
versions ranges regardless whether it obeys the involved ranges or not.

this patch tries obey ranges. if there is no overlap between two ranges for the
same gem then it fails. the second range the same gem will be narrowed down to
the intersection of the first and second range.

it still can fail but now you can fix things be reordering you dependencies a bit
for most cases.
@rtyler
Copy link
Member

rtyler commented May 11, 2015

Looks great dude! Thanks for dading such informative comments

@rtyler rtyler added this to the 0.1.18 milestone May 11, 2015
rtyler pushed a commit that referenced this pull request May 11, 2015
@rtyler rtyler merged commit 3737ba4 into jruby-gradle:master May 11, 2015
@tommysullivan
Copy link

yay

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

Successfully merging this pull request may close these issues.

None yet

4 participants