> -----Original Message----- > From: Man-Chi Leung [mailto:[EMAIL PROTECTED] > Sent: Friday, 13 January 2006 2:24 AM > To: Maven Users List > Subject: Re: Installing 3rd party JARs, how generating the pom? > > to deploy in the local repository, do the following: > > $mvn install:install-file -Dfile=<path-to-file> -DgroupId=<group-id> \ > -DartifactId=<artifact-id> -Dversion=<version> - > Dpackaging=<packaging> > > for exmaple: > mvn install:install-file -Dfile=easymock.jar -DgroupId=org.easymock - > DartifactId=easymock -Dversion=2.0 -Dpackaging=jar -DgeneratePom=true > > > anyway, in the future, it is better to setup a maven-proxy and deploy > all 3rd party jar to a department internal maven repository
You have a local repository, a company repository and then you might have a proxy which unifies the company repository, ibiblio and other repositories. There are two concepts it took me a while to work out. You "install" files to your local repository but you "deploy" to your company repository. As manchi points out you are better deploying these to your company repository so that it can be shared amongst all the developers. To install see http://maven.apache.org/guides/mini/guide-installing-3rd-party-jars.html and include the -DgeneratePom=true as manchi shows. To deploy see http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html e.g.: mvn deploy:deploy-file -DgroupId=GROUP_ID -DartifactId=ARTIFACT_ID \ -Dversion=VERSION_ID -DgeneratePom=true \ -Dpackaging=jar \ -Dfile=PATH/TO/JAR \ -DrepositoryId=YOUR_COMPANYS_REPO_ID \ -Durl=scp://YOUR_COMPANYS_REPO_IP/PATH/TO/REPO The latest version of deploy will now create the checksum files too. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
