This is what I did The pom for version 2.0 is
<project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> <modelVersion>4.0.0</modelVersion> <groupId>xx.xy.xz.abc.commons</groupId> <artifactId>abc-commons</artifactId> <version>2.0</version> <name>DMS Commons</name> <description> description of the lib </description> <organization> <name>Environment Canada</name> <url>http://path/</url> </organization> </project> And upload script for 2.0 is mvn deploy:deploy-file -Durl=scp://path -DrepositoryId=maven-repo -Dfile=commons-2.0.jar -DpomFile=pom.xml And pom for version 3.0 is <project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> <modelVersion>4.0.0</modelVersion> <groupId>xx.xy.xz.abc.commons</groupId> <artifactId>abc-commons</artifactId> <version>3.0</version> <name>DMS Commons</name> <description> description of the lib </description> <organization> <name>Environment Canada</name> <url>http://path/</url> </organization> </project> And upload script for 3.0 is mvn deploy:deploy-file -Durl=scp://path -DrepositoryId=maven-repo -Dfile=commons-3.0.jar -DpomFile=pom.xml -------------------------------------------- Shahzad Qureshi Systems Analyst/Programmer Applications Directorate, CIOB Environment Canada 416-739-4702 shahzad.qure...@ec.gc.ca -----Original Message----- From: adasal [mailto:adam.salt...@gmail.com] Sent: Friday, July 31, 2009 3:07 PM To: Maven Users List Subject: Re: Uploading a new version to internal remote repository Are you sure? I think you have misconfigured something. The pom dictates the version of artifact you are using. This doesn't make sense to me. Adam 2009/7/31 Qureshi,Shahzad [Ontario] <shahzad.qure...@ec.gc.ca> > Hi all, > > I've an internal remote repository setup which is working fine. I just > have one confusion. > > I uploaded a internally developed library to the internal remote > repository a few months ago which worked fine. However, now there is a > new version for it available and I wanted to upload the new version > but I also don't want to remove the older version yet as there are few > modules that require the old version. > > I simply updated the version number in the pom file of the library and > updated the file name in the upload script and it was uploaded fine. > > I updated the pom file on my module to the new version, however I > still get the older version downloaded in the module that needs to use > the new version. > > Someone had mentioned to me before that if I use SNAPSHOT I won't get > this problem however, is that the rite approach though? I thought > SNAPSHOT is used only for the libraries/modules that are actively > under development and not for the stable/production versions? > > Hows do log4j for instance do this? I can simply change the version > for log4j in my pom file to whatever I want and I'll get that version. > > > > -------------------------------------------- > Shahzad Qureshi > Systems Analyst/Programmer > Applications Directorate, CIOB > Environment Canada > 416-739-4702 > shahzad.qure...@ec.gc.ca > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
