Re: Behavior with multiple goals

2006-02-03 Thread Alex Boisvert

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 goal package run every hour and a goal release
run every day.  Would release happen if it is run after package?  Or
should I set up two different projects for this?

alex



Emmanuel Venisse wrote:

 I don't understand why you set 2 build definitions for the same
 schedule. It will be more logic to delete the second (compile) because
 it's included in package phase.

 As you have 2 build definitions on the same schedule, continuum run
 them separatly. In your case it run compile definition first, and when
 it try to run package definition, scm update return no changes, so
 continuum doesn't do the build.

 Emmanuel

 Alex Boisvert a écrit :

 Hi,

 I'm using continuum 1.0.2 and I've defined two goals for a Maven2
 project:


   Build Definitions

 Goals Arguments POM File Profile Schedule
 From  package --batch-mode pom.xml DEFAULT
 DEFAULT_SCHEDULE Project Edit
 http://release.intalio.com:/continuum/servlet/continuum/target/BuildDefinition.vm/view/BuildDefinition/buildDefinitionId/11/id/11

 | Delete
 http://release.intalio.com:/continuum/servlet/continuum/target/DeleteBuildDefinition.vm/buildDefinitionId/11/id/11/executorId/maven2


 compile --batch-mode pom.xml DEFAULT
 DEFAULT_SCHEDULE Project Edit
 http://release.intalio.com:/continuum/servlet/continuum/target/BuildDefinition.vm/view/BuildDefinition/buildDefinitionId/51/id/11

 | Delete
 http://release.intalio.com:/continuum/servlet/continuum/target/DeleteBuildDefinition.vm/buildDefinitionId/51/id/11/executorId/maven2




 I've discovered today that only the second goal (compile) gets run every
 hour (DEFAULT_SCHEDULE).  The first goal (package; which is flagged as
 default) only executes if I trigger the build manually.

 Is this normal?

 alex






Re: How to make multi module work in continuum

2006-02-03 Thread raghurajan . x . gurunathan
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 : MyMavenPrj
Version : snapshot
 Scm Url: scm:clearcase|Myview|Myconfig_spec

then when i hit the build now

i'm getting the following error?? What am i doing wront, 

ognl.MethodFailedException: Method buildProject failed for object 
[EMAIL PROTECTED] 
[org.apache.maven.continuum.ContinuumException: Project (id=81 doens't 
have a default build definition.]
 at 
ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796)
 at 
ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61)
 at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819)
 at ognl.ASTMethod.getValueBody(ASTMethod.java:75)
 at 
ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170)
 at ognl.SimpleNode.getValue(SimpleNode.java:210)
 at ognl.Ognl.getValue(Ognl.java:333)
 at ognl.Ognl.getValue(Ognl.java:378)
 at ognl.Ognl.getValue(Ognl.java:357)
 at 
org.apache.maven.continuum.web.action.CallApplicationModel.execute(CallApplicationModel.java:72)
 at 
org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:68)
 at 
org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70)
 at 
org.codehaus.plexus.summit.Summit.doGet(Summit.java:54)
 at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
 at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
 at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358)
 at 
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294)
 at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
 at 
org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
 at 
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525)
 at 
org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
 at 
org.mortbay.http.HttpServer.service(HttpServer.java:879)
 at 
org.mortbay.http.HttpConnection.service(HttpConnection.java:789)
 at 
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960)
 at 
org.mortbay.http.HttpConnection.handle(HttpConnection.java:806)
 at 
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218)
 at 
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331)
 at 
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520)
/-- Encapsulated exception \
org.apache.maven.continuum.ContinuumException: Project (id=81 doens't have 
a default build definition.
 at 
org.apache.maven.continuum.DefaultContinuum.buildProject(DefaultContinuum.java:396)
 at 
org.apache.maven.continuum.DefaultContinuum.buildProject(DefaultContinuum.java:381)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:324)
 at ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:491)
 at 
ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:785)
 at 
ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61)
 at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819)
 at ognl.ASTMethod.getValueBody(ASTMethod.java:75)
 at 
ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170)
 at ognl.SimpleNode.getValue(SimpleNode.java:210)
 at ognl.Ognl.getValue(Ognl.java:333)
 at ognl.Ognl.getValue(Ognl.java:378)
 at ognl.Ognl.getValue(Ognl.java:357)
 at 
org.apache.maven.continuum.web.action.CallApplicationModel.execute(CallApplicationModel.java:72)
 at 
org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:68)
 at 
org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70)
 at 
org.codehaus.plexus.summit.Summit.doGet(Summit.java:54)
 at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
 at 

Re: How to make multi module work in continuum

2006-02-03 Thread Emmanuel Venisse



[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 there any example(step-step) somewhere it shows how to add M2project as 
shell project??


Not yet.







Thanks,
Raghurajan G 






Emmanuel Venisse [EMAIL PROTECTED]
02/03/2006 11:19 AM
Please respond to continuum-users

 
To: continuum-users@maven.apache.org
cc: 
Subject:Re: How to make multi module work in continuum





[EMAIL PROTECTED] a écrit :


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



yes, but only on modules that have changes.




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 : MyMavenPrj
   Version : snapshot
Scm Url: scm:clearcase|Myview|Myconfig_spec

then when i hit the build now

i'm getting the following error?? What am i doing wront, 



You must add a build definition. With shell project, we can't add a 
default build definition.




ognl.MethodFailedException: Method buildProject failed for object 
[EMAIL PROTECTED] 
[org.apache.maven.continuum.ContinuumException: Project (id=81 doens't 
have a default build definition.]
at 
ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796)
at 
ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61)

at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819)
at ognl.ASTMethod.getValueBody(ASTMethod.java:75)
at 
ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170)

at ognl.SimpleNode.getValue(SimpleNode.java:210)
at ognl.Ognl.getValue(Ognl.java:333)
at ognl.Ognl.getValue(Ognl.java:378)
at ognl.Ognl.getValue(Ognl.java:357)
at 



org.apache.maven.continuum.web.action.CallApplicationModel.execute(CallApplicationModel.java:72)

at 



org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:68)

at 



org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70)

at 
org.codehaus.plexus.summit.Summit.doGet(Summit.java:54)
at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:595)
at 
javax.servlet.http.HttpServlet.service(HttpServlet.java:688)
at 
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358)
at 



org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294)

at 
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
at 
org.mortbay.http.HttpContext.handle(HttpContext.java:1807)
at 



org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525)

at 
org.mortbay.http.HttpContext.handle(HttpContext.java:1757)
at 
org.mortbay.http.HttpServer.service(HttpServer.java:879)
at 
org.mortbay.http.HttpConnection.service(HttpConnection.java:789)
at 
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960)
at 
org.mortbay.http.HttpConnection.handle(HttpConnection.java:806)
at 



org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218)

at 
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331)
at 
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520)

/-- Encapsulated exception \
org.apache.maven.continuum.ContinuumException: Project (id=81 doens't 


have 


a default build definition.
at 



org.apache.maven.continuum.DefaultContinuum.buildProject(DefaultContinuum.java:396)

at 



org.apache.maven.continuum.DefaultContinuum.buildProject(DefaultContinuum.java:381)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
at 



sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at 



sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)


at java.lang.reflect.Method.invoke(Method.java:324)
at ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:491)
at 
ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:785)
at 
ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61)

at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819)
at ognl.ASTMethod.getValueBody(ASTMethod.java:75)

Re: Error in detecting changes

2006-02-03 Thread Punkin Head
The pom.xml is version 1.34.

[INFO] Scanning for projects...
[INFO]

[INFO] Building WRAT Parent
[INFO]task-segment: [clean, deploy]
[INFO]

[INFO] [clean:clean]
[INFO] [install:install]
[INFO] Installing c:\Program Files\Apache Software Foundation\continuum-
1.0.2\working-directory\108\pom.xml to C:\Documents and
Settings\continuum.MOBILVOX\.m2\repository\com\mobilvox\wrat\application-parent\1.1-SNAPSHOT\application-
parent-1.1-SNAPSHOT.pom
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from mv-repo
Uploading:
file:\\dc103\software\.m2\repository/com/mobilvox/wrat/application-parent/1.1-SNAPSHOT/application-
parent-1.1-20060202.212006-1.pom
5K uploaded
[INFO] Retrieving previous metadata from mv-repo
[INFO] Uploading repository metadata for: 'artifact
com.mobilvox.wrat:application-parent'
[INFO] Retrieving previous metadata from mv-repo
[INFO] Uploading repository metadata for: 'snapshot
com.mobilvox.wrat:application-parent:1.1-SNAPSHOT'
[INFO]

[INFO] BUILD SUCCESSFUL
[INFO]

[INFO] Total time: 1 second
[INFO] Finished at: Thu Feb 02 16:20:06 EST 2006
[INFO] Final Memory: 3M/6M
[INFO]


On 2/3/06, Emmanuel Venisse [EMAIL PROTECTED] wrote:

 Is it your pom.xml that have this version?

 Can you send log traces of a build execution on this project.

 Emmanuel

 Punkin Head a écrit :
  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 [EMAIL PROTECTED] wrote:
 
 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
 
 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
 we
 
 can
 
 see who did what?
 
 Thanks,
 
 Adam
 
 --
 www.punkinshred.net  // punkin'head official homepage
 
 www.myspace.com/punkinhead -- for true shred
 
 
 
 
 
  --
  www.punkinshred.net  // punkin'head official homepage
 
  www.myspace.com/punkinhead -- for true shred
 




--
www.punkinshred.net  // punkin'head official homepage

www.myspace.com/punkinhead -- for true shred