> The way local and remote repositories are different, for example:
>
> - Local snapshots are not saved with timestamp, remote snapshots are saved
> with timestamps. If you use a local repository as remote repository, maven
> can't tell if a SNAPSHOT has changed and won't download newer SNAPSHOTS
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thu 3/6/2008 09:34
To: Maven Users List
Subject: Re: RE: converting from maven1 to maven2, pom for third party jars?
So what else do you recommend me to easily get all required dependencies on the
remote server - at once if possible?
008 09:10:48 +0100
> Von: [EMAIL PROTECTED]
> An: "Maven Users List"
> Betreff: RE: converting from maven1 to maven2, pom for third party jars?
> I can't repeat it often enough: do not copy a local repository to be used
> as a remote repository. There is not t
ick S.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thu 3/6/2008 07:04
To: Maven Users List
Subject: Re: converting from maven1 to maven2, pom for third party jars?
To be able to deploy something on your company's remote server,
have a look at &qu
thing" to your repository...
Hope that helps,
Christine
Original-Nachricht
> Datum: Wed, 05 Mar 2008 23:29:53 +0100
> Von: david delbecq <[EMAIL PROTECTED]>
> An: Maven Users List
> Betreff: Re: converting from maven1 to maven2, pom for third party jars?
There are many problems with installing files into your remote
repository, especially with the metadata and snapshots.
What I noticed with settings.xml. If you have a repository and a server
with the same id, it will not pickup the credentials from the server.
Most of the users with an own rep
Did :) does not work, will investigate further. For now am doing
scripted convertion server side, attackign directly the server
direcgtory structure using install-file, works like a charm :D
Nick Stolwijk a écrit :
Take a look at the repositoryId [1] option of deploy-file and the
server sectio
Take a look at the repositoryId [1] option of deploy-file and the server
section in settings.xml [2]. They should take care of your authorisation.
Hth,
Nick Stolwijk
[1]
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#repositoryId
[2]
http://maven.apache.org/ref/2.0
the deploy target doesnt seem to accept the fact our local repository
requires password authentification. it just fails. Our server ask client
for credential for write operation (apache DAV mod) but maven doesn't
try with password. i'll give a try using install:install-file thanks
[EMAIL PRO
There is a solution for this problem. The deploy:deploy-file will automatically
generate a pom file.
So, remove the jars from your remote repository and deploy them again with mvn
deploy:deploy-file .
Perhaps if you make a list with the directories it should be possible to create
a little scri
10 matches
Mail list logo
