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

Default Spring Data JPA RELEASE versions depend on spring-core SNAPSHOT versions [DATAJPA-258] #671

Closed
spring-projects-issues opened this issue Oct 3, 2012 · 0 comments
Assignees
Labels
type: bug A general bug

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Oct 3, 2012

Eugen Paraschiv opened DATAJPA-258 and commented

It looks like spring-data-jpa 1.1.2.RELEASE depends on spring-core 3.2.0-SNAPSHOT. The reason is the <repository> definition from spring-data-jpa itself:

<repository>
   <id>spring-libs-snapshot</id>
   <url>http://repo.springsource.org/libs-snapshot</url>
</repository>

This makes the ranged version to simply pick up the latest it finds, which, with the repository enabled, are the SNAPSHOT versions
The relevant build output is:

Downloaded: http://repo.springsource.org/libs-sn...n-metadata.xml (375 B at 0.9 KB/sec)

A quick solution should be to remove the snapshot repository from the pom of spring-data-jpa (which would make sense). Another possible solution would be to not use ranged versions, but that should not be necessary once the snapshot repository definition is removed.


Affects: 1.1.2

Referenced from: commits b0efce1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

No branches or pull requests

2 participants