Return-Path: X-Original-To: apmail-continuum-users-archive@www.apache.org Delivered-To: apmail-continuum-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2623C6499 for ; Tue, 26 Jul 2011 00:18:12 +0000 (UTC) Received: (qmail 40982 invoked by uid 500); 26 Jul 2011 00:18:11 -0000 Delivered-To: apmail-continuum-users-archive@continuum.apache.org Received: (qmail 40909 invoked by uid 500); 26 Jul 2011 00:18:11 -0000 Mailing-List: contact users-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@continuum.apache.org Delivered-To: mailing list users@continuum.apache.org Received: (qmail 40900 invoked by uid 99); 26 Jul 2011 00:18:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jul 2011 00:18:10 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dr.louis.smith@gmail.com designates 209.85.215.177 as permitted sender) Received: from [209.85.215.177] (HELO mail-ey0-f177.google.com) (209.85.215.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Jul 2011 00:18:03 +0000 Received: by eyh6 with SMTP id 6so4277070eyh.8 for ; Mon, 25 Jul 2011 17:17:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=b9tnLReRsg/anfG94/WKR6QxqvkigsjTFDcrG1mH87g=; b=WRmqAIQxrxVI2XygA9+KTEsbtENXvAE127ya+f6gdD8okEVRB8HWuGoXJ9YH1b671z TxmPcqAPAuRebx+fr+xZ7XCMTNnq7DBH/WblAf4ushI7lWEhANvJNGQLyCBllqF7XqqZ pknaFZBoCTD8GwLHNiNWSIASicIovj7AGqhRc= MIME-Version: 1.0 Received: by 10.223.64.80 with SMTP id d16mr7395783fai.86.1311639462981; Mon, 25 Jul 2011 17:17:42 -0700 (PDT) Received: by 10.223.36.201 with HTTP; Mon, 25 Jul 2011 17:17:42 -0700 (PDT) In-Reply-To: <4E2E003F.60906@novyon.org> References: <1311626376.35117.ezmlm@continuum.apache.org> <4E2DD618.3080500@novyon.org> <4E2DECA6.6080404@novyon.org> <4E2DF9A2.4080608@novyon.org> <4E2E003F.60906@novyon.org> Date: Mon, 25 Jul 2011 20:17:42 -0400 Message-ID: Subject: Re: Project prepare / perform From: Louis Smith To: users@continuum.apache.org Content-Type: multipart/alternative; boundary=00151744845c43b1a504a8eddc1b X-Virus-Checked: Checked by ClamAV on apache.org --00151744845c43b1a504a8eddc1b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable re-releasing is a different animal. remember - the process is "copy snapshot of code to NEW svn tag", "Modify trunk", "build from new tag". Since 0.0.3 already exists, and was created from the code in /trunk as of 0.0.3-SNAPSHOT - you have to do something different. You will wind up doing a "point" or "fix" release.. like 0.0.3.1 Ignore all the directories that it creates while it is screwing over your code... all that matters is what winds up finally being deployed to the maven installation/release directory. All the "working files" should remai= n un-touched by human hands. We run continuum jobs at night to clean out all those temporary copies. We'll worry about that after you get a build/release done cleanly first. Better half just got home... and I'm on cooking duty... gotta go. I will b= e happy to write up a full demo if you still have problems. I can get to that tomorrow night. Louis 2011/7/25 Csepregi G=E1bor > I get the concept of the working directory. I got one last question befor= e > giving it up: > > Why does it check out the release into a folder > (working-directory/releases-**1311634791879) and does the mvn deploy from > another one (working-directory/1)? (This completly explains why I get > nullpointerexception when trying to re-release eg. 0.0.3, which has been > prepeared long time ago, but re-releasing it is a valid maven action) I'l= l > try one last thing, giving the working directory argument as a command li= ne > argument on the interface, and see if it will solve it. > > 2011.07.26. 1:30 keltez=E9ssel, Louis Smith =EDrta: > >> The directories are controlled from the configuration screen. >> >> Also check the section for where you are >> publishing >> your releases... you should see a new file there. >> >> The "working directory" is where continuum always does its work.. it wil= l >> be >> // .. looks like >> you >> are doing your first project since yours is data/working-directory/1 >> >> It just checks out what it wants into that directory, does its thing, an= d >> cleans up (sometimes). >> >> 2011/7/25 Csepregi G=E1bor >> >> Thanks for the details, I have compared my pom settings to the continuu= m >>> pom, so now I guess it should not be a problem. The svn also looks good >>> and >>> so is the prepare form. But I get a strange log in the continuum.log >>> regarding the perform step: >>> >>> 2011-07-26 00:59:52,026 [pool-4-thread-1] INFO >>> org.apache.continuum.scm.* >>> *manager.Slf4jScmLogger - Executing: /bin/sh -c cd >>> /opt/www/local/continuum/****apache-continuum-1.4.0/data/**** >>> working-directory >>> && svn --username anthyon --password '*****' --non-interactive checkou= t >>> http://svn./<****artifactId>/tags/-****0.0.6 >>> */data/working-****directory/releases-****1311634791879* >>> 2011-07-26 00:59:52,027 [pool-4-thread-1] INFO >>> org.apache.continuum.scm.* >>> *manager.Slf4jScmLogger - Working directory: >>> /data/working-directory >>> 2011-07-26 00:59:59,024 [pool-4-thread-1] INFO >>> org.apache.continuum.utils. >>> **shell.****DefaultShellCommandHelper - Executing: /bin/sh -c cd >>> */data/working-****directory/1*&& /opt/www/local/continuum/**** >>> maven/bin/mvn >>> clean deploy --no-plugin-updates --batch-mode >>> >>> The release is done from the wrong directory as far as I can tell. All = I >>> did was following your steps, and doing the perform step from the offer= ed >>> 0.0.6 version. Do I have control over these directories somewhere? >>> >>> If I create a build by hand from the project, the version number is >>> updated >>> as expected. So the build itself is working fine. I just wished to do t= he >>> release from the same place, though if it's not working, I can do it fr= om >>> command line or eclipse. >>> >>> 2011.07.26. 0:46 keltez=E9ssel, Louis Smith =EDrta: >>> >>> There are a LOT of moving parts to get in synch for it to work... it c= an >>>> be >>>> a lot of effort to set it up the first time. >>>> >>>> 1) you have to have the correct structure in SVN >>>> project (we use the artifactId) >>>> project/trunk >>>> project/tags >>>> project/branches >>>> project/releases >>>> >>>> 2) you have to have the correct entries in in the pom.xml >>>> >>>> 3) You have to be sure the prepare goes against the correct new tag >>>> base... >>>> make sure the prepare screen is correct: >>>> >>>> SCM Username : correct userid for the project to access SVN >>>> SCM Password : correct password for SVN Access >>>> SCM Tag :- - like sdi-maven-skin-1.0.1 >>>> SCM Tag Base : svn://>>> SCM Comment Prefix >>>> Preparation Goals: clean integration-test >>>> Arguments: Noramlly empty >>>> Build Environment : Your maven as defined in the TOOLS >>>> >>>> It will show release version (the root of the current -SNAPSHOT) >>>> Next Dev version (0.0.1 up from current snapshot) >>>> >>>> If the screen isn't mostly correct without changes - then see #1 and >>>> #2... >>>> get it right first. >>>> >>>> The perform should then create the new /tags/ version - just look at >>>> your >>>> svn repo with tortoise or other tool to confirm. >>>> >>>> Click the perform radio button, and the right release number should >>>> appear >>>> in the box... if so, go for it. If not, go back to #1 >>>> >>>> 2011/7/25 Csepregi G=E1bor >>>> >>>> Hello, >>>> >>>>> thanks, I took a closer look and found more problems. I can use maven >>>>> release plugin from within eclipse so I'm familiar with it. The probl= em >>>>> still exists though with Continuum. >>>>> >>>>> 1. If I use choose from the dropdown the previously prepared release >>>>> version, it simply creates a deploy from trunk. >>>>> 2. If I choose to fill in the parameters myself, the scm tagbase gets >>>>> filled with a wrong url (it starts with scm:svn:http://... instead of >>>>> http://...), but fixing it by hand is not a great deal. But when I hi= t >>>>> the >>>>> button to go with the release, the correct tag is checked out from th= e >>>>> svn, >>>>> and then I get a NullPointerException stacktrace in the continuum.log >>>>> >>>>> 2011-07-26 00:14:31,487 [pool-4-thread-1] INFO >>>>> org.apache.continuum.scm.* >>>>> *manager.Slf4jScmLogger - Working directory: >>>>> /opt/www/local/continuum/** >>>>> apache-continuum-1.4.0/data/******working-directory >>>>> 2011-07-26 00:14:37,025 [Thread-19] ERROR >>>>> taskQueueExecutor#perform-**** >>>>> release >>>>> - Error executing task >>>>> edu.emory.mathcs.backport.******java.util.concurrent.**** >>>>> ExecutionException: >>>>> java.lang.NullPointerException >>>>> at edu.emory.mathcs.backport.******java.util.concurrent.** >>>>> FutureTask.getResult(******FutureTask.java:299) >>>>> at edu.emory.mathcs.backport.******java.util.concurrent.** >>>>> FutureTask.get(FutureTask.******java:118) >>>>> at org.codehaus.plexus.taskqueue.******execution.** >>>>> ThreadedTaskQueueExecutor$******ExecutorRunnable.waitForTask(****** >>>>> ThreadedTaskQueueExecutor.******java:159) >>>>> at org.codehaus.plexus.taskqueue.******execution.** >>>>> ThreadedTaskQueueExecutor$******ExecutorRunnable.run(** >>>>> ThreadedTaskQueueExecutor.******java:127) >>>>> Caused by: java.lang.NullPointerException >>>>> at java.io.File.(File.java:******222) >>>>> at org.apache.continuum.release.******phase.** >>>>> AbstractContinuumRunGoalsPhase******.execute(**** >>>>> AbstractContinuumRunGoalsPhase***** >>>>> *.java:104) >>>>> at org.apache.maven.shared.******release.DefaultReleaseManager= . >>>>> ****** >>>>> perform(DefaultReleaseManager.******java:336) >>>>> at org.apache.maven.shared.******release.DefaultReleaseManager= . >>>>> ****** >>>>> performWithResult(******DefaultReleaseManager.java:******294) >>>>> at org.apache.maven.shared.******release.DefaultReleaseManager= . >>>>> ****** >>>>> performWithResult(******DefaultReleaseManager.java:******579) >>>>> at org.apache.maven.continuum.******release.executors.** >>>>> PerformReleaseTaskExecutor.******execute(****** >>>>> PerformReleaseTaskExecutor.** >>>>> java:88) >>>>> at org.apache.maven.continuum.******release.executors.** >>>>> AbstractReleaseTaskExecutor.******executeTask(**** >>>>> AbstractReleaseTaskExecutor.** >>>>> java:68) >>>>> at org.codehaus.plexus.taskqueue.******execution.** >>>>> ThreadedTaskQueueExecutor$******ExecutorRunnable$1.run(** >>>>> ThreadedTaskQueueExecutor.******java:116) >>>>> at edu.emory.mathcs.backport.******java.util.concurrent.** >>>>> Executors$RunnableAdapter.******call(Executors.java:442) >>>>> at edu.emory.mathcs.backport.******java.util.concurrent.** >>>>> FutureTask.run(FutureTask.******java:176) >>>>> at edu.emory.mathcs.backport.******java.util.concurrent.** >>>>> ThreadPoolExecutor.runWorker(******ThreadPoolExecutor.java:**987) >>>>> at edu.emory.mathcs.backport.******java.util.concurrent.** >>>>> ThreadPoolExecutor$Worker.run(******ThreadPoolExecutor.java:**528) >>>>> at java.lang.Thread.run(Thread.******java:662) >>>>> >>>>> The working directory in question is there, but I could not find the >>>>> line >>>>> 104 of the AbstractContinuumRunGoalsPhase class, yet. I'll try to bui= ld >>>>> a >>>>> version from the continuum svn and see, it the problem still exists. >>>>> (currently I'm using the 1.4.0 beta) >>>>> >>>>> Thanks for the fast reply, >>>>> >>>>> Gabor Csepregi >>>>> >>>>> 2011.07.25. 22:52 keltez=E9ssel, Brent Atkinson =EDrta: >>>>> >>>>> 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/ >>>>>> <**http://maven.apache.org/****plugins/maven-release-plugin/ >>>>>> > >>>>>> <**http://maven.apache.org/****plugins/maven-release-plugin/ >>>>>> <**http://maven.apache.org/**plugins/maven-release-plugin/ >>>>>> > >>>>>> >>>>>> >>>>>> Brent >>>>>> >>>>>> 2011/7/25 Csepregi G=E1bor >>>>>> >>>>>> 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 guid= e, >>>>>>> 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 >>>>>>> >>>>>>> >>>>>>> >>>>>>> >> --=20 Dr. Louis Smith, ThD Chief Technology Officer, Kyra InfoTech Colonel, Commemorative Air Force --00151744845c43b1a504a8eddc1b--