What does stable mean? Ultimately the only thing that matters is that you are happy for testers to test it or users to use it. Don' t jt avoid given things version because its "not" stable.
I just version everything and only "Release" some versions. Not sure how big you team is but consider... you release a snapshot and your colleague is like awesome new feature really needed that... works diligently... you realise theres a mistake and fix it - or even better someone else deploys from the same project with some different changes... you collegue finds that all of the sudden hes broken... and no way to go back... you spend x minutes/hours trying to resolve what should happen next. Now add 10 people with various project interelations... its unmanageable.. you might as well use ant and build everything from source. However if you use the release plugin and release rather than deploy then your collegues can choose when to upgrade and take the integration pain. There are two approaches pessimistic with fixed versions or optimistic using ranges back to work... On Fri, 10 Oct 2008 07:58:12 Qureshi,Shahzad [Ontario] wrote: > Hi all, > > I'm working on a module that is a dependency of our main project. I > created this module as a snapshot since its currently under development > as well and its not a stable version yet. I upload it to our internal > remote repository, however, whenever anyone updates their dependencies > they don't get the latest version of my module, the copy still remains > the same as the previous version until they delete their local copy of > the dependency. > > This is a sample of my module's pom file > > <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>ca.abc</groupId> > <artifactId>list</artifactId> > <version>1.0-SNAPSHOT</version> > <name>some List</name> > <description>XMLBeans created schema jar</description> > </project> > > I use mvn deploy plugin to deploy this file (its an xmlbean created jar > file if anyone cares to know). And this is what I use to deploy the jar > file > > >mvn deploy:deploy-file -Durl=scp://address -DrepositoryId=repo_id > > -Dfile=file.jar -DpomFile=pom.xml > > This part seems to be working fine since it creates a new jar file on > the repo with a new timestamp everytime I deploy the new verison of my > jar file, however the other users can't get the latest copy. > > This is the sample pom file of our main project > <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>ca.abc</groupId> > <artifactId>qc</artifactId> > <packaging>jar</packaging> > <version>2.0</version> > <name>QC</name> > <build> > <plugins> > <plugin> > <artifactId>maven-compiler-plugin</artifactId> > <version>2.0.2</version> > <configuration> > <source>1.6</source> > <target>1.6</target> > </configuration> > </plugin> > </plugins> > </build> > <repositories> > <repository> > <id>repo_id</id> > <url>http://address</url> > </repository> > </repositories> > <dependencies> > <dependency> > <groupId>junit</groupId> > <artifactId>junit</artifactId> > <version>4.3.1</version> > <scope>test</scope> > </dependency> > <dependency> > <groupId>ca.abc</groupId> > <artifactId>list</artifactId> > <version>1.0-SNAPSHOT</version> > <scope>compile</scope> > </dependency> > </dependencies> > </project> > > Any ideas? Or do I've the whole idea of SNAPSHOT wrong? > > > Thank you -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
