Does it mean that maven2 can not retrieve artifacts (jars etc) from
remote repositories ? Or something else ?
Regards.
-Original Message-
From: Nick Stolwijk [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 30, 2006 4:07 PM
To: Maven Users List
Subject: Re: How to disable creation of
I tried to say, that the programs run by Maven2 needs the jar files
locally. i.e. when you use Maven to compile something it calls javac
with a classpath set to the jar files specified in your POM. Javac uses
the classpath to locate the jar files and as far as I know, Javac can't
work with
I created a network first to try it out instead of webserver, but
unfortunately it did not work :
What I did was :
- created a network share on server.
- assigned write permissions on that to me only,
everyone read.
- create a environment variable
I think what he meant is, he want the local files (i.e. local repository) to be
alive only during
the build period but not forever long.
Is it possible to modify the mvn.bat to make it remove the directory after it
did its work?
or have a schedule job to delete the local repository everyday
Thanks Nick, But don't you think that, placing tonns of dependencies /
plugins on every developer machine is not a sound idea ? Being the fact
that theses depedencies / plugins are alreay available on intranet
repository, why not a mechanism on demand.
Yes, If there is no way, and we want to
I don't think that is a problem. Hard disks don't cost that much anymore
(My local repository is now around 500 MB). The jars in the repository
are all versioned. (as in, Maven2 automagically takes the right one,
i.e. a specific version if you define that in your POM or a latest
version
Though it seems unusual to refer it as local, it did not
work. I am not sure If took right steps, may be someone else
give some pointers on this ?
Define 'did not work'. What seems to go wrong? I think Maven does not know
(or care) wether it's a local or mounted disk. So if it doesn't work
