"mvn install" will install your project jar in your local repository, usually it is located at /home/../.m2/repository.
"mvn deploy" will deploy your project in your enterprise repository, but you have to fill the necessary informations in your pom. I have never did it myself because WebDav isn't supported yet but I think there is some guides on the subject. By the way, you should take a look at the Maven lifecycle in the documentation if you want to understand all the important phases. And I don't understand what you mean by generating your pom. If you wrote a pom, you don't need to generate one, it will get deployed automatically with your jar don't worry about it. Generating a pom is useful when you have to use a 3rd party jar not developped with Maven. Hope it's help! On 1/13/06, Gerald Müllan <[EMAIL PROTECTED]> wrote: > Another question is coming up. > > Generating the pom due to adding the -DgeneratePom=true command doesn't help. > The pom isn't near the copied jar in the repository on my machine. > > I think this feature is not provided in the current maven version and > will be added in future releases of maven. Ok, no problem i can do > this by hand. > > Is it possible to automatize this whole process of generating the > stuff to the repository on my machine and loading the things up to the > corporate repo? > > best regards, > > Gerald > > On 1/13/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: > > It's because you don't need Maven-Proxy to setup a company repository > > but most people install Maven-Proxy and their repository at the same > > location. Maven-Proxy is really just a proxy to reduce the downloading > > of jars but since it uses a standard repository layout, usually people > > share the repository location between the two. This way you don't have > > to define a new repository in your configuration. > > > > But if you need it, iou could easily put your corporation repository > > on a totally different server, you would just need to add a repository > > in your pom.xml or in your settings.xml. > > > > Hope it's help > > > > > > On 1/12/06, Man-Chi Leung <[EMAIL PROTECTED]> wrote: > > > yes, i agree with Treloar, > > > > > > in fact, after u have played with Maven for while, very soon, u will > > > start to hit the bottleneck on jar file management. > > > > > > UNLESS, u r play Maven ALONE, otherwise, u will start copying jars > > > from local repository to your friend's local repositories for > > > synchronization. what a wonderful task! > > > > > > Maven Proxy is really the KILLER feature that , I believe, will > > > distinguish very clearly from Ant and motivate all team members to > > > pick up dependency management! > > > > > > I was wondering why maven-proxy is not part of the standard > > > distribution for Maven!! > > > > > > ~manchi > > > > > > > > > On Jan 13, 2006, at 7:39 AM, Treloar, Barrie (SAPOL) wrote: > > > > > > >> -----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] > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > Alexandre Poitras > > Québec, Canada > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Gerald Muellan > Schelleingasse 2/11 > 1040 Vienna, Austria > 0043 699 11772506 > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Alexandre Poitras Québec, Canada --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
