Hi Justin! thanks, that helped on fixing the problem, very appreciated!
In other (non) ASF projects, I followed the rule to not have SNAPSHOT dependencies - or, at least, the current SNAPSHOT... not sure if that would help on having that issue fixed, I should spend some time on investigation... All the best! -Simo http://people.apache.org/~simonetripodi/ http://twitter.com/simonetripodi On Wed, Jan 29, 2014 at 3:12 PM, Justin Edelson <[email protected]>wrote: > Hi Simo, > TL;DR - manually change that dependency to 1.0.1-SNAPSHOT > > Longer: > This always happens when we are mid-release of a new module. Trunk > points to the next snapshot, but other modules point to the last > snapshot. We can't update the dependencies to the release version as > the release isn't promoted yet, so we have to switch to the next > snapshot (and then switch back to the release version). Any > suggestions on how to improve this? > > Justin > > On Wed, Jan 29, 2014 at 9:03 AM, Simone Tripodi > <[email protected]> wrote: > > Hi all, > > > > I completely dropped the local chache of mvn artifacts > > (~/.m2/repository/org/apache/sling/) and checked out sling trunk > r1562439, > > while reinstalling the build I stumbled on the error below. > > Do I need to checkout other modules from a different location? > > > > TIA, all the best! > > -Simo > > > > [ERROR] Failed to execute goal on project org.apache.sling.jcr.base: > Could > > not resolve dependencies for project > > org.apache.sling:org.apache.sling.jcr.base:bundle:2.1.3-SNAPSHOT: Failure > > to find > > org.apache.sling:org.apache.sling.serviceusermapper:jar:0.0.1-SNAPSHOT in > > http://repository.apache.org/snapshots was cached in the local > repository, > > resolution will not be reattempted until the update interval of > > apache.snapshots has elapsed or updates are forced -> [Help 1] > > > > http://people.apache.org/~simonetripodi/ > > http://twitter.com/simonetripodi >
