At the moment, the relationship is the wrong way around - the release plugin should contact the SCM. That's my fault. I didn't want to mess with the existing release plugin other than to reuse the POM transformer inside there.
Jason is currently working on the release process as well, so I think we should all "sit down" and work out some requirements together with anyone else interested. Between the 3 of us we seem to have a lot of the different use cases covered in the workflow area. scm:prepare-release and scm:perform-release do most of what I need for the moment (although JIRA/Bugzilla integration would be really nice!) Cheers, Brett > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, 3 May 2004 4:13 PM > To: 'Maven Developers List' > Subject: RE: Little glitches in rc2 release process > > > I am not very clear about this: so we use the scm plugin for > performing releases? But not the release plugin, right? > What's the goal? To modify and use the release plugin in the > future? (makes more sense to me - the name is great!). > > I'm asking because I was planning to work on the release > process and release plugin in the near future (but not before 1 week). > > Thanks > -Vincent > > > -----Original Message----- > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > Sent: 03 May 2004 07:59 > > To: 'Maven Developers List' > > Subject: RE: Little glitches in rc2 release process > > > > > > A bug in the changes plugin, already fixed. > > > > > > What's the relationship with the changes plugin? > > > > > > > Sorry, I meant release plugin. > > > > scm:prepare-release utilises changes to transform changes > and release > to > > transform the POM. > > > > - Brett > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
