commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton" <niall.pember...@gmail.com>
Subject Re: [all] Moving staged artifacts (was Re: Release Version 2 of Commons Skin ...)
Date Fri, 14 Dec 2007 15:02:37 GMT
On Dec 14, 2007 2:53 PM, Rahul Akolkar <rahul.akolkar@gmail.com> wrote:
> On 12/14/07, Niall Pemberton <niall.pemberton@gmail.com> wrote:
> <snip/>
> > >
> > > We definitely do not want to sync the entire m2-snap-repo (if thats
> > > possible!). Suggest copying manually (yes, there are downsides etc.,
> > > but its not like its not been done before and this seems to be special
> > > circumstances unless I've missed something or the plugin has been
> > > fixed to copy specific artifacts).
> >
> > OK thanks Rahul - I'll do it manually for now. I guess the one bit
> > that automation makes easier is merging/updating the
> > maven-metadata.xml[1] (and signing/creating keys for it) - are there
> > any other options than a manual edit if I do the rest manually?
> >
> <snap/>
>
> Yup, makes that easier, and the multi-module stuff, if any (as you can
> imagine, there'd be a bunch of artifacts in various directories). You
> really care about the meta-data if you care about repository managers
> etc. (any tools that mine the data). How much do we care about that
> for commons-skin? Is it worth the added effort? If all this worked, I
> wouldn't be asking.
>
> From memory, it wasn't a showstopper when I asked before (e.g. Shale v1.0.4).

OK great - I never really knew what it was for as it seemed to work
when not present - so I'll leave that for now.

Niall

> -Rahul
>
>
> > Niall
> >
> > [1] http://repo1.maven.org/maven2/org/apache/commons/commons-skin/maven-metadata.xml
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message