Page 2 of 2 FirstFirst 12
Results 11 to 12 of 12

Thread: Maven issue with Spring Data Neo4j 2.0.0.RELEASE

  1. #11
    Join Date
    Jan 2009
    Location
    Huntington Beach, CA
    Posts
    718

    Default

    Quote Originally Posted by Oliver Gierke View Post
    The easiest way of getting the snapshots pulled is removing the snapshot repository. That way the snapshot dependencies should not be considered during dependency resolution. If this is not possible because you rely on snapshots of other libraries make sure you declare each and every spring dependency that gets pulled in explicitly in your pom fixing the version to your desired one (3.1.0 or 3.0.7)
    I had had to do the same. removing the snapshot and milestone repositories from my pom file, which had then led me to the issue I Jira'd about from this thread.

    If I had the milestone and snapshot repositories in my pom file, it downloaded all pom files for all versions, including all snapshots and all milestones of Spring from 3.0 up to 3.1. Which led to at least 15 of them. Wasn't a pretty site, so I removed the two repos and I don't have that problem anymore.

    Mark

  2. #12
    Join Date
    Jan 2009
    Location
    Huntington Beach, CA
    Posts
    718

    Default

    The maven problem downloading all the Milestone and snapshots from 3.0.7 to 3.1.1 happens if you try to build the samples too.

    Mark

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •