Then you can't make any reasonable use of Maven unless you want to build your own repository manager that maps that structure to what Maven is expecting. Which would be a Big Job. Better stick with whatever you are using.
On Sat, Jul 23, 2011 at 7:34 PM, Daivish Shah <[email protected]> wrote: > Hi Ron, > > I am looking for something which can provide me to follow my existing JAR > Location which is as followed. > > * Existing network Path :* > > * C:\networkfolder\ErrorLogging\1.0\Java\ErrorLogClient.jar* > > > And i don't want to change this network location of JAR file and > without changing the location of JAR Files, I want to use them in my > POM.xml as a Maven Repository. which follows the URL something like as > below from WEB. > > http://localhost:8080/samplepath/networkrepository/ErrorLogClient/ErrorLogClient/1.0/ErrorClient-1.0.jar > > > > And if i use ARCHIVA or NEXUS which actually doesn't support my existing > NETWORK location of JAR files. I need to move those Network location JAR > files to different location. Which is something like this. new<goog_7024208> > networkrepository/ErrorLogClient/ErrorLogClient/1.0/ErrorClient-1.0.jar<http://localhost:8080/samplepath/networkrepository/ErrorLogClient/ErrorLogClient/1.0/ErrorClient-1.0.jar> > > So here i can't use NEXUS or ARCHIVA. > > Let me know if you are still not clear. > > > Thanks, > Daivish. > > On Sat, Jul 23, 2011 at 12:18 PM, Ron Wheeler < > [email protected]> wrote: > >> On 22/07/2011 6:56 PM, Daivish Shah wrote: >> >>> Hi, >>> >>> I have one quick Question for you guys. >>> >>> I am having one issue to adopt Maven. My company needs following features >>> available with Maven. I am trying to force my company to choose Maven as >>> build TOOL. but they have one critical question for you guys. >>> >>> >>> My company is looking to write something like this or something which is >>> available in the market which supports this feature, 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/**samplepath/networkrepository/** >>> ErrorLogClient/ErrorLogClient/**1.0/ErrorClient-1.0.jar<http://localhost:8080/samplepath/networkrepository/ErrorLogClient/ErrorLogClient/1.0/ErrorClient-1.0.jar> >>> <http:/**/localhost:8080/archiva/**browse/ErrorLogClient/** >>> ErrorLogClient/1.0/**ErrorClient-1.0.jar<http://localhost:8080/archiva/browse/ErrorLogClient/ErrorLogClient/1.0/ErrorClient-1.0.jar> >>> > >>> >>> >>> Is there any work around for this, That 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 MAVEN is following at this moment. >>> >>> Can you please reply me as soon as possible. AS i need to figure it out >>> can >>> i choose MAVEN for this or not ? >>> >>> Let me know if you are confused or not clear with my requirement. >>> >> Not sure what you are trying to accomplish with this. >> You should look at installing Nexus or some other Maven Repo if you are >> serious about Maven for a large set of products. >> This will give you a proper repo. >> A Maven Repo is not just a collection of jars. >> >> Ron >> >>> Thanks, >>> Daivish. >>> >>> >> >> ------------------------------**------------------------------**--------- >> To unsubscribe, e-mail: >> users-unsubscribe@maven.**apache.org<[email protected]> >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
