You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "daivish shah (JIRA)" <ji...@codehaus.org> on 2011/07/22 23:36:43 UTC
[jira] Created: (MRM-1482) Exsiting Network Location Access for JAR
files
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
[jira] Commented: (MRM-1482) Exsiting Network Location Access for
JAR files
Posted by "daivish shah (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276696#comment-276696 ]
daivish shah commented on MRM-1482:
-----------------------------------
Hi Brett,
Yes i didn't get this email in my inbox sorry about that.
i think i am fine at this moment as i already made my own repository code, If i will find any issue in future i will contact you again.
Thanks for all your help.
> 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
> Fix For: Backlog
>
>
> 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
[jira] Commented: (MRM-1482) Exsiting Network Location Access for
JAR files
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274196#comment-274196 ]
Brett Porter commented on MRM-1482:
-----------------------------------
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
> 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
[jira] Commented: (MRM-1482) Exsiting Network Location Access for
JAR files
Posted by "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
[jira] Commented: (MRM-1482) Exsiting Network Location Access for
JAR files
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276547#comment-276547 ]
Brett Porter commented on MRM-1482:
-----------------------------------
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
> 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
> Fix For: Backlog
>
>
> 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
[jira] Commented: (MRM-1482) Exsiting Network Location Access for
JAR files
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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 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.
> 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
[jira] Updated: (MRM-1482) Exsiting Network Location Access for JAR
files
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-1482:
------------------------------
Fix Version/s: Backlog
how are you going with this?
> 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
> Fix For: Backlog
>
>
> 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
[jira] Commented: (MRM-1482) Exsiting Network Location Access for
JAR files
Posted by "daivish shah (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274198#comment-274198 ]
daivish shah commented on MRM-1482:
-----------------------------------
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.
> 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
[jira] Commented: (MRM-1482) Exsiting Network Location Access for
JAR files
Posted by "daivish shah (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274148#comment-274148 ]
daivish shah commented on MRM-1482:
-----------------------------------
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.
> 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
[jira] Commented: (MRM-1482) Exsiting Network Location Access for
JAR files
Posted by "daivish shah (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276482#comment-276482 ]
daivish shah commented on MRM-1482:
-----------------------------------
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.
> 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
> Fix For: Backlog
>
>
> 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
[jira] Commented: (MRM-1482) Exsiting Network Location Access for
JAR files
Posted by "daivish shah (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274396#comment-274396 ]
daivish shah commented on MRM-1482:
-----------------------------------
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 ?
> 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
[jira] Commented: (MRM-1482) Exsiting Network Location Access for
JAR files
Posted by "daivish shah (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRM-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274301#comment-274301 ]
daivish shah commented on MRM-1482:
-----------------------------------
Hi Brett,
Can you explain me little bit on this ?
Thanks,
daivish.
> 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