Announcement Announcement Module
Collapse
No announcement yet.
Spring Data JPA 1.1.2.RELEASE depends on spring-core 3.2.0-SNAPSHOT Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Spring Data JPA 1.1.2.RELEASE depends on spring-core 3.2.0-SNAPSHOT

    Hi,
    I am using spring-data-jpa 1.1.2.RELEASE in a project which does not have any <repository> definition for any kind of Spring related repositories. However, I'm still getting spring-core 3.2.0-SNAPSHOT in my dependencies from spring-data-jpa (if I don't manually override it). This leads to a lot of redundant dependency definitions for a lot of spring artifacts which should be explicitly defined - only to fix the versions and not use snapshots.
    I'm seeing this repository defined in the spring-data-jpa pom:
    Code:
    <repository>
       <id>spring-libs-snapshot</id>
       <url>http://repo.springsource.org/libs-snapshot</url>
    </repository>
    Also, when I build, I'm seeing:
    Code:
    Downloaded: http://repo.springsource.org/libs-sn...n-metadata.xml (375 B at 0.9 KB/sec)
    So it's relatively clear that this is indeed the repository being used.
    The pom.xml is this: https://raw.github.com/eugenp/REST/master/sec/pom.xml (also has a parent pom).
    This may be the reason for which the ${spring.version.range} is resolved to whatever is latest, including SNAPSHOT artifacts.
    Can someone please confirm this - I'd like to open a JIRA to track this one, as it is problematic and entirely unnecessary.
    Thanks.
    Eugen.
    Last edited by eugenparaschiv; Sep 30th, 2012, 10:12 AM. Reason: added code tags and additional details

  • #2
    Hello

    1) Use code tags
    2) could you share your pom.xml configuration?

    Comment


    • #3
      Thanks for the feedback.
      I have added the additional details.
      Eugen.

      Comment

      Working...
      X