I would setup a maven repository, with mirrors for at least central and maybe some other repositories. Also create inhouse repositories for your own release, Snapshots and external dependencies. (3 different repositories)
Then set up your local maven to use the mirrors, and rebuild with an empty local repository. For every dependency that is not found, use the same tactics as you did, but then with deploy:deploy-file deploy them to the external dependency repository and add the remote repository to the repository section in the pom file. 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. Hth, Nick S. -----Original Message----- 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? What would / could happen if I simply copied the local repository to the remote one? Thanks in advance, Stefanie -------- Original-Nachricht -------- > Datum: Thu, 6 Mar 2008 09:10:48 +0100 > Von: [EMAIL PROTECTED] > An: "Maven Users List" <users@maven.apache.org> > 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 the same information in your local > repository as in your remote repository. > > Really, do use a Maven repository / mirror, like Archiva, Artifactory or > Nexus/Proximity. > > Hth, > > Nick 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 "Distribution Management". > > What I do for those external jars is - on the console, when maven doesn't > find a depdency, it always gives you the exact String you need to use to > install it on your local server or to deploy it on your company's remote > server. I always copy this String from the console, then edit it in a text > editor, put the jar in the same folder as the pom, add the name of the pom to > the end of the String, hit enter, the jar gets installed, its poms and > checksums created, when done, I delete the jar I put in the project's folder. > > I've never tried the deploy option, as I am planning to copy my entire > local repository to the remote one, as soon as I am finished migrating to > Maven 2. The install version works perfectly (and I am sure when you set up > distribution management, this works perfectly too). > To set up Distribution Management, Add it to your pom, then set the login > information in your setting.xml, though I wouldn't recommend you to leave > away the password - a) for security reasons b) so that noone can "accidently > upload something" 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 <users@maven.apache.org> > > Betreff: Re: converting from maven1 to maven2, pom for third party jars? > > > 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] > > -- > GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! > Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
