[
https://jira.codehaus.org/browse/MRM-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274315#comment-274315
]
Brett Porter commented on MRM-1482:
-----------------------------------
Here are the steps to just support a custom managed repository type, building
on Archiva 1.3.x. If you wanted to make the modification to trunk (which has
changed but is not released yet) or make it flexible, please discuss it with us
on [email protected] and we'd be happy to help incorporate your patch.
The first step is to make sure you can checkout and build Archiva:
http://archiva.apache.org/developers/building.html
Instead of the location there, you will want to check out the branch for your
purposes:
http://svn.apache.org/repos/asf/archiva/branches/archiva-1.3.x
Once you can build and run it, try copying the class above to a new one in the
same directory and change the "legacy" references to, say, "custom". As part of
changing this, you'll also need alternatives for these:
- AbstractLegacyRepositoryContent
- LegacyPathParser
You'll also need to add "custom" as valid values in these:
-
archiva-webapp/src/main/resources/org/apache/maven/archiva/web/action/admin/ConfigureRepositoryAction-validation.xml
- archiva-webapp/src/main/webapp/WEB-INF/jsp/admin/include/repositoryForm.jspf
If you can then build and run archiva and create a managed repository of type
"custom", you are ready to edit the code you copied to read files in the format
you expect. Hopefully, how to do that is obvious from the code there.
If you have any questions, feel free to ping us on [email protected].
> 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
