I'd need to take a closer look, was there an issue in JIRA you've found that describes this, or could you file it?
Thanks, Brett On 19/05/2011, at 11:53 AM, Not Zippy wrote: > I was contrasting the behavior to prove the scan did indeed hit the > artifacts folder but did not create the maven-metadata.xml file. I did try > to manually place the maven-metadata.xml in the artifacts folder but a scan > did not update that file either. So to summarize: > > (Check box to create maven metadata file is checked on the server) > Scan to update maven-metadata.xml file - results FAIL > Scan to create maven-metadata.xml file - result FAIL > Publish using IVY ant task did not create maven-metadata.xml. > Publish through archiva's web interface did not create maven-metadata.xml. > > The server is running on a windows machine. This is an upgraded server from > 1.3.1 upgrade process was to copy the conf and data folder onto the new > version. > > Thanks > nz > > On Wed, May 18, 2011 at 8:42 PM, Brett Porter <br...@apache.org> wrote: > >> Sorry, I may be confused - you were referring to maven-metadata.xml, not >> the checksums - or are you just contrasting the behaviour? >> >> Do the metadata files exist and are not updated, or they do not exist? >> >> On 19/05/2011, at 11:33 AM, Not Zippy wrote: >> >>> No that doesn't work either - although if I delete the md5 files they are >>> recreated with a scan >>> >>> nz >>> >>> On Wed, May 18, 2011 at 7:15 PM, Brett Porter <br...@apache.org> wrote: >>> >>>> I recall someone else mentioning this, but I can't find an associated >> MRM >>>> ticket. >>>> >>>> Does re-scanning with the "scan all artifacts" checkbox ticked fix it, >> once >>>> it completes? >>>> >>>> - Brett >>>> >>>> On 19/05/2011, at 12:44 AM, Not Zippy wrote: >>>> >>>>> I just upgraded from 1.3.1 to 1.3.4 when this problem started to occur. >>>>> Before it worked through the web interface and using the ant task from >>>> ivy. >>>>> Now neither generate the maven-metadata.xml file. >>>>> I thought the repository scanner would try to fix create the >>>>> maven-metadata.xml, but it does not either (metadata-updater is >> enabled). >>>>> >>>>> >>>>> >>>>> On Tue, May 17, 2011 at 4:06 PM, Chris Mylonas <ch...@opencsta.org> >>>> wrote: >>>>> >>>>>> Hi Not Zippy, >>>>>> >>>>>> I had this problem with 1.3.1. Couldn't diagnose it, but it went >> away. >>>>>> Initially I had uploaded my jar through the web interface. >>>>>> >>>>>> To rectify the problem, I made it a maven task and the problem went >>>> away. >>>>>> >>>>>> HTH >>>>>> >>>>>> On 18/05/2011, at 1:03 AM, Not Zippy wrote: >>>>>> >>>>>>> The maven-metadata.xml is not generated or updated when using archiva >>>>>> 1.3.4, >>>>>>> anyone have a possible fix for this ? >>>>>>> >>>>>>> thx >>>>>> >>>>>> >>>> >>>> -- >>>> Brett Porter >>>> br...@apache.org >>>> http://brettporter.wordpress.com/ >>>> http://au.linkedin.com/in/brettporter >>>> >>>> >>>> >>>> >>>> >> >> -- >> Brett Porter >> br...@apache.org >> http://brettporter.wordpress.com/ >> http://au.linkedin.com/in/brettporter >> >> >> >> >> -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter
