Hi, The artifacts of the first Sling release are now also available through central.
Regards Felix Bertrand Delacretaz schrieb: > Hi Ian, > > On Thu, Jun 11, 2009 at 11:59 PM, Ian Boston<i...@tfd.co.uk> wrote: >> ...I have a jar that depends on >> org.apache.sling:org.apache.sling.engine:jar:2.0.4-incubator, which since >> its released I think is a "reasonable" thing to do... > > Of course. > >> . But if you clean out >> your maven repo (rm -rf ~/.m2/repository/org/apache/sling ) and build you >> find the build fails with a dependency path of: >> ... >> 5) org.apache.sling:org.apache.sling.commons.osgi:jar:2.0.2-incubator >> >> and no 5 doesnt exist in the repo. see [1] >> >> There is a simple solution to this, force the versions of those releases >> that are missing to versions that are not, but that a) feels dangerous and >> b) creates a maintenance headache >> >> >> A quick scan of the repo1 looks like *all* the 202 versions have gone >> missing from the repo, perhaps they were never there ? > > That's correct, the artifacts of the first Sling release are in > > http://people.apache.org/repo/m2-incubating-repository/org/apache/sling/org.apache.sling.commons.osgi/ > > for example, so currently you need to add that repository to your > setup, as described in > http://incubator.apache.org/sling/site/getting-and-building-sling.html > > Now, considering that since our first release the incubator voted [2] > to allow podlings to deploy to the main Maven repository, I think we > should make the whole > http://people.apache.org/repo/m2-incubating-repository/org/apache/sling/ > available on repo1.maven.org. What do people think? And how do we do > that, is there a way to copy the whole thing at once? > > -Bertrand > >> [1] >> http://repo1.maven.org/maven2/org/apache/sling/org.apache.sling.commons.osgi/ > > [2] https://issues.apache.org/jira/browse/INCUBATOR-82 >
