Re: Make our first release available on central Maven repo? (was: Problems with dependency paths)
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 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 >
Re: Make our first release available on central Maven repo? (was: Problems with dependency paths)
Hi, Jukka Zitting schrieb: > Hi, > > On Fri, Jun 12, 2009 at 8:46 AM, Felix Meschberger wrote: >> My first try to would be to checkout the Sling 3 tag and deploy it to >> repository.apache.org setting the altDeploymentRepository property >> appropriately. > > I'd rather not do that, as then we'd have separate copies of the same > artifacts with different checksums and signatures. Yeah, right. Thanks for the reminder. > > We could ask the people at reposit...@apache.org to copy the existing > artifacts from p.a.o to r.a.o. Will do that. Regards Felix
Re: Make our first release available on central Maven repo? (was: Problems with dependency paths)
Hi, On Fri, Jun 12, 2009 at 8:46 AM, Felix Meschberger wrote: > My first try to would be to checkout the Sling 3 tag and deploy it to > repository.apache.org setting the altDeploymentRepository property > appropriately. I'd rather not do that, as then we'd have separate copies of the same artifacts with different checksums and signatures. We could ask the people at reposit...@apache.org to copy the existing artifacts from p.a.o to r.a.o. BR, Jukka Zitting
Re: Make our first release available on central Maven repo? (was: Problems with dependency paths)
On 12 Jun 2009, at 07:37, Bertrand Delacretaz wrote: 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/ Ahh, ok thanks, Ian
Re: Make our first release available on central Maven repo? (was: Problems with dependency paths)
Felix Meschberger wrote: > Hi, > > Yes at the time of our first release poddlings had to deploy to the > incubator repository at > >http://people.apache.org/repo/m2-incubating-repository > > And, yes, I agree we should probably deploy this to central, now. > Central being managed through the Nexus repository nowadays, it would > probably be easiest to see how to deploy to there. > > My first try to would be to checkout the Sling 3 tag and deploy it to > repository.apache.org setting the altDeploymentRepository property > appropriately. > > Carsten, would that be correct ? > Yes, that should do the trick. The tag has externals to the released modules. Good idea! Carsten -- Carsten Ziegeler cziege...@apache.org
Re: Make our first release available on central Maven repo? (was: Problems with dependency paths)
Hi, Yes at the time of our first release poddlings had to deploy to the incubator repository at http://people.apache.org/repo/m2-incubating-repository And, yes, I agree we should probably deploy this to central, now. Central being managed through the Nexus repository nowadays, it would probably be easiest to see how to deploy to there. My first try to would be to checkout the Sling 3 tag and deploy it to repository.apache.org setting the altDeploymentRepository property appropriately. Carsten, would that be correct ? Regards Felix Bertrand Delacretaz schrieb: > Hi Ian, > > On Thu, Jun 11, 2009 at 11:59 PM, Ian Boston 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 >
Make our first release available on central Maven repo? (was: Problems with dependency paths)
Hi Ian, On Thu, Jun 11, 2009 at 11:59 PM, Ian Boston 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
