Ralph Goers escribió:
You should also consider building your own "local mirror". i.e., a
maven repository in your own local network. (This is not the same as
the local repository - it contains the stuff from your local builds).
However, I don't think Maven has an automated way to do this other
than to manually copy stuff from the local repository to the mirror.
Here is another way, when you can place the jars into your own repo.
It's manually too, but somehow I found it easier:
Syntax:
mvn deploy:deploy-file -DgroupId=<group-id> \
-DartifactId=<artifact-id> \
-Dversion=<version> \
-Dpackaging=<type-of-packaging> \
-Dfile=<path-to-file> \
-DrepositoryId=<id-to-map-on-server-section-of-settings.xml> \
-Durl=<url-of-the-repositor-to-deploy>
Sample uploading postgresql-8.1-405.jdbc3.jar:
mvn deploy:deploy-file -DgroupId=postgresql \
-DartifactId=postgresql \
-Dversion=8.1-405.jdbc3
-Dpackaging=jar \
-Dfile="/home/agallardo/dev/lib/postgresql-8.1-405.jdbc3.jar" \
-DrepositoryId="my-own-repo" \
-Durl=scp://my.server.name/home/www/*maven*
Best Regards,
Antonio Gallardo.
Reinhard Poetz wrote:
Bertrand Delacretaz wrote:
On 5/18/06, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
...I had similar problems with m2 and now I'm always doing a "clean
install" and most times remove my local repo as well...
Just curious, how much time do you need for a clean build of the
trunk, starting with an empty m2 repository?
I've had several occurences where the whole thing was not finished
after more than an hour, using an usually fast DSL or similar
connection. For some reason, the repository downloads seem to be very
slow here.
Not only for you. I also encounter problems with artifact downloads
and I saw many comments by frustrated users on other ASF mailing
lists. Maybe we should revive the idea setting up our own mirror with
all dependencies that trunk needs. Andrew, is your offer still valid?
