Skip to content

Fix for sbt/sbt#1933#2258

Merged
eed3si9n merged 2 commits intosbt:0.13from
Duhemm:fix-1933
Nov 10, 2015
Merged

Fix for sbt/sbt#1933#2258
eed3si9n merged 2 commits intosbt:0.13from
Duhemm:fix-1933

Conversation

@Duhemm
Copy link
Contributor

@Duhemm Duhemm commented Oct 28, 2015

sbt was reporting warning abouts inconsistent versions of dependencies
even if these dependencies didn't have the same configuration (as in
provided vs compile).

This commit fixes this problem by comparing the dependencies by
organization, artifact name and configuration.

Fixes #1933

sbt was reporting warning abouts inconsistent versions of dependencies
even if these dependencies didn't have the same configuration (as in
`provided` vs `compile`).

This commit fixes this problem by comparing the dependencies by
organization, artifact name and configuration.

Fixes sbt#1933
@typesafe-tools
Copy link

Can one of the admins verify this patch?

@dwijnand
Copy link
Member

Nice!

Should this target 0.13? Also, would be great to have release notes for this.

@Duhemm
Copy link
Contributor Author

Duhemm commented Oct 28, 2015

Good catch! I just added the notes.

I think @eed3si9n would like to release a 0.13.10 at some point

@eed3si9n
Copy link
Member

I was thinking about 0.13.10 but it may or may not happen.

eed3si9n added a commit that referenced this pull request Nov 10, 2015
@eed3si9n eed3si9n merged commit 8603e24 into sbt:0.13 Nov 10, 2015
@eed3si9n
Copy link
Member

@Duhemm Could you send the same PR to sbt/librarymanagement?

Duhemm added a commit to Duhemm/librarymanagement that referenced this pull request Nov 11, 2015
(This is a port of sbt/sbt#2258)

sbt was reporting warning abouts inconsistent versions of dependencies
even if these dependencies didn't have the same configuration (as in
`provided` vs `compile`).

This commit fixes this problem by comparing the dependencies by
organization, artifact name and configuration.
@max-voloshyn
Copy link

Thanks for the fix! Is there any plans to release sbt version with this fix or ability to use this fix via brew?

@dwijnand
Copy link
Member

dwijnand commented Jan 3, 2016

@max-voloshin See @eed3si9n's very recent answer: #2256 (comment)

@max-voloshyn
Copy link

@dwijnand thanks!

@Duhemm Duhemm deleted the fix-1933 branch February 8, 2016 08:29
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.

5 participants