Hi Sonia, The current implementation of the repository scanning is that it only processes files/artifacts whose last modification date is newer than the last scan. So if you're artifacts are older than the last scan, you might need to update their last modification date then execute the repo scan again in order for it to pop up in the Browse. Please see [1] which is more or less a related issue..
The "indexable-content" in the file types defines the file types that would be processed by the index-content consumer, which performs the indexing of the repository during the repo scan :) HTH, Deng [1] http://jira.codehaus.org/browse/MRM-841 On Thu, Jan 29, 2009 at 1:14 AM, solo1970 <[email protected]>wrote: > > Hello, > > I want 2 new file extensions to come up with the artifact. a .xsd and .onf > extension. > > I put them under "artifacts" in the "Repository Scanning - File Types" > section, but they still won't come up... > > Also, can anyone explain the "indexable-content" section? > > THANKS! > > Sonia > -- > View this message in context: > http://www.nabble.com/Repository-scanning-tp21710206p21710206.html > Sent from the archiva-users mailing list archive at Nabble.com. > > -- Maria Odea Ching Software Engineer | Exist Global | 687-4091 | Skype: maria.odea.ching | www.exist.com | Innovation Delivered
