Exsiting Network Location Access for JAR files

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.

I think from your answer it looks like i have to write a custom code which brings me URL something like this...

http://localhost:8080/samplepath/networkrepository/ErrorLogClient/ErrorLogClient/1.0/ErrorClient-1.0.jar

And i have to USE this URL as my network-repository only, And then no point of Using Archiva at this moment unless i upload all artifacts into Archiva repository.

I was trying to avoid writing new custom code. As archiva is nice tool and very good features available itself. But my company is not looking to change existing network location or structure for all JARs at this moment. So i have only one option left to write custom code to create HTTP URL.

Thanks for your help.

-Daivish.

Actually, what I meant was to write custom code within Archiva, so that Maven would request:

http://localhost:8080/archiva/repository/someid/ErrorLogClient/ErrorLogClient/1.0/ErrorLogClient-1.0.jar

and on the storage end you would look that up as a path C:\networkfolder\ErrorLogging\1.0\Java\ErrorLogClient.jar

It is a copy of this class: http://svn.apache.org/viewvc/archiva/branches/archiva-1.3.x/archiva-modules/archiva-base/archiva-repository-layer/src/main/java/org/apache/maven/archiva/repository/content/ManagedLegacyRepositoryContent.java?revision=900340&view=markup

I think you are right.

Can you explain me, What exactly all things i need to do with this file and What all steps that i need to follow to complete this ?

This is really good idea if i can do with Archiva only, I am very happy to hear this... Please explain me more in detail.

Thanks Brett !!! Looking forward to hear more from you.

Hi Brett,

Can you explain me little bit on this ?

Thanks,
daivish.

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 dev@archiva.apache.org 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 dev@archiva.apache.org.

Thanks Brett for your help. I sent email to dev@archiva.apache.org group waiting for reply from them now.

I hope it should not take much effort to do this. What do you think is it require lot of work around ?

how are you going with this?

Hi Brett,

I didn't get any reply from (dev@archiva.apache.org) So i developed my own Archiva which doesn't have same kind of functionality But atleast i can download JAR files with POM XML from my own project URL.

something like this So you hit the URL and it gives me POM and JAR file which MAVEN is looking for.

http://localhost:8080/myproject/repository/ErrorLogClient/ErrorLogClient/1.0/ErrorLogClient-1.0.jar

So currently i am using my own project which i developed and which is using Archiva concepts.

Thanks for asking Brett, I can't wait such a long so i thought let me develop myself only.

No problem. You may want to check your email settings though, as you did get responses:
http://mail-archives.apache.org/mod_mbox/archiva-dev/201107.mbox/%3C202ACA4A-6B53-4701-8C48-D267DBA9E927@apache.org%3E
http://mail-archives.apache.org/mod_mbox/archiva-dev/201107.mbox/%3CCAPCVKoLxj_vQNBMuNoVg3Os4Ce7xa0OirJZBE6Y-_U=hGzsVMw@mail.gmail.com%3E