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 > > > > >
