[jira] Commented: (MRM-1482) Exsiting Network Location Access for JAR files

["Brett Porter (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MRM-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274089#comment-274089 ] 

Brett Porter commented on MRM-1482:
-----------------------------------

You would have to write a small amount of custom code into Archiva, but it isn't exposed as a user level feature. Essentially this is the same abstraction that is used to support Maven 1.x and Maven 2.x format repositories simultaneously. Is that something you are prepared to do? 

Alternatively, you could quite easily script something to upload that directory into Archiva with default POMs, but then you have two copies and you probably only want to maintain one going forward. 

There is a catch to keep in mind here though - default POMs will not have any dependency information, so the amount of dependency management you can do with these JARs will be limited. You may want to invest the right amount effort to get this populated as well to improve your use of Maven.

> Exsiting Network Location Access for JAR files
> ----------------------------------------------
>
>                 Key: MRM-1482
>                 URL: https://jira.codehaus.org/browse/MRM-1482
>             Project: Archiva
>          Issue Type: New Feature
>          Components: repository scanning
>    Affects Versions: 1.3.5
>         Environment: Windows 
>            Reporter: daivish shah
>            Priority: Critical
>
> 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. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira