You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Daivish Shah <da...@gmail.com> on 2011/07/23 00:56:51 UTC
Existing Network Location Access for JAR files
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/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.
Thanks,
Daivish.
Re: Existing Network Location Access for JAR files
Posted by Daivish Shah <da...@gmail.com>.
Yes you are absolutely right. Yes currently it's hard for debugging as we
don't know which version of JAR is breaking the Environment.
that's the reason we want to move with Maven we can know our artifact build
version and believe me it's very hard to change these things when you have
more then 100 products live :-)
That's why we come up with a solution at this moment to create some mock-up
URL, Which Maven is looking for and once things are good and everybody is
happy :-) i mean each team :-) then we can get approval to move with MAVEN.
Thanks a lot for all your help again.
-daivish.
On Mon, Jul 25, 2011 at 1:01 PM, Ron Wheeler <rwheeler@artifact-software.com
> wrote:
>
> On 25/07/2011 3:47 PM, Wayne Fay wrote:
>
>> Yes I agree with Nexus, But the only concern in choosing Nexus is we have
>>> to
>>> daily copy our latest JAR files from Existing location to New location
>>> for
>>> Even 1 Project. As so many dependency on those Jar files and which are
>>> daily
>>> updating. So we have to daily Update the new Nexus location too.
>>>
>> Arguably, this can be easily handled with a simply cron job which
>> calls mvn deploy:deploy-file across files in various directories where
>> your artifacts currently live.
>>
>> Wayne
>>
> Good solution.
> You also should only be copying the released versions of libraries rather
> that the daily snapshots.
> You need some stability in the dependencies of your projects otherwise you
> have a heck of a time debugging the project.
>
> It sounds like your current system makes it very hard to know the pedigree
> of any artifact that you build.
> Maven and Nexus should move you towards a way of life that is more aware of
> releases, SNAPSHOTS and stuff that somebody is working on. (I don't want to
> use any of the last type and usually prefer an older version of the first
> type to a current SNAPSHOT unless I absolutely need the latest thing that
> only the SNAPSHOT includes.)
>
> Ron
>
>
> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<us...@maven.apache.org>
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<us...@maven.apache.org>
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Existing Network Location Access for JAR files
Posted by Ron Wheeler <rw...@artifact-software.com>.
On 25/07/2011 3:47 PM, Wayne Fay wrote:
>> Yes I agree with Nexus, But the only concern in choosing Nexus is we have to
>> daily copy our latest JAR files from Existing location to New location for
>> Even 1 Project. As so many dependency on those Jar files and which are daily
>> updating. So we have to daily Update the new Nexus location too.
> Arguably, this can be easily handled with a simply cron job which
> calls mvn deploy:deploy-file across files in various directories where
> your artifacts currently live.
>
> Wayne
Good solution.
You also should only be copying the released versions of libraries
rather that the daily snapshots.
You need some stability in the dependencies of your projects otherwise
you have a heck of a time debugging the project.
It sounds like your current system makes it very hard to know the
pedigree of any artifact that you build.
Maven and Nexus should move you towards a way of life that is more aware
of releases, SNAPSHOTS and stuff that somebody is working on. (I don't
want to use any of the last type and usually prefer an older version of
the first type to a current SNAPSHOT unless I absolutely need the latest
thing that only the SNAPSHOT includes.)
Ron
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Existing Network Location Access for JAR files
Posted by Wayne Fay <wa...@gmail.com>.
> Yes I agree with Nexus, But the only concern in choosing Nexus is we have to
> daily copy our latest JAR files from Existing location to New location for
> Even 1 Project. As so many dependency on those Jar files and which are daily
> updating. So we have to daily Update the new Nexus location too.
Arguably, this can be easily handled with a simply cron job which
calls mvn deploy:deploy-file across files in various directories where
your artifacts currently live.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Existing Network Location Access for JAR files
Posted by Daivish Shah <da...@gmail.com>.
Hi Ron,
Yes I agree with Nexus, But the only concern in choosing Nexus is we have to
daily copy our latest JAR files from Existing location to New location for
Even 1 Project. As so many dependency on those Jar files and which are daily
updating. So we have to daily Update the new Nexus location too.
That is why we have to write some work around which can use existing network
location.
Thanks for your all explanation.
-Daivish.
On Mon, Jul 25, 2011 at 10:49 AM, Ron Wheeler <
rwheeler@artifact-software.com> wrote:
> I still think that installing Nexus and using Maven and Nexus out of the
> box for 1 project is the best way to start.
> That will handle all of your needs for third party libraries and it will
> only take a few minutes to upload the internal libraries that you require to
> build the one project that you want to start with.
> It will take 1/2 a day to set up Nexus and get your Maven set up to use it.
>
> This will give you a standard platform to use Maven which will make it
> possible for you to get support.
>
> Once you get your first project working well, you will be in a better
> situation where you have the knowledge to plan a migration to Maven for the
> rest of the projects.
> You will understand how repositories are used by Maven and understand how
> Maven deals with dependencies and library searches.
> You will also understand what it means to have artifacts in your library
> that do not have POM files.
>
> If you still want to customize Maven, you can go ahead at that point with a
> lot better understanding of the need and will be able to explain the
> advantages, disadvantages, life-cycle costs and risks that this entails.
>
> Wayne is one of the smartest and most knowledgeable people in this forum
> and if you do decide to go ahead with a custom approach, you should read
> very carefully what he suggests and be sure to follow it.
>
>
> Ron
>
>
> On 25/07/2011 1:17 PM, Daivish Shah wrote:
>
>> 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<wa...@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<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<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<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/<http://kthoms.wordpress.com/2009/10/13/how-to-register-a-custom-maven-repository-layout/>
>>>
>>> Wayne
>>>
>>> ------------------------------**------------------------------**
>>> ---------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<us...@maven.apache.org>
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<us...@maven.apache.org>
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Existing Network Location Access for JAR files
Posted by Ron Wheeler <rw...@artifact-software.com>.
I still think that installing Nexus and using Maven and Nexus out of the
box for 1 project is the best way to start.
That will handle all of your needs for third party libraries and it will
only take a few minutes to upload the internal libraries that you
require to build the one project that you want to start with.
It will take 1/2 a day to set up Nexus and get your Maven set up to use it.
This will give you a standard platform to use Maven which will make it
possible for you to get support.
Once you get your first project working well, you will be in a better
situation where you have the knowledge to plan a migration to Maven for
the rest of the projects.
You will understand how repositories are used by Maven and understand
how Maven deals with dependencies and library searches.
You will also understand what it means to have artifacts in your library
that do not have POM files.
If you still want to customize Maven, you can go ahead at that point
with a lot better understanding of the need and will be able to explain
the advantages, disadvantages, life-cycle costs and risks that this entails.
Wayne is one of the smartest and most knowledgeable people in this forum
and if you do decide to go ahead with a custom approach, you should read
very carefully what he suggests and be sure to follow it.
Ron
On 25/07/2011 1:17 PM, Daivish Shah wrote:
> 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<wa...@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-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Existing Network Location Access for JAR files
Posted by Daivish Shah <da...@gmail.com>.
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 <wa...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Existing Network Location Access for JAR files
Posted by Wayne Fay <wa...@gmail.com>.
> 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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Existing Network Location Access for JAR files
Posted by Daivish Shah <da...@gmail.com>.
Yes but what we are thinking is We can make HTTP URL something like this
http://localhost:8080/samplepath/networkrepository/ErrorLogClient/ErrorLogClient/<http://localhost:8080/samplepath/networkrepository/ErrorLogClient/ErrorLogClient/1.0/ErrorClient-1.0.jar>
1.0/ErrorClient-1.0.jar<http://localhost:8080/samplepath/networkrepository/ErrorLogClient/ErrorLogClient/1.0/ErrorClient-1.0.jar>
For that may be we have to write small WAR project and which can come up as
this URL and step by step we move our projects to MAVEN and till that time
we use this HTTP url as our Network Repository.
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 ??
Thanks,
daivish.
On Sat, Jul 23, 2011 at 4:38 PM, Benson Margulies <bi...@gmail.com>wrote:
> 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 <da...@gmail.com>
> 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 <
> > rwheeler@artifact-software.com> 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<
> users-unsubscribe@maven.apache.org>
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Existing Network Location Access for JAR files
Posted by Benson Margulies <bi...@gmail.com>.
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 <da...@gmail.com> 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 <
> rwheeler@artifact-software.com> 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<us...@maven.apache.org>
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Existing Network Location Access for JAR files
Posted by Daivish Shah <da...@gmail.com>.
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 <
rwheeler@artifact-software.com> 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<us...@maven.apache.org>
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Existing Network Location Access for JAR files
Posted by Ron Wheeler <rw...@artifact-software.com>.
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/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
For additional commands, e-mail: users-help@maven.apache.org