History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: NEXUS-29
Type: User Story User Story
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Tamás Cservenák
Reporter: Kamen Petroff
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Nexus

Proxying Maven 1 legacy Repositories as a Maven 2 Repo

Created: 04/22/08 07:38 AM   Updated: 06/20/08 04:04 PM
Component/s: None
Affects Version/s: 1.0.0-beta-1, 1.0.0-beta-2, 1.0.0-beta-3
Fix Version/s: 1.0.0-beta-3

Time Tracking:
Not Specified

Environment: Any

Rank:
Issue is not rankable.     


 Description  « Hide
One thing I miss from archiva is the ability to access a maven 1 legacy repository through nexus, as if it has maven 2 layout.
For example if you use JAXB, you need the Java Net repository http://download.java.net/maven/1
If you define it in your pom as having legacy layout, then everything is fine. However in enterprise environment, you might want to mange the repositories centraly, e.g. having <mirrorOf>*</mirrorOf> pointing to nexus, and define a single inhouse repository.
This works with archiva, but not in nexus!

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Brian Fox - 05/13/08 03:44 PM
This works in beta-3. You need to add an M1 proxy repo, then add an M2 virtual repo and add this to your group (you can't directly mix m1/m2 in the same group)