Hi Andy, I recently sent some info the maven-user list about this: http://www.nabble.com/Release-cycle---Maven-release-plugin-usability-td16296 781s177.html#a16321701
--Brian -----Original Message----- From: Andy Dingfelder [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2008 5:08 PM To: [email protected] Subject: [m2eclipse-user] how do people handle version numbers? A bit of background info: 1. My java projects each have a standard 4 digit version number (major-minor-patch-build) and my help/about screens etc can access that for debugging etc. 2. My own jar files that get built have version numbers in the pom: <project> <modelVersion>4.0.0</modelVersion> <groupId>com.mycompany</groupId> <artifactId>thisproject</artifactId> <version>0.0.1</version> creates: thisproject-0.0.1.jar 3. 3rd party required Jar files also have version numbers for example: log4j 1.2.14 <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.14</version> </dependency> 4. The install tool I am using (JExpress) has to know the names of the jar files so it can build the launcher's classpath correctly and can handle dealing with changed files for it's automatic update process. A couple of thoughts: 1. RE Points 1&2 above, there is currently no relationship between my project jar file's version number and the internal build number that I store in an internal constants class file. Has anyone figured out a way to make the pom use a programmatically updated version number instead of hard coding it? The reason I have left my jar at 0.0.1 is that I don't want to have to manually change the version number of the jar every time my internal build # changes. 2. RE point 3, does everyone deploy 3rd party jars in this way? or perhaps just naming the jar log4j.jar might help the deployment process, as if the jar gets updated, the classpath would not change? or is that a bad idea ? 3. Even if I could get the build process to use different version numbers, the jar file names would then be changing, which would complicate my install tool. Has anyone used JExpress or a similar java installer tool and had success with version numbers for these type of issues from a deployment point of view? I like JExpress because it automatically detects and installs your JRE if you are not current and handles automatic updates and uninstalls and works on multiple OSes. If I found a better tool I would be willing to consider switching but for now it is working well for me. Or is there a better way to deal with version numbers that I am missing? Cheers, Ding +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Please consider the environment before printing this email WARNING: This email and any attachments may be confidential and/or privileged. They are intended for the addressee only and are not to be read, used, copied or disseminated by anyone receiving them in error. If you are not the intended recipient, please notify the sender by return email and delete this message and any attachments. The views expressed in this email are those of the sender and do not necessarily reflect the official views of SirTrack. see http://www.sirtrack.com +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
