Hi Wayne, You understood me correctly. And our company is looking to use MAVEN standards in future so i think the idea to create custom repository structure will not be good for us.
We have to prove some projects with MAVEN first and make them easy going with MAVEN. Then all projects will move with MAVEN standards. So to start with we have to create HTTP URL which follows existing standard of MAVEN. And no change in Network location of all Artifacts here. So based on your explanation, I have only one option to write a small project which brings up this Maven Standard URL format and use that as maven repository for now. Thanks for all your explanation and sorry for all confusion that you had to understand my requirement. Correct me if still any other work around. Thanks, Daivish. On Mon, Jul 25, 2011 at 8:26 AM, Wayne Fay <wayne...@gmail.com> wrote: > > So i wanted to confirm that i only have ONE WAY TO write ONE WEB Project > > which can bring up like this URL so in background my Project should use > old > > network location but HTTP location should follow the MAVEN standard. > > > > that's the only way for me ?? > > Clearly we are all having trouble understanding what you are asking, > even though we are all speaking English. > > Let me tell you what I believe you are asking and then you confirm or deny: > 1. I have an existing repo with a different structure to what Maven > expects, and I want to use it to fulfill dependency requests while > building artifacts with Maven. We cannot adjust the layout/structure > of the old repo at this time. > > 2. I am planning to write some webapp that will work like mod_rewrite > and turn requests from Maven that look like > http://repo/m2/ErrorLogClient/ErrorLogClient/1.0/ErrorClient-1.0.jar > into requests that my existing repo will understand under a path like > http://repo2/networkfolder/ErrorLogging/1.0/Java/ErrorLogClient.jar > > 3. I would like to be told the algorithm that Maven uses when looking > for artifacts in my repo so that I can code up the rewrite webapp > properly. > > If this is what you are asking then yes this would seem to be possible > if you are unwilling or unable to change your existing repo structure > to match what Maven is looking for. The path Maven uses to find its > artifacts is simply: > http://repo/groupId/artifactId/version/artifactId-version.packaging > > This corresponds to: > <project> > <modelVersion>4.0.0</modelVersion> > <groupId>groupId</groupId> > <artifactId>artifactId</artifactId> > <version>version</version> > <packaging>packaging</packaging> > </project> > > Arguably, you may find it worth some investment in time/dollars to > look into modifying Maven itself to support your repo structure with a > custom repo layout handler. Here's a blog post with details but do > read the comments about how this will only work with Maven2 at this > point: > > http://kthoms.wordpress.com/2009/10/13/how-to-register-a-custom-maven-repository-layout/ > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
