The perforce provider does not handle passwords; it is assumed that you are already logged in. We have a special build user who is only allowed to log in from the build server and whose login never expires.
> -----Original Message----- > From: EJ Ciramella [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 14, 2006 9:54 AM > To: Maven Users List > Subject: RE: integration builds and version numbers > > I'm talking about passwords to perforce > > -----Original Message----- > From: Roald Bankras [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 14, 2006 10:55 AM > To: Maven Users List > Subject: RE: integration builds and version numbers > > The website mentioned by Kieran Brady shows how you can store > the scm passwords. > > Roald Bankras > Software Engineer > JTeam b.v. > > -----Original Message----- > From: EJ Ciramella [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 14, 2006 4:40 PM > To: Maven Users List > Subject: RE: integration builds and version numbers > > Ok - got the pdf, but I'm confused. Does this release plugin > need to be configured at the parent or child pom level? What > if our scm tool of choose (perforce) requires passwords? > > -----Original Message----- > From: Roald Bankras [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 14, 2006 10:26 AM > To: Maven Users List > Subject: RE: integration builds and version numbers > > In chapter 7 of the 'better builds with maven' book (downloadable from > www.mergere.com) there is a description on how to use the > release plugin. > The plugin website can be found at > http://maven.apache.org/plugins/maven-release-plugin/ > > Roald Bankras > Software Engineer > JTeam b.v. > > -----Original Message----- > From: EJ Ciramella [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 14, 2006 4:14 PM > To: Maven Users List > Subject: RE: integration builds and version numbers > > I tried both mvn release and mvn release:release - neither exists. > > What is the correct goal? > > -----Original Message----- > From: EJ Ciramella [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 14, 2006 9:51 AM > To: Maven Users List > Subject: RE: integration builds and version numbers > > Where is this documented? I'd like to read more about this. > > -----Original Message----- > From: Roald Bankras [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 14, 2006 3:16 AM > To: Maven Users List > Subject: RE: integration builds and version numbers > > Updating the version numbers in the pom files can be done by > calling the release goal. > > Roald Bankras > Software Engineer > JTeam b.v. > > -----Original Message----- > From: EJ Ciramella [mailto:[EMAIL PROTECTED] > Sent: Monday, June 12, 2006 11:30 PM > To: Maven Users List > Subject: RE: integration builds and version numbers > > Someone must be using CC + M2, no? > > -----Original Message----- > From: EJ Ciramella [mailto:[EMAIL PROTECTED] > Sent: Monday, June 12, 2006 8:01 AM > To: Maven Users List > Subject: integration builds and version numbers > > How are people updating their pom.xml files with version > numbers from say cruisecontrol? > > We have two types of codelines (in perforce) here, project > and release lines. Everything starts out life as a project > then over time one (or > more) projects can be integrated to a release line. > > I'm curious, we're forcefully editing (with the ant replace > task) some templated version.html files to reflect what > version was built. Do I need to be doing this to the pom.xml > files also? > > When something is getting built from a project branch, the > build number looks like this: > > X.<projectbranchname>.<buildnumber> > > So: > > 8.P000001.1 > > In the maven world, all the project branches would look like this: > > <version>X.X-SNAPSHOT</version > > So in the above case - > > <version>8.0-P000001-SNAPSHOT</version> > > And when that goes to release > > <version>8.0.X</version> > > Where X is a build number. > > This has a problem though - I'll have to remember the > dependency order to build and make sure that module "C" gets > built before "B" which is built before "A" (or the replace at > least happens in that order). > > So what are people doing for this? Manually updating before > every build? I _really_ don't want to have to go back to that.... > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.394 / Virus Database: 268.8.3/361 - Release > Date: 6/11/2006 > > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.1.394 / Virus Database: 268.8.3/362 - Release > Date: 6/12/2006 > > > --------------------------------------------------------------------- > 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] > > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.394 / Virus Database: 268.8.4/363 - Release > Date: 6/13/2006 > > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.1.394 / Virus Database: 268.8.4/363 - Release > Date: 6/13/2006 > > > --------------------------------------------------------------------- > 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] > > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.394 / Virus Database: 268.8.4/363 - Release > Date: 6/13/2006 > > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.1.394 / Virus Database: 268.8.4/363 - Release > Date: 6/13/2006 > > > --------------------------------------------------------------------- > 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]
