INFO | jvm 1| 2006/02/02 04:20:00 | 2006-02-02 04:20:00,742
[Thread-1] INFO ContinuumScm - Updating project: id:
'108', name 'WRAT Parent'.
INFO | jvm 1| 2006/02/02 04:20:00 | 2006-02-02 04:20:00,789 [Thread-1]
DEBUG ScmManager - cvsRoot:
:pserver
The pom.xml is version 1.34.
[INFO] Scanning for projects...
[INFO]
[INFO] Building WRAT Parent
[INFO]task-segment: [clean, deploy]
[INFO]
[
[EMAIL PROTECTED] a écrit :
Can you please give me more details on your comment
"You must add a build definition. With shell project, we can't add a
default build definition"
Open the project view in Continuum interface
Click on "Add" button in build definition part
set parameters
Is the
Again Thanks for your reply,
If i remove the -N option i think i read somewhere its gonna do build all
modules 2 times? is that right
in case of shell project where do i give my pom url ? coz all its asking
for project name,versin,scm url
so i gave it like this
Project Name : MyMav
Yes, I understand the "package" goal is a superset of the "compile"; I
mostly wanted to understand why I didn't see it happening. Thanks for
your clarification.
Are you saying that if the build definitions were set on different
schedules the behavior would be different?
Let's say I have a goa
Emmannuel noted in the other thread "multi-module maven 2 project" that there
were multi-project improvements being planned.
"Project grouping is a planned feature for 1.1"
"Building dependant projects is a planned feature."
I was also confused about why building the parent module does not build
The version in CVS is 1.34 (with an update by another individual) but, the
Continuum build number is 25. On CVS 1.25 I was the one who commited the
changes and it is those comments that are on the Continuum build changes
page, not the ones from CVS version 1.34.
On 2/3/06, Emmanuel Venisse <[EMAI
What do you mean? What is a CVS revision?
When continuum does a new build, it run the following command 'cvs -f -q update
-d'
A build number is internal to Continuum and cvs doesn't know it.
Emmanuel
Punkin Head a écrit :
When Continuum does a new build, it seems to detect the CVS revision th
When Continuum does a new build, it seems to detect the CVS revision that is
equivalent to the build number. For example, one of our modules is on build
25 but CVS revision 34 and the comments for the changes on the build result
page are from CVS revision 25. Is there a way to match these so that
I don't know for the moment.
Emmanuel
Richard C. L. Li a écrit :
Such a nice feature, will it happens in Continuum 1.1? Or I have to
wait longer?
Regards,
Richard Li
Alex Boisvert wrote:
http://jira.codehaus.org/browse/CONTINUUM-581
Emmanuel Venisse wrote:
It isn't possible but can
No, you must use the maven-scm-plugin with tag mojo, but you can define a
dynamic name for the tag.
Release plugin is for creating release and it update all poms.
File an issue for creating a tag after a successful build. I think it should be independant of
plugins usage.
Emmanuel
dan tran a
11 matches
Mail list logo
