yea, that is my idea On Dec 28, 2012, at 2:44 PM, Olivier Lamy <ol...@apache.org> wrote:
> Nope > Thanks to take care of that !! > I just wonder if you will add stuff in various folders ? /plugins /shared > etc... > > -- > Olivier > Le 28 déc. 2012 19:09, "Benson Margulies" <bimargul...@gmail.com> a écrit : > >> Anyone else have any input to this? If not, I'll start copying things >> here and there soon. >> >> >> >> On Fri, Dec 21, 2012 at 9:43 PM, Benson Margulies <bimargul...@gmail.com> >> wrote: >>> Absolutely, positively, only source-releases. Those are the only >>> things that the Foundation sees as 'releases' and wants on /dist. >>> >>> I've started to cook up some python code to grab them all from nexus; >>> so far I can tell you that all the source-releases of all the plugins >>> amount to 65728461 bytes of storage. >>> >>> As for people other than us, the policy this: whatever you build, and >>> whatever convenience binaries you care to make, you must prepare a >>> conforming, buildable, source package (like our source-release) and >>> you must put it on /dist. >>> >>> >>> On Fri, Dec 21, 2012 at 7:22 PM, Brett Porter <br...@apache.org> wrote: >>>> >>>> On 22/12/2012, at 9:46 AM, Olivier Lamy <ol...@apache.org> wrote: >>>> >>>>> 2012/12/21 Benson Margulies <bimargul...@gmail.com>: >>>>>> Dear fellow community members, >>>>>> >>>>>> Discussions today have made it clear, to me at least, that we're >>>>>> missing a step in the release procedures for plugins and component >>>>>> (indeed, for everything except 'core' releases). >>>>>> >>>>>> The step is to copy the official release package (the source-release >>>>>> artifact) to the Apache dist hierarchy, in some fashion compatible >>>>>> with svnpubsub. >>>>> funny to have to put a source-relase for a pom .... >>>>> Does it mean all artifacts deployed to maven central need to have a >>>>> source-release in /dist ? >>>>> Only source-release or more ? (fun to have those duplicate in my local >>>>> maven repo and in the directory I will use to checkout this /dist) >>>> >>>> I think the source release would suffice (and we don't necessarily need >> to push that to r.a.o if it's not useful). >>>> >>>> For the POM, I'd say we can probably just push the file itself. >>>> >>>>> >>>>> How other ASF projects will do ? Yes Benson this doesn't concern only >>>>> Maven plugins etc... >>>>> I think about some which produce osgi bundle from other projects >>>>> (sample >> http://repo.maven.apache.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.commons-io/1.4_3/ >>>>> so all those bundles need to be /dist or this one >> http://repo.maven.apache.org/maven2/org/apache/directory/studio/org.apache.commons.lang/2.6/ >>>>> ) >>>>> Do they need to do it too ? >> http://sling.apache.org/site/release-management.html#ReleaseManagement-PromotingtheRelease >>>> >>>> - Brett >>>> >>>> -- >>>> Brett Porter >>>> br...@apache.org >>>> http://brettporter.wordpress.com/ >>>> http://au.linkedin.com/in/brettporter >>>> http://twitter.com/brettporter >>>> >>>> >>>> >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>>> For additional commands, e-mail: dev-h...@maven.apache.org >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
