Hi... Sorry, I have been in meetings all day... let me try to answer. The /trunk/ is ALWAYS the working directory, and is where -SNAPSHOT jar/war/ear files are created from for testing on the Integration environment.
The prepare/perform release process works like this: 1) You start with a current "-SNAPSHOT" - such as your example 0.0.5-SNAPSHOT 2) The "Prepare" copies this off to the new tag location in SVN at the "root version" - 0.0.5 and prepares the trunk to be 0.0.6-SNAPSHOT 3) the "Perform" checks out the code from the new tag/0.0.5 (which is NOT a "-SNAPSHOT") version, builds, packages, and installs this as groupid/artifactid-0.0.5.<packaging> 4) you do a new build (in the trunk) which updates the current continuum project to 0.0.6-SNAPSHOT. The release is always the "root" of the current "-SNAPSHOT" and the SNAPSHOT is updated to the next "working version". We have 174 projects in Continuum now, and do releases all the time - of supporting enterprise .JAR files, and of our WAR and EAR based applications. Louis On Mon, Jul 25, 2011 at 6:14 PM, Paul Davis <pauleda...@gmail.com> wrote: > 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 > -- Dr. Louis Smith, ThD Chief Technology Officer, Kyra InfoTech Colonel, Commemorative Air Force
