Use a Maven property which is set to the CL number and feed it into the build. This way you can use the property to change the name of your jar as indicated below
Also if you are using a tool such as Hudson for the continuous integration aspect then this produces a report of which CLs triggered a build. We use Hudson with the P4 plugin and works reasonably well. -----Original Message----- From: Richard Chamberlain [mailto:[EMAIL PROTECTED] Sent: 25 April 2008 12:50 To: Maven Users List Subject: RE: perforce numbered unique snapshots Sorry for not being clear. Every time our artefact (jar) is built it gets integration tested against another system. That test cycle pulls in the latest built snapshot and runs tests with it. When something goes wrong with that snapshot it would be nice to instantly know what code was in it. Perforce has a global changelist number (not unlike svn) and it would be good to name my artefact myapp-1.3-SNAPSHOT-12345.jar where 12345 is the perforce changelist number when the build occurred. When the build failed I can sync my code to 12345 and be able to debug it instantly. Richard -----Original Message----- From: Bracewell, Robert [mailto:[EMAIL PROTECTED] Sent: 25 April 2008 12:31 To: Maven Users List Subject: RE: perforce numbered unique snapshots Hi, Can you expand a little? What do you mean by a perforce numbered artefact? Would you not have the potential for several P4 CLs that affect any one artefact? What we do is embed a unique id as a java class which can then be queried via a UI. We also embed this unique id as part of the manifest generation. This unique id then maps back to a datetime stamp which allows us to generate reports of every CL that affected or went into build an artefact be it a jar, ear, war, assembly etc. -- Robert -----Original Message----- From: Richard Chamberlain [mailto:[EMAIL PROTECTED] Sent: 25 April 2008 12:04 To: Maven Users List Subject: perforce numbered unique snapshots Hi all, I think it'd be useful to have perforce changelist numbered snapshots. Has anyone done this? I think the steps needed to do this are: 1) Make a perforce numbered jar for artefactA (maybe using ant) 2) Attach the artefact as the main jar for artefactA 3) Tell the repository that i'm using a unique snapshot for artefactA 4) Work out how i refer to unique snapshots within projectB's dependencies However i'm not sure how to proceed after step 1. Can anyone help me out? Thanks Richard --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
