Yes I have the metadata-updater enabled, using Archiva 1.0.1. Initially in my testing it seemed to be layout-related; the version directory contained one artifact that did not being with the module name. In other words, for artifact /repo/group/foo/1.0/foo-1.0.jar there was also file named /repo/group/foo/1.0/bar.xml, no metadata would get generated in the module dir (in the version dir it always generated without problem). If I removed that bar.xml file and then re-scanned, then the metadata would generate.
I was reproducing this consistently, then I restarted Tomcat and I can't get it to reproduce at all anymore. There must have been something problematic cached in memory. > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 01, 2008 8:21 PM > To: archiva-users@maven.apache.org > Subject: Re: Archiva not generating maven-metadata for > available revisions > > do you have the metadata-updater consumer enabled? What > version of Archiva are you using? > > It certainly is implemented - it would be good to find out if > it has issues, though. > > - Brett > > On 02/04/2008, Brown, Carlton <[EMAIL PROTECTED]> wrote: > > In Maven 2 central repository, I notice some > maven-metadata.xml files > > that list all the available revisions of a module (stored at the > > module level of the directory hierarchy). Archiva doesn't > generate > > this metadata, although it does generate metadata in the > revision folder. > > Is Archiva supposed to generate the revision listing > metadata, or is > > this feature not implemented? If it is implemented, what > would cause > > it not to work for me? Do I need to enable it somehow? > > > > Thanks, > > Carlton > > > > > > > > ----------------------------------------- > > ==================================================== > > This message contains PRIVILEGED and CONFIDENTIAL > information that > > is intended only for use by the named recipient. If you > are not the > > named recipient, any disclosure, dissemination, or action > based on > > the contents of this message is prohibited. In such case please > > notify us and destroy and delete all copies of this transmission. > > Thank you. > > ==================================================== > > > -- > Brett Porter > Blog: http://blogs.exist.com/bporter/ >
