[MRM-1482] Exsiting Network Location Access for JAR files

• Type: New Feature
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 1.3.5
• Fix Version/s: Backlog
• Component/s: repository scanning
• Environment: Windows
• Assignee: Unassigned
• Reporter: daivish shah
• Created: 22/Jul/11 16:36
• Updated: 22/Aug/11 11:30

Description

Hi,

I have one quick Question for you guys.

I am having one issue to adopt Archiva and Maven. My company needs following features available with Archiva. I am trying to force my company to choose Archiva but they have one critical question for you guys.

My company is looking for a tool, Which can provide existing network path location as Maven Local Repository. Example is as followed.

Existing network Path :

C:\networkfolder\ErrorLogging\1.0\Java\ErrorLogClient.jar

And my MAVEN repository should show-up path something like this.

http://localhost:8080/archiva/browse/ErrorLogClient/ErrorLogClient/1.0/ErrorClient-1.0.jar

Is there any work around for this, That Archiva can provide me ?

The company has more then 100 products which is using something like this so we have to start with only 1 project for now. And for that there are so many dependency with each projects so we can't create a new network location and where we point as a MAVEN repository so i am looking for something which can provide me to use existing network path which actually has different kind of directory structure which is archiva is expecting at this moment.

Can you please reply me as soon as possible. AS i need to figure it out can i choose Archiva for this or not ?

Let me know if you are confused or not clear with my requirement.

Thanks,
Daivish.