You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Simon McClenahan <sm...@healthcompartners.com> on 2005/06/17 16:19:40 UTC
Remote repository version control
I am specifying a remote repository because the jar files I need are
stored in my version control system, where I have checked them out into
my local filesystem. I would have like to specify a relative path to the
remote repository, but I don't think that's possible with a URL scheme.
I have not attempted to setup a multiproject configuration in Maven yet,
but what would be the best practice for version control of artifacts in
a remote repository that is referenced locally? Maybe this is the
complicated way of doing it. Should I be creating a remote repository to
upload to on a shared resource (e.g. network drive) instead and not be
concerned about version control?
- Simon
-----Original Message-----
From: Henry Isidro [mailto:hisidro@exist.com]
Sent: Thursday, June 16, 2005 7:06 PM
To: Maven Users List
Subject: Re: Component Descriptor Error Message
Simon McClenahan wrote:
>I'm running Maven under Windows, and I was unable to specify the drive
>letter. Conveniently I do everything on my C: drive, and I have ended
up
>using the following:
>
>maven.repo.remote=file:///localhost/projects/online/trunk/,http://www.i
b
>iblio.org/maven/
>
>I know it doesn't seem right, but I figured this out by trial and
error.
>I'm using Maven 1.0.2.
>
>- Simon
>
>
>
If you're using Maven 1.0.2, you could just place the jars in your local
repository and not go through the trouble of mirroring a remote
repository on your machine. Maven checks the local repository first for
dependencies before attempting to download from the remote repository.
Usually, the local repository is found in ${maven.home.local}/repository
where maven.home.local is ${user.home}/.maven. So if you're using
Windows, and your user name is for example, User1, your local repository
would be found in "C:\Documents and Settings\User1\.maven".
Hope this clears up a few things. Regards,
Henry
||||
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
--------------------------
NOTE: This message and any included attachments are from HealthCom Partners, LLC and are intended only for the addressee(s). The information contained herein may include trade secrets or privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you received this message in error, or have reason to believe you are not authorized to receive it, please promptly delete this message and notify the sender by e-mail.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Remote repository version control
Posted by Brett Porter <br...@gmail.com>.
There is nothing saying you can't store the repository in VCS either,
by the way - it just needs to be accessible over HTTP in Maven 1, and
in the desired format.
Maven's objection lies more with storing binary dependencies in your
project's VCS as it results in duplicates and bigger checkout/updates.
- Brett
On 6/18/05, dan tran <da...@gmail.com> wrote:
> Hi Simon, maven encourges not to store binary artifact to version
> control system,
> but to be placed in your remote repository (make sure to back it up regularly).
>
> Let's maven manages the artifacts for you.
>
> If you insist on using artifacts in your VCS, look up
> maven.jar.override settings.
> So that you can ask maven to skip the remote lookup but only at your
> local propriety place.
>
> -D
>
>
> On 6/17/05, Guillaume Lederrey <gu...@gmail.com> wrote:
> > On 6/17/05, Simon McClenahan <sm...@healthcompartners.com> wrote:
> > > I am specifying a remote repository because the jar files I need are
> > > stored in my version control system, where I have checked them out into
> > > my local filesystem. I would have like to specify a relative path to the
> > > remote repository, but I don't think that's possible with a URL scheme.
> > > I have not attempted to setup a multiproject configuration in Maven yet,
> > > but what would be the best practice for version control of artifacts in
> > > a remote repository that is referenced locally? Maybe this is the
> > > complicated way of doing it. Should I be creating a remote repository to
> > > upload to on a shared resource (e.g. network drive) instead and not be
> > > concerned about version control?
> >
> > I would say that the cleanest way is to create a repository on a
> > shared resource. If you really want to include your dependencies in
> > your versionning tool, it probably makes sense only if they are
> > included with your project. So in this case, put them in your project
> > tree and copy them at the right place with a "maven.xml" goal.
> >
> > ---------------------------------------------------------------------
> > 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Remote repository version control
Posted by dan tran <da...@gmail.com>.
Hi Simon, maven encourges not to store binary artifact to version
control system,
but to be placed in your remote repository (make sure to back it up regularly).
Let's maven manages the artifacts for you.
If you insist on using artifacts in your VCS, look up
maven.jar.override settings.
So that you can ask maven to skip the remote lookup but only at your
local propriety place.
-D
On 6/17/05, Guillaume Lederrey <gu...@gmail.com> wrote:
> On 6/17/05, Simon McClenahan <sm...@healthcompartners.com> wrote:
> > I am specifying a remote repository because the jar files I need are
> > stored in my version control system, where I have checked them out into
> > my local filesystem. I would have like to specify a relative path to the
> > remote repository, but I don't think that's possible with a URL scheme.
> > I have not attempted to setup a multiproject configuration in Maven yet,
> > but what would be the best practice for version control of artifacts in
> > a remote repository that is referenced locally? Maybe this is the
> > complicated way of doing it. Should I be creating a remote repository to
> > upload to on a shared resource (e.g. network drive) instead and not be
> > concerned about version control?
>
> I would say that the cleanest way is to create a repository on a
> shared resource. If you really want to include your dependencies in
> your versionning tool, it probably makes sense only if they are
> included with your project. So in this case, put them in your project
> tree and copy them at the right place with a "maven.xml" goal.
>
> ---------------------------------------------------------------------
> 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: Remote repository version control
Posted by Guillaume Lederrey <gu...@gmail.com>.
On 6/17/05, Simon McClenahan <sm...@healthcompartners.com> wrote:
> I am specifying a remote repository because the jar files I need are
> stored in my version control system, where I have checked them out into
> my local filesystem. I would have like to specify a relative path to the
> remote repository, but I don't think that's possible with a URL scheme.
> I have not attempted to setup a multiproject configuration in Maven yet,
> but what would be the best practice for version control of artifacts in
> a remote repository that is referenced locally? Maybe this is the
> complicated way of doing it. Should I be creating a remote repository to
> upload to on a shared resource (e.g. network drive) instead and not be
> concerned about version control?
I would say that the cleanest way is to create a repository on a
shared resource. If you really want to include your dependencies in
your versionning tool, it probably makes sense only if they are
included with your project. So in this case, put them in your project
tree and copy them at the right place with a "maven.xml" goal.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org