Yes, the URL is the same - the path will just be in the for groupId/jars/artifactId-version.jar instead.
Regards, Brett 2008/8/13 Baeriswyl Kuno - Extern (IT-BA-MV) <[EMAIL PROTECTED]>: > Hi Brett, > > > Thanks for your fast answer. What would be the URL? The same for the Maven2 > Repository? I guess I can see like it a virtual repository? > > Thanks a lot > > Kuno > > > > -----Ursprüngliche Nachricht----- > Von: Brett Porter [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 13. August 2008 14:04 > An: [email protected] > Betreff: Re: Accessing Maven2 Repository with Maven1 Client > > > Yes, it supports both clients. It will translate the paths behind the scenes. > We recommend storing your repository in Maven 2.x format inside Archiva. > > Cheers, > Brett > > 2008/8/13 Baeriswyl Kuno - Extern (IT-BA-MV) <[EMAIL PROTECTED]>: >> Hello, >> >> >> we plan to replace our maven1 repository with Archiva. We also upgrade >> the build environement to maven2. Though, we still have some legacy >> maven1 clients, those need to access our central repository. >> >> Unfortunarely, I'm confused about the Archiva documentation. It says >> it supports the mapping between Maven1 legacy format and Maven2 >> format. However, it seems it doens't support accessing a repository by >> a Maven1 and Maven2 clients. >> >> Thanks for your clarifications. >> >> Kuno >> >> >> > > > > -- > Brett Porter > Blog: http://blogs.exist.com/bporter/ > -- Brett Porter Blog: http://blogs.exist.com/bporter/
