Return-Path: 
 <users-return-8374-apmail-continuum-users-archive=continuum.apache.org@continuum.apache.org>
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 E6D1766A3
	for <apmail-continuum-users-archive@www.apache.org>;
 Mon, 25 Jul 2011 23:30:49 +0000 (UTC)
Received: (qmail 10258 invoked by uid 500); 25 Jul 2011 23:30:49 -0000
Delivered-To: apmail-continuum-users-archive@continuum.apache.org
Received: (qmail 10221 invoked by uid 500); 25 Jul 2011 23:30:49 -0000
Mailing-List: contact users-help@continuum.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@continuum.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@continuum.apache.org>
List-Post: <mailto:users@continuum.apache.org>
List-Id: <users.continuum.apache.org>
Reply-To: users@continuum.apache.org
Delivered-To: mailing list users@continuum.apache.org
Received: (qmail 10213 invoked by uid 99); 25 Jul 2011 23:30:48 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jul 2011 23:30:48 +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; Mon, 25 Jul 2011 23:30:41 +0000
Received: by eyh6 with SMTP id 6so4236076eyh.8
        for <users@continuum.apache.org>;
 Mon, 25 Jul 2011 16:30:21 -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=u5o/C4sxA1T7aKgG8n5jTIvwlf4u3Wm7Mld9wleYEAI=;
        b=mIW7XNaQ3Kzwj0ui3qnDv9JYVoe7CtKdZF4/LxSG4YFQBJOqIhxZELFPrH5MuY3ZJQ
         1/DTWGBvgH94MbEaIKfX4D1iUj9jer1OpsayDUNuVu/fzx2vSxYLXUvZuolYSG0vChCJ
         aww1otaNgIKAQV4JqeEE141HYtVLoJkEV1rhs=
MIME-Version: 1.0
Received: by 10.223.64.80 with SMTP id d16mr7384982fai.86.1311636621011; Mon,
 25 Jul 2011 16:30:21 -0700 (PDT)
Received: by 10.223.36.201 with HTTP; Mon, 25 Jul 2011 16:30:20 -0700 (PDT)
In-Reply-To: <4E2DF9A2.4080608@novyon.org>
References: <1311626376.35117.ezmlm@continuum.apache.org>
	<4E2DD618.3080500@novyon.org>
	<CALyHw0G8qjwnGdHEVm-sOYwHtKqueO5SSkY3W3FT8aDrQG7Fcg@mail.gmail.com>
	<4E2DECA6.6080404@novyon.org>
	<CAJxTgsf=Wha6U8D6gfVh7x0UsmFbqs3=PmjQN6Mry77a6UOPvg@mail.gmail.com>
	<4E2DF9A2.4080608@novyon.org>
Date: Mon, 25 Jul 2011 19:30:20 -0400
Message-ID: 
 <CAJxTgseYB=1cnQaZiKV8jBb9g8yJVyP4RaQXG7G6ERmy9D5XUw@mail.gmail.com>
Subject: Re: Project prepare / perform
From: Louis Smith <dr.louis.smith@gmail.com>
To: users@continuum.apache.org
Content-Type: multipart/alternative; boundary=00151744845cdeac2204a8ed3242
X-Virus-Checked: Checked by ClamAV on apache.org

--00151744845cdeac2204a8ed3242
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The directories are controlled from the configuration screen.

Also check the <distributionmanagement> section for where you are publishin=
g
your releases... you should see a new file there.

The "working directory" is where continuum always does its work.. it will b=
e
<configured working directory path>/<continuum project #>/ .. looks like yo=
u
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, and
cleans up (sometimes).

2011/7/25 Csepregi G=E1bor <anthyon@novyon.org>

> Thanks for the details, I have compared my pom settings to the continuum
> pom, so now I guess it should not be a problem. The svn also looks good a=
nd
> 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-director=
y
> && svn --username anthyon --password '*****' --non-interactive checkout
> http://svn.<server>/<**artifactId>/tags/<artifactId>-**0.0.6
> *<path>/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:
> <path>/data/working-directory
> 2011-07-26 00:59:59,024 [pool-4-thread-1] INFO  org.apache.continuum.util=
s.
> **shell.**DefaultShellCommandHelper  - Executing: /bin/sh -c cd
> *<path>/data/working-**directory/1* && /opt/www/local/continuum/**maven/b=
in/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 offered
> 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 updat=
ed
> as expected. So the build itself is working fine. I just wished to do the
> release from the same place, though if it's not working, I can do it from
> 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 can
>> 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<SCM>  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 :<artifactId>-<release RVL>  - like sdi-maven-skin-1.0.1
>> SCM Tag Base : svn://<your host url/groupid/artifactid/tags
>> SCM Comment Prefix<empty>
>> 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 you=
r
>> svn repo with tortoise or other tool to confirm.
>>
>> Click the perform radio button, and the right release number should appe=
ar
>> in the box... if so, go for it.  If not, go back to #1
>>
>> 2011/7/25 Csepregi G=E1bor<anthyon@novyon.org>
>>
>>  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 problem
>>> 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 hit
>>> the
>>> button to go with the release, the correct tag is checked out from the
>>> 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.<init>(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 li=
ne
>>> 104 of the AbstractContinuumRunGoalsPhase class, yet. I'll try to build=
 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://mave=
n.apache.org/plugins/maven-release-plugin/>
>>>> >
>>>>
>>>>
>>>> Brent
>>>>
>>>> 2011/7/25 Csepregi G=E1bor<anthyon@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 pleas=
e
>>>>> 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 fo=
r
>>>>> 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 modifie=
s
>>>>> 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

--00151744845cdeac2204a8ed3242--