On Dec 14, 2007 5:47 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > > Niall Pemberton wrote: > > On Dec 14, 2007 4:31 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote: > >> Niall Pemberton wrote: > >>> On Dec 14, 2007 2:53 PM, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > >>>> On 12/14/07, Niall Pemberton <[EMAIL PROTECTED]> 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. > >> Fixing the meta data is important and not that difficult to do. Just > >> edit the maven-metadata.xml file and create new checksums. If you are > >> unsure how to do it I can do it for you. > > > > Thanks Dennis - I've created an updated copy here: > > > > http://people.apache.org/~niallp/temp/ > > > > If you could have a quick look that would be great. I saw in the > > snapshot metadata a <release> element - does it need that and if so > > for what versions (e.g. just 2 or 1.0 as well)? > > I had a look at other meta data files and they have both "latest" and > "release" tags. I believe that they are used by Maven and other repo > tools to determine the latest and released version respectively. > > So I recommend adding the following as the first entries within the > "versioning" tag. > > <latest>2</latest> > <release>2</release> > > Also an sha1 checksum should be added.
Thanks Dennis - updated versions: http://people.apache.org/~niallp/skin-meta/ Niall > > > > Niall > > > >>> Niall > >>> > >>>> -Rahul > >>>> > >>>> > >>>>> Niall > >>>>> > >>>>> [1] > >>>>> http://repo1.maven.org/maven2/org/apache/commons/commons-skin/maven-metadata.xml > >>>>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >> > >> -- > >> Dennis Lundberg > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Dennis Lundberg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
