Hi Brent, How is a user supposed to know the difference when all they see is a button in continuum to release?
Personally, I have never seen a Maven release work ever in continuum nor do I personally know anyone who has been successful with it. Whenever the topic is brought up, as Csepregi did, those asking just get blown off (as a search through the mailing list will verify). I think most people would reasonably assume that using the "maven-release-plugin" is "normal release plugin semantics". On Mon, Jul 25, 2011 at 1:52 PM, Brent Atkinson <batkin...@apache.org>wrote: > Hello, > > This is a question the maven release plugin. Continuum supports releasing > Maven projects using the normal release plugin semantics. For information > about what prepare and perform goals are doing, refer to the corresponding > documentation: > > http://maven.apache.org/plugins/maven-release-plugin/ > > Brent > > 2011/7/25 Csepregi Gábor <anth...@novyon.org> > > > Hi there, > > > > I'm a new user to this list, and browsed the latest mails to find a > > solution to my problem, but my question remained unanswered. So please > > direct me to the link if it has been solved before. > > > > I'm trying to use continuum, and it works quite well so far except for > one > > thing: I cannot make a release with it. I'm following the user guide, but > > the problem I'm facing is strange: > > > > 1. the prepare step creates the tag in my svn as supposed and modifies > the > > pom in the trunk to reflect the next developer version. > > 2. the perform step makes a new deployment from the new developer version > > (eg. the prepare created the tag 0.0.5 and modified the pom to > > 0.0.6-SNAPSHOT, then the perform will create the jar for the new > SNAPSHOT) > > > > Am I missing something there? > > > > Thanks in advance for the answers. > > > > Gabor Csepregi > > > -- Paul E. Davis pauleda...@gmail.com 253-861-7769
