RE: How to schedule a nightly build in Maven
You can use MavenBuilder in CC like this. I got this tip from this list. schedule maven mavenscript=c:\maven-1.0\bin\maven.bat projectfile=checkout/myapp/project.xml goal=clean:clean test:test time=2330 / pause day=saturday starttime= endtime=2359/ pause day=sunday starttime= endtime=2359/ /schedule -Original Message- From: Dinko Hadzic [mailto:[EMAIL PROTECTED] Sent: Thursday, September 09, 2004 9:47 AM To: Maven Users List Subject: RE: How to schedule a nightly build in Maven CruiseControl seems like a good choice. It however requires having Ant build scripts, which than again makes Maven unnecessary in this scenario (nightly build system)..? Or am I wrong here? I see that Maven has a plugin for CruiseControl and vice versa, what are the potential advantages of integrating these two tools? Please tolerate my newbie questions ;) What our J2EE project needs is a continous build system tests which creates some kind of notification if the build fails. Thanks for any help -Original Message- From: STRAYER, JON (SBCSI) [mailto:[EMAIL PROTECTED] Sent: 9. september 2004 14:36 To: 'Maven Users List' Subject: RE: How to schedule a nightly build in Maven We use CruiseControl for this. -Original Message- From: Dinko Hadzic [mailto:[EMAIL PROTECTED] Sent: Thursday, September 09, 2004 7:22 AM To: [EMAIL PROTECTED] Subject: How to schedule a nightly build in Maven Hi Is it possible to schedule a periodical nightly build of a J2EE project with Maven, and what is the best approach? Could you please give me some hints to get started? Is CruiseControl the tool I should be looking at, or does this functionality also exist within Maven? Thanks \Dinko - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: checkout-project error=2
most likely it means that cvs executable is not in path. -Original Message- From: Henderson, Jerry L [CC] [mailto:[EMAIL PROTECTED] Sent: Thursday, September 09, 2004 1:57 PM To: Maven Users List Subject: scm:checkout-project error=2 Help. When I try to run maven scm:checkout-project to download any of the maven projects I get a error=2 For example: maven scm:checkout-project -Dmaven.scm.method=cvs -Dmaven.scm.cvs.module=goals-grabber -Dmaven.scm.cvs.root=:pserver:[EMAIL PROTECTED]:/home/ projects/mevenide/scm -Dmaven.scm.checkout.dir=. Results in : java.io.IOException: CreateProcess: cvs -d:pserver:[EMAIL PROTECTED]:/home/projects/mevenide/s cm -q checkout -P goals-grabber error=2 Can someone tell me what I'm doing wrong ? Thanks. Jerald L. Henderson HRD Corporate Staff/UE Infrastructure Staff (913)315-3803 (Office) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
remote jboss:deploy-warfile
I use jboss:deploy-warfile to create and deploy a web application. I got it work on localhost. Then I wanted to deploy it to a remote JBoss by changing maven.jboss.hostname, but it failed. With the following url in the error log, I think it is looking for the war file on C drive on myRemoteServer. But the created war file is on C drive on localhost, not myRemoteServer. http://myRemoteServer:80/jmx-console/HtmlAdaptor?action=invokeOpByNamename= jboss.system:service%3DMainDeployermethodName=deployargType=java.net.URLa rg0=file:C:\build\myapp/../target/myapp.war Then how do you deploy to a remote JBoss instance? Thanks in advance. This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: email maven build log
I switched to maven builder in CC. Problem fixed. It is awesome. Thanks a lot. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, September 02, 2004 12:06 PM To: [EMAIL PROTECTED] Subject: RE: email maven build log Is there a reason you're not using the maven specific capabilities of CruiseControl? i.e. rather than schedule interval=60 ant buildfile=ProjectX-build.xml target=build / /schedule have something like schedule interval=300 maven goal=clean:clean test:test projectfile=S:\fo_tcw_fip\TCW/project.xml mavenscript=C:/Progra~1/Apache~1/Maven1~1.0-R/bin/maven / /schedule -Original Message- From: Liu, Zhihai [mailto:[EMAIL PROTECTED] Sent: 02 September 2004 16:48 To: 'Maven Users List' Subject: RE: email maven build log Thank you, Martijn. I followed your examples and got Maven + CruiseControl running. It is a little off topic, but I have another question. I have a target to run unit tests in cc-build.xml. target name=test depends=prepare exec executable=maven.bat dir=myapp arg line=clean:clean test:test / /exec /target There are some compile errors in the code, but CruiseControl's email publisher still said build successful and skipped unit tests. I noticed you have a check failure step in your example. How does it work? and can you include the error messages in the log file into the email publisher? Thanks in advance. -Original Message- From: Martijn Dashorst [mailto:[EMAIL PROTECTED] Sent: Monday, August 23, 2004 10:39 AM To: Maven Users List Subject: Re: email maven build log Liu, Zhihai wrote: Thank you, Dion. I heard of CruiseControl but am reluctant to switch to it just because of this requirement. That's why I am searching for a quick and easy solution. See the 'pragmatic project automation' example chapter (can't remember the exact link now), for installing and configuring cruisecontrol. On a Windows box it is *very* simple. I had implemented this within 1 hour. My cruisecontrol config: cruisecontrol project name=ProjectX buildafterfailed=false bootstrappers currentbuildstatusbootstrapper file=logs/ProjectX/currentbuildstatus.txt / /bootstrappers modificationset quietperiod=60 cvs localworkingcopy=checkout/ProjectX / /modificationset schedule interval=60 ant buildfile=ProjectX-build.xml target=build / /schedule log dir=logs/ProjectX merge dir=checkout/ProjectX/target/test-reports / /log publishers currentbuildstatuspublisher file=logs/ProjectX/currentbuildstatus.txt / execute command=checkbuild.bat / htmlemail mailhost=mailserver returnaddress=[EMAIL PROTECTED] defaultsuffix=@mailserver buildresultsurl=http://buildserver/cruisecontrol/buildresults/ProjectX; css=d:/cruisecontrol-2.1.6/reporting/jsp/css/cruisecontrol.css xsldir=d:/cruisecontrol-2.1.6/reporting/jsp/xsl logdir=logs/ProjectX always address=user1 / failure address=user2 reportWhenFixed=true / /htmlemail /publishers /project /cruisecontrol ?xml version=1.0? project name=cc-build default=build basedir=checkout target name=build delete dir=ProjectX/ cvs command=co ProjectX cvsRoot=:pserver:[EMAIL PROTECTED]:d:/cvs/ exec executable=maven.bat dir=ProjectX arg line=clean site:deploy/ /exec !-- checks if 'failure' or 'error' exists in the TEST-results.xml files -- exec executable=checkbuild.bat dir=d:/builds/ available file=ProjectX.FAIL filepath=d:/builds property=build.failure/ fail if=build.failure message=Tests failed / /target /project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For more information about Barclays Capital, please visit our web site at http://www.barcap.com. Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message. Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group. Replies to this email
email maven build log
We have a scheduled nightly build. Is there a way to save the build information in a log file and send it by email? I am thinking of using nagEmailAddress and maven:reactor, but not sure if it will do the work. Thanks in advance. This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
pom.siteDirectory
I wanted to define pom.siteDirectory in build.properties to overwrite siteDirectory in project.xml to deploy to a different location, but it did not work. This is what I have in build.properties ... maven.site.deploy.method=fs pom.siteDirectory=C:/app/site ... Maven build always uses the value for siteDirectory in project.xml and ignores my change in build.properties. Any help is greatly appreciated. This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: pom.siteDirectory
Eric, thanks for the prompt response. It works.
-Original Message-
From: Erik Husby [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 10, 2004 4:11 PM
To: Maven Users List
Subject: Re: pom.siteDirectory
Liu, Zhihai wrote:
I wanted to define pom.siteDirectory in build.properties to overwrite
siteDirectory in project.xml to deploy to a different location, but it
did
not work.
This is what I have in build.properties
...
maven.site.deploy.method=fs
pom.siteDirectory=C:/app/site
...
Maven build always uses the value for siteDirectory in project.xml and
ignores my change in build.properties.
Any help is greatly appreciated.
Put in the pom something like
siteDirectory${siteDirectory}/siteDirectory
Then put a default value in project.properties
siteDirectory=defaultSite
Then put in build.properties
siteDirectory=c:/app/site
--
Erik Husby
Team Lead for Software Quality Automation
Broad Institute of MIT and Harvard
Rm. 2192 320 Charles St
Cambridge, MA 02141-2023
mobile: 781.354.6669, office: 617.258.9227, [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
