Conversation
…51ec93 When I went digging into Ivy's code base I discovered that it's been checking if the repository layout pattern ends with M2_PATTERN to use maven-metadata.xml, which for sbt would return false since we customize the mattern - https://github.com/apache/ant-ivy/blob/2.3.0/src/java/org/apache/ivy/plu gins/resolver/IBiblioResolver.java#L497-L499
Member
|
LGTM mod Travis |
Member
Author
|
Patched Ivy is synced to Sonatype - https://oss.sonatype.org/content/repositories/public/org/scala-sbt/ivy/ivy/2.3.0-sbt-c5d1b95fdcc1e1007740ffbecf4eb07abc51ec93/ |
eed3si9n
added a commit
that referenced
this pull request
Jun 26, 2015
Fixes #2005. Bump to ivy 2.3.0-sbt-c5d1b95fdcc1e1007740ffbecf4eb07abc…
eed3si9n
added a commit
that referenced
this pull request
Jun 27, 2015
eed3si9n
added a commit
that referenced
this pull request
Dec 14, 2015
#1520 originally fixed #1514 by reimplementing part of chain resolver to check all resolvers to find the latest snapshot artifacts. This behavior did not work well with Maven repositories where sbt was failing to calculate the correct publication dates. Now that #2075 fixes the Maven integration issue we should enable this flag back again. The build user can opt out by: updateOptions := updateOptions.value.withLatestSnapshots(false)
Duhemm
pushed a commit
to Duhemm/sbt
that referenced
this pull request
Feb 1, 2016
to check all resolvers to find the latest snapshot artifacts. This behavior did not work well with Maven repositories where sbt was failing to calculate the correct publication dates. Now that sbt#2075 fixes the Maven integration issue we should enable this flag back again. The build user can opt out by: updateOptions := updateOptions.value.withLatestSnapshots(false)
eed3si9n
added a commit
to eed3si9n/sbt
that referenced
this pull request
Feb 26, 2016
to check all resolvers to find the latest snapshot artifacts. This behavior did not work well with Maven repositories where sbt was failing to calculate the correct publication dates. Now that sbt#2075 fixes the Maven integration issue we should enable this flag back again. The build user can opt out by: updateOptions := updateOptions.value.withLatestSnapshots(false)
eed3si9n
added a commit
to eed3si9n/sbt
that referenced
this pull request
Feb 26, 2016
to check all resolvers to find the latest snapshot artifacts. This behavior did not work well with Maven repositories where sbt was failing to calculate the correct publication dates. Now that sbt#2075 fixes the Maven integration issue we should enable this flag back again. The build user can opt out by: updateOptions := updateOptions.value.withLatestSnapshots(false)
eed3si9n
added a commit
to eed3si9n/sbt
that referenced
this pull request
Feb 27, 2016
to check all resolvers to find the latest snapshot artifacts. This behavior did not work well with Maven repositories where sbt was failing to calculate the correct publication dates. Now that sbt#2075 fixes the Maven integration issue we should enable this flag back again. The build user can opt out by: updateOptions := updateOptions.value.withLatestSnapshots(false)
eed3si9n
added a commit
to eed3si9n/sbt
that referenced
this pull request
Mar 18, 2016
to check all resolvers to find the latest snapshot artifacts. This behavior did not work well with Maven repositories where sbt was failing to calculate the correct publication dates. Now that sbt#2075 fixes the Maven integration issue we should enable this flag back again. The build user can opt out by: updateOptions := updateOptions.value.withLatestSnapshots(false)
adpi2
pushed a commit
to adpi2/sbt
that referenced
this pull request
Oct 9, 2024
to check all resolvers to find the latest snapshot artifacts. This behavior did not work well with Maven repositories where sbt was failing to calculate the correct publication dates. Now that sbt#2075 fixes the Maven integration issue we should enable this flag back again. The build user can opt out by: updateOptions := updateOptions.value.withLatestSnapshots(false)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #2005, #679
Ref sbt/ivy#13
This PR is pending on https://bintray.com/sbt/maven-releases/ivy/2.3.0-sbt-c5d1b95fdcc1e1007740ffbecf4eb07abc51ec93/view getting on Maven Central. Currently waiting on Bintray request to push it into JCenter.
I discovered that Ivy has been
checking if the repository layout pattern ends with M2_PATTERN to use
maven-metadata.xml, which for sbt would return false since we customize
the pattern -
https://github.com/apache/ant-ivy/blob/2.3.0/src/java/org/apache/ivy/plugins/resolver/IBiblioResolver.java#L497-L499
/review @dwijnand, @jsuereth