MRM-872 created for this, with the concrete case I fall into. If confirmed, this is a blocker for repository group use
2008/7/10 Dan Tran <[EMAIL PROTECTED]>: > sounds like a blocking bug? would love to see this fixed in 1.1 :-) > > On Wed, Jul 9, 2008 at 7:11 PM, Maria Odea Ching <[EMAIL PROTECTED]> > wrote: > > Hi Nico, > > > > That looks like a new bug :( The metadata should be just the same as the > > regular metadata of a managed repo (not belonging to a group) as it uses > the > > same code for webdav & proxying. Could you file a jira for this? > > > > Thanks, > > Deng > > > > On Wed, Jul 9, 2008 at 8:45 PM, nicolas de loof <[EMAIL PROTECTED]> > wrote: > > > >> Hy, > >> > >> I get strange behaviour wen using repository group : > >> > >> From a fresh maven installation (empty local repo), with settings set to > >> mirror central to my archiva repository group URL, the eclipse 2.5 > plugin > >> can't find the required org.eclipse.core:resources:[3.1.0,4.0.0) > >> > >> The maven-metadata.xml returned by the group URL is emty. requesting > >> metadatas from individual managed repos in the group are fine. Is this a > >> known limitation ? > >> > >> Nico. > >> > > >
