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 repository has a repository and a server
part for the same repository. In this case use different id's (ie.
<repositoryId>.server for the server).
Hth,
Nick S.
david delbecq wrote:
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 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.7/maven-settings/settings.html#class_server
delbd wrote:
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 PROTECTED] a écrit :
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 script to do it.
Hth,
Nick S.
-----Original Message-----
From: David Delbecq [mailto:[EMAIL PROTECTED]
Sent: Wed 3/5/2008 16:27
To: Maven Users List
Subject: converting from maven1 to maven2, pom for third party jars?
Hello,
in the process of converting our app from maven1 to maven2, we
changed our repository to have maven2 structure. For most library
we use public repositories (maven, jboss, apache) to fetch files.
But from some libraries we had to make them available to our local
repository, moving the jar from his group/jars/artefact-version.jar
to group/artifact/version/artifact-version.jar.
However, for the jar there is no "pom" files coming along, just a
jar. maven2 has no special trouble handling them, except it keeps
trying to go to all our configured repositories and try to download
those inexistant pom:
Downloading:
http://xxxxxxx/repository/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading:
http://download.java.net/maven/2//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading:
http://archiva.openqa.org/repository/releases//enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading:
http://repository.jboss.com/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading:
http://repo1.maven.org/maven2/enhydra/dods/dbmanager-api/6.4-1/dbmanager-api-6.4-1.pom
Downloading:
http://xxxxxxx/repository/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading:
http://download.java.net/maven/2//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading:
http://archiva.openqa.org/repository/releases//enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading:
http://repository.jboss.com/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading:
http://repo1.maven.org/maven2/enhydra/dods/stdconnection/6.4-1/stdconnection-6.4-1.pom
Downloading:
http://xxxxxxx/repository/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading:
http://download.java.net/maven/2//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading:
http://archiva.openqa.org/repository/releases//enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading:
http://repository.jboss.com/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
Downloading:
http://repo1.maven.org/maven2/enhydra/dods/ejen/6.4-1/ejen-6.4-1.pom
As you see, it tries to go to 5 different repositories, everytime
to get a 404. Is there a recommended way to either
a) tell maven that there is definitely no pom to download
b) create the pom and metadata file from a .jar file (generic pom
with correct names, but no dependencies)?
I tried for some jar to manually create pom, i received complains
about checksums ? and maven ignored the file!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
