Re: Maven 2.0 Cruisecontrol plugin?
According to the plugin matrix (http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Matrix) it hasn't been updated yet, and is listed as low priority. We're going to need it ourselves, so I may just take the time to get some basic functionality. On 10/4/05, Frank Zhao [EMAIL PROTECTED] wrote: We are considering upgrading to Maven 2.0. Can someone tell me whether the current Maven Cruisecontrol plugin v1.7 supprt Maven 2.0 or not? Another question, is there a document showing how to convert Maven 1.0's maven.xml and project.properties files to the pom.xml for Maven 2.0? Thanks in advance, Frank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven 2.0 Cruisecontrol plugin?
We are considering upgrading to Maven 2.0. Can someone tell me whether the current Maven Cruisecontrol plugin v1.7 supprt Maven 2.0 or not? Another question, is there a document showing how to convert Maven 1.0's maven.xml and project.properties files to the pom.xml for Maven 2.0? Thanks in advance, Frank
Re: maven and cruisecontrol
Stephen Gray wrote: Hi, I am trying to use maven to kick off cruisecontrol but Im having a problem with my cvs connection. I am using the following in my project.xml scm:cvs:local:ignored:/home/cvs:devbase which works fine when I run maven on its own. Im getting the following error; BUILD FAILED [exec] File.. /home/stephen/.maven/cache/maven-scm-plugin-1.4.1/plugin.jelly [exec] Element... ant:cvs [exec] Line.. 258 [exec] Column 9 [exec] cvs exited with error code 1 [exec] Command line was [Executing 'cvs' with arguments: [exec] '-d:local:/home/cvs' [exec] '-q' [exec] 'update' [exec] '-Pd' [exec] [exec] The ' characters around the executable and arguments are [exec] not part of the command. does anyone know what the problem is? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] That first line (File) might be showing the cause. If it was file xxx is in the way then you have to delete that file. Oh, to be only half as wonderful as my child thought I was when he was small, and only half as stupid as my teenager now thinks I am. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven and cruisecontrol
I am pretty sure that it is something related to Maven, not CC.. Are you trying both approaches on the same machine? Can you run cvs directly using just the command line arguments that are being passed to the underlying Ant task? Also, can you get CVS modificationset aspect of CC to work properly? Eric On Apr 4, 2005, at 4:50 AM, Stephen Gray wrote: Hi, I am trying to use maven to kick off cruisecontrol but Im having a problem with my cvs connection. I am using the following in my project.xml scm:cvs:local:ignored:/home/cvs:devbase which works fine when I run maven on its own. Im getting the following error; BUILD FAILED [exec] File.. /home/stephen/.maven/cache/maven-scm-plugin-1.4.1/plugin.jelly [exec] Element... ant:cvs [exec] Line.. 258 [exec] Column 9 [exec] cvs exited with error code 1 [exec] Command line was [Executing 'cvs' with arguments: [exec] '-d:local:/home/cvs' [exec] '-q' [exec] 'update' [exec] '-Pd' [exec] [exec] The ' characters around the executable and arguments are [exec] not part of the command. does anyone know what the problem is? - 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]
maven and cruisecontrol
Hi, I am trying to use maven to kick off cruisecontrol but Im having a problem with my cvs connection. I am using the following in my project.xml scm:cvs:local:ignored:/home/cvs:devbase which works fine when I run maven on its own. Im getting the following error; BUILD FAILED [exec] File.. /home/stephen/.maven/cache/maven-scm-plugin-1.4.1/plugin.jelly [exec] Element... ant:cvs [exec] Line.. 258 [exec] Column 9 [exec] cvs exited with error code 1 [exec] Command line was [Executing 'cvs' with arguments: [exec] '-d:local:/home/cvs' [exec] '-q' [exec] 'update' [exec] '-Pd' [exec] [exec] The ' characters around the executable and arguments are [exec] not part of the command. does anyone know what the problem is? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven and CruiseControl results display
Hi, I haven't got any help from the CC-user mailing list so I thought I'd try here as it is Maven related. I have Cruise Control building a Maven-based project regularly. Here's the maven element I'm using: maven mavenscript=PATH\\TO\\maven.bat projectfile=checkout/trunk/project.xml goal=scm:update site / This is a Subversion repository. What I'd like is to have Maven log it's output (from compilation and testing) that is currently going to the console to be saved the log that CruiseControl would then display as build result from the JSP page. So, here are my questions: 1) How do I get Maven to log this output? 2) Which log file should be specified the CC knows is the build output? Also, Maven is automatically running our JUnit tests and putting the output in target/test-reports. The output is one .xml and one .txt file for each test case. I have the following in CC's config.xml: log dir=logs/trunk merge dir=checkout/trunk/target/test-reports// /log but clicking the Test Results tab when looking at CC's JSP results dispays nothing. What do I need to get the unit test results to show up in CC? Thanks much, Guy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven and CruiseControl results display
This is a Subversion repository. What I'd like is to have Maven log it's output (from compilation and testing) that is currently going to the console to be saved the log that CruiseControl would then display as build result from the JSP page. So, here are my questions: 1) How do I get Maven to log this output? 2) Which log file should be specified the CC knows is the build output? I don't know how CC does its thing here. It doesn't show in the build results JSP, but it all appears in the email sent out. You can tweak Maven's logging by giving it a custom log4j configuration, but really CC should be doing something itself with stdout/stderr here, as it does with the mail. Also, Maven is automatically running our JUnit tests and putting the output in target/test-reports. The output is one .xml and one .txt file for each test case. I have the following in CC's config.xml: log dir=logs/trunk merge dir=checkout/trunk/target/test-reports// /log but clicking the Test Results tab when looking at CC's JSP results dispays nothing. What do I need to get the unit test results to show up in CC? This works for me: log merge dir=checkout/core_systems/core_standalone/prs-FDRA/target/test-reports / /log Perhaps you need to double check your logDir in cruise control's web.xml? HTH, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven and CruiseControl results display
Brett Porter wrote: I don't know how CC does its thing here. It doesn't show in the build results JSP, but it all appears in the email sent out. You can tweak Maven's logging by giving it a custom log4j configuration, but really CC should be doing something itself with stdout/stderr here, as it does with the mail. Are you using the htmlemail element instead of email? I'll have to try that then. Weird that the JSP wouldn't show it, seems like kind of a glaring defect. This works for me: log merge dir=checkout/core_systems/core_standalone/prs-FDRA/target/test-reports / /log Perhaps you need to double check your logDir in cruise control's web.xml? I dropped the trailing slash off my dir: log dir=logs/trunk merge dir=checkout/trunk/target/test-reports/ /log to see if that helps. I'm running another build cycle right now. Here is the override.properties I used when building cruisecontrol.war: # This should be the full path to your CruiseControl log directory. # If you are in multi-project mode, there will be multiple sub-dirs # inside this log directory, one for each project. user.log.dir=E:/Development/CruiseControl/logs # This should be the path to your current build status file, # expressed relative to the project's log directory. user.build.status.file=buildstatus.txt # This should be the absolute path to the directory where # additional build artifacts are stored. cruise.build.artifacts.dir=E:/Development/CruiseControl/artifacts jdk1.4=true The comment talks about multi-project mode, but I'm not sure if I've got that enabled properly in CC. I need it as each branch in Subversion needs to be its own CC project apparently. Thanks for your help. Guy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven and CruiseControl results display
It works, I promise! Are you using the latest released version of CC? Maven support really only got there recently. Also, run maven cruisecontrol and inspect the generated config.xml file, you should have something like that... I regualry build all my projects config in CC using that goal... Eric -Original Message- From: Guy Davis [mailto:[EMAIL PROTECTED] Sent: Thursday, January 20, 2005 6:35 PM To: Maven Users List Subject: Re: Maven and CruiseControl results display Brett Porter wrote: I don't know how CC does its thing here. It doesn't show in the build results JSP, but it all appears in the email sent out. You can tweak Maven's logging by giving it a custom log4j configuration, but really CC should be doing something itself with stdout/stderr here, as it does with the mail. Are you using the htmlemail element instead of email? I'll have to try that then. Weird that the JSP wouldn't show it, seems like kind of a glaring defect. This works for me: log merge dir=checkout/core_systems/core_standalone/prs-FDRA/target/test-reports / /log Perhaps you need to double check your logDir in cruise control's web.xml? I dropped the trailing slash off my dir: log dir=logs/trunk merge dir=checkout/trunk/target/test-reports/ /log to see if that helps. I'm running another build cycle right now. Here is the override.properties I used when building cruisecontrol.war: # This should be the full path to your CruiseControl log directory. # If you are in multi-project mode, there will be multiple sub-dirs # inside this log directory, one for each project. user.log.dir=E:/Development/CruiseControl/logs # This should be the path to your current build status file, # expressed relative to the project's log directory. user.build.status.file=buildstatus.txt # This should be the absolute path to the directory where # additional build artifacts are stored. cruise.build.artifacts.dir=E:/Development/CruiseControl/artifacts jdk1.4=true The comment talks about multi-project mode, but I'm not sure if I've got that enabled properly in CC. I need it as each branch in Subversion needs to be its own CC project apparently. Thanks for your help. Guy - 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]
Maven and CruiseControl
Hello, I'm trying to get CruiseControl working for our Maven-controlled build. If I set the CC config.xml to call have a maven entry within the schedule element with a target of site, then the build happens but the checked out tree (via Subversion) isn't updated first. Is there anyone else using Maven, CruiseControl and Subversion. I can get things going with CruiseControl calling a small Ant script which updates the tree, then calls Maven with an exec. This seems like a bit of a hack to me though. Are there better approaches that don't involve using an Ant intermediary? Thanks, Guy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven and CruiseControl
Call first the update of your project I your list of goal to attain schedule interval=30 maven goal=scm:update-project|clean|test projectfile=project.xml mavenscript=c:/maven/bin/maven /maven /schedule Nicolas On Tue, 18 Jan 2005 08:28:20 -0700, Guy Davis [EMAIL PROTECTED] wrote: Hello, I'm trying to get CruiseControl working for our Maven-controlled build. If I set the CC config.xml to call have a maven entry within the schedule element with a target of site, then the build happens but the checked out tree (via Subversion) isn't updated first. Is there anyone else using Maven, CruiseControl and Subversion. I can get things going with CruiseControl calling a small Ant script which updates the tree, then calls Maven with an exec. This seems like a bit of a hack to me though. Are there better approaches that don't involve using an Ant intermediary? Thanks, Guy - 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: Maven and CruiseControl
Thanks for the tip. That worked great. My next concern is having the output from Maven show up in the CC Build Results tab. It looks like Ant logs for CC to a file while this isn't happening for Maven? The downside is that I can see the output in the cmd shell I'm running CC from, but if the build won't compile, other developers can't see the reason from the CC results page. Any ideas? Thanks, Guy Nicolas Chalumeau wrote: Call first the update of your project I your list of goal to attain schedule interval=30 maven goal=scm:update-project|clean|test projectfile=project.xml mavenscript=c:/maven/bin/maven /maven /schedule Nicolas On Tue, 18 Jan 2005 08:28:20 -0700, Guy Davis [EMAIL PROTECTED] wrote: Hello, I'm trying to get CruiseControl working for our Maven-controlled build. If I set the CC config.xml to call have a maven entry within the schedule element with a target of site, then the build happens but the checked out tree (via Subversion) isn't updated first. Is there anyone else using Maven, CruiseControl and Subversion. I can get things going with CruiseControl calling a small Ant script which updates the tree, then calls Maven with an exec. This seems like a bit of a hack to me though. Are there better approaches that don't involve using an Ant intermediary? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven in Cruisecontrol + Out Of Memory error
Hi, First of all...I've already looked for help from the Cruisecontrol community on this one. One good soul from that community helped me for a few days but came to the conclusion that my problem was more of a Maven problem than anything else. Below is the outline of my problem. I'll try to be as succinct as possible, while trying to give all relevant details. I'd really appreciate any input on this problem as I'm very, very frustrated with this at this stage and it's paramount that we get cruisecontrol up and running again. Thank you. ** I'm running cruisecontrol with 10 projects. One of these (the last one) is a TestSuite project for running all our unit tests. Each time I run cruisecontrol I get as far as the last project and then the build fails due to an OutOfMemory error. Prior to this it was failing at the third to last project while attempting a test:compile. So I refactored the source files from scr/test for that project into src/java as it contained no unit tests. Then I got as far as the second to last project with the same result - OutOfMemory at test:compile. Did the same thing and now I get to the TestSuite project. Obviously I cannot refactor this project as it's running unit tests. So...it would appear that test:compile is the culprit. I've tried supplying cruisecontrol with different combinations of memory...512, 1024 etc... PC has 1024 memory. P4. The guy from the cruise community feels that it's Maven that has the problem...perhaps holding onto memory and not letting it go or something. Everything runs fine outside of cruisecontrol. I can run the same goals that cruise is running on each individual project and get no OutOfMemory errors. I've ensured that each of the 10 projects only has 256 as a compiler arg in it's project.properties and reduced the memory supplied to cruisecontrol to 256 also. Still getting OutOfMemory when I get to the Testsuite project. The strange thing is this was all working a short time ago. Now I've spent the last 4 days playing around with this...all to no avail. If anyone has any ideas I'd be very, very grateful for any input. Thanks a lot, Ian. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.766 / Virus Database: 513 - Release Date: 17/09/2004
Re: Maven in Cruisecontrol + Out Of Memory error
giving cruise control more memory won't pass it on to Maven - you need to set MAVEN_OPTS=-Xmx512m or such to increase the memory size for Maven (make sure this is in your environment before starting cruise control though). it's unusual that test:compile would have an out of memory error. What happens when you run the projects outside of cruise control? Are you actually running out of RAM, or just JAva heap? Cheers, Brett On Thu, 30 Sep 2004 11:11:42 +0100, Ian Black [EMAIL PROTECTED] wrote: Hi, First of all...I've already looked for help from the Cruisecontrol community on this one. One good soul from that community helped me for a few days but came to the conclusion that my problem was more of a Maven problem than anything else. Below is the outline of my problem. I'll try to be as succinct as possible, while trying to give all relevant details. I'd really appreciate any input on this problem as I'm very, very frustrated with this at this stage and it's paramount that we get cruisecontrol up and running again. Thank you. ** I'm running cruisecontrol with 10 projects. One of these (the last one) is a TestSuite project for running all our unit tests. Each time I run cruisecontrol I get as far as the last project and then the build fails due to an OutOfMemory error. Prior to this it was failing at the third to last project while attempting a test:compile. So I refactored the source files from scr/test for that project into src/java as it contained no unit tests. Then I got as far as the second to last project with the same result - OutOfMemory at test:compile. Did the same thing and now I get to the TestSuite project. Obviously I cannot refactor this project as it's running unit tests. So...it would appear that test:compile is the culprit. I've tried supplying cruisecontrol with different combinations of memory...512, 1024 etc... PC has 1024 memory. P4. The guy from the cruise community feels that it's Maven that has the problem...perhaps holding onto memory and not letting it go or something. Everything runs fine outside of cruisecontrol. I can run the same goals that cruise is running on each individual project and get no OutOfMemory errors. I've ensured that each of the 10 projects only has 256 as a compiler arg in it's project.properties and reduced the memory supplied to cruisecontrol to 256 also. Still getting OutOfMemory when I get to the Testsuite project. The strange thing is this was all working a short time ago. Now I've spent the last 4 days playing around with this...all to no avail. If anyone has any ideas I'd be very, very grateful for any input. Thanks a lot, Ian. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.766 / Virus Database: 513 - Release Date: 17/09/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven in Cruisecontrol + Out Of Memory error
Hi Brett, Running the maven goals outside of cruise works fine. No problems. Is setting MAVEN_OPTS=-Xmx512m the same as setting maven.compile.compilerargs=-J-mx512m in project.properties? If not, where should the MAVEN_OPTS go? From looking at the tak manager, the memory usage doesn't spike at any point, so I'm guessing that it's Java heap. Thanks. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: 30 September 2004 11:13 To: Maven Users List Subject: Re: Maven in Cruisecontrol + Out Of Memory error giving cruise control more memory won't pass it on to Maven - you need to set MAVEN_OPTS=-Xmx512m or such to increase the memory size for Maven (make sure this is in your environment before starting cruise control though). it's unusual that test:compile would have an out of memory error. What happens when you run the projects outside of cruise control? Are you actually running out of RAM, or just JAva heap? Cheers, Brett On Thu, 30 Sep 2004 11:11:42 +0100, Ian Black [EMAIL PROTECTED] wrote: Hi, First of all...I've already looked for help from the Cruisecontrol community on this one. One good soul from that community helped me for a few days but came to the conclusion that my problem was more of a Maven problem than anything else. Below is the outline of my problem. I'll try to be as succinct as possible, while trying to give all relevant details. I'd really appreciate any input on this problem as I'm very, very frustrated with this at this stage and it's paramount that we get cruisecontrol up and running again. Thank you. ** I'm running cruisecontrol with 10 projects. One of these (the last one) is a TestSuite project for running all our unit tests. Each time I run cruisecontrol I get as far as the last project and then the build fails due to an OutOfMemory error. Prior to this it was failing at the third to last project while attempting a test:compile. So I refactored the source files from scr/test for that project into src/java as it contained no unit tests. Then I got as far as the second to last project with the same result - OutOfMemory at test:compile. Did the same thing and now I get to the TestSuite project. Obviously I cannot refactor this project as it's running unit tests. So...it would appear that test:compile is the culprit. I've tried supplying cruisecontrol with different combinations of memory...512, 1024 etc... PC has 1024 memory. P4. The guy from the cruise community feels that it's Maven that has the problem...perhaps holding onto memory and not letting it go or something. Everything runs fine outside of cruisecontrol. I can run the same goals that cruise is running on each individual project and get no OutOfMemory errors. I've ensured that each of the 10 projects only has 256 as a compiler arg in it's project.properties and reduced the memory supplied to cruisecontrol to 256 also. Still getting OutOfMemory when I get to the Testsuite project. The strange thing is this was all working a short time ago. Now I've spent the last 4 days playing around with this...all to no avail. If anyone has any ideas I'd be very, very grateful for any input. Thanks a lot, Ian. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.766 / Virus Database: 513 - Release Date: 17/09/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.766 / Virus Database: 513 - Release Date: 17/09/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.766 / Virus Database: 513 - Release Date: 17/09/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven in Cruisecontrol + Out Of Memory error
Hi, At http://www.jroller.com/page/carlossg/20040926 you can see two tips to increase memory, e.g. 1) MAVEN_OPTS=-Xmx512m 2) maven.junit.fork=true maven.junit.jvmargs=-Xmx512m Regards Carlos Sanchez A Coruña, Spain http://www.jroller.com/page/carlossg/Weblog Oness Project http://oness.sourceforge.net -Original Message- From: Ian Black [mailto:[EMAIL PROTECTED] Sent: Thursday, September 30, 2004 12:12 PM To: [EMAIL PROTECTED] Subject: Maven in Cruisecontrol + Out Of Memory error Hi, First of all...I've already looked for help from the Cruisecontrol community on this one. One good soul from that community helped me for a few days but came to the conclusion that my problem was more of a Maven problem than anything else. Below is the outline of my problem. I'll try to be as succinct as possible, while trying to give all relevant details. I'd really appreciate any input on this problem as I'm very, very frustrated with this at this stage and it's paramount that we get cruisecontrol up and running again. Thank you. ** ** ** ** ** I'm running cruisecontrol with 10 projects. One of these (the last one) is a TestSuite project for running all our unit tests. Each time I run cruisecontrol I get as far as the last project and then the build fails due to an OutOfMemory error. Prior to this it was failing at the third to last project while attempting a test:compile. So I refactored the source files from scr/test for that project into src/java as it contained no unit tests. Then I got as far as the second to last project with the same result - OutOfMemory at test:compile. Did the same thing and now I get to the TestSuite project. Obviously I cannot refactor this project as it's running unit tests. So...it would appear that test:compile is the culprit. I've tried supplying cruisecontrol with different combinations of memory...512, 1024 etc... PC has 1024 memory. P4. The guy from the cruise community feels that it's Maven that has the problem...perhaps holding onto memory and not letting it go or something. Everything runs fine outside of cruisecontrol. I can run the same goals that cruise is running on each individual project and get no OutOfMemory errors. I've ensured that each of the 10 projects only has 256 as a compiler arg in it's project.properties and reduced the memory supplied to cruisecontrol to 256 also. Still getting OutOfMemory when I get to the Testsuite project. The strange thing is this was all working a short time ago. Now I've spent the last 4 days playing around with this...all to no avail. If anyone has any ideas I'd be very, very grateful for any input. Thanks a lot, Ian. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.766 / Virus Database: 513 - Release Date: 17/09/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven in Cruisecontrol + Out Of Memory error
Thanks a lot Carlos. I've a few things to try now. I'll post back with updates. P.S...I might be crying! -Original Message- From: Carlos Sanchez [mailto:[EMAIL PROTECTED] Sent: 30 September 2004 11:10 To: 'Maven Users List' Subject: RE: Maven in Cruisecontrol + Out Of Memory error Hi, At http://www.jroller.com/page/carlossg/20040926 you can see two tips to increase memory, e.g. 1) MAVEN_OPTS=-Xmx512m 2) maven.junit.fork=true maven.junit.jvmargs=-Xmx512m Regards Carlos Sanchez A Coruña, Spain http://www.jroller.com/page/carlossg/Weblog Oness Project http://oness.sourceforge.net -Original Message- From: Ian Black [mailto:[EMAIL PROTECTED] Sent: Thursday, September 30, 2004 12:12 PM To: [EMAIL PROTECTED] Subject: Maven in Cruisecontrol + Out Of Memory error Hi, First of all...I've already looked for help from the Cruisecontrol community on this one. One good soul from that community helped me for a few days but came to the conclusion that my problem was more of a Maven problem than anything else. Below is the outline of my problem. I'll try to be as succinct as possible, while trying to give all relevant details. I'd really appreciate any input on this problem as I'm very, very frustrated with this at this stage and it's paramount that we get cruisecontrol up and running again. Thank you. ** ** ** ** ** I'm running cruisecontrol with 10 projects. One of these (the last one) is a TestSuite project for running all our unit tests. Each time I run cruisecontrol I get as far as the last project and then the build fails due to an OutOfMemory error. Prior to this it was failing at the third to last project while attempting a test:compile. So I refactored the source files from scr/test for that project into src/java as it contained no unit tests. Then I got as far as the second to last project with the same result - OutOfMemory at test:compile. Did the same thing and now I get to the TestSuite project. Obviously I cannot refactor this project as it's running unit tests. So...it would appear that test:compile is the culprit. I've tried supplying cruisecontrol with different combinations of memory...512, 1024 etc... PC has 1024 memory. P4. The guy from the cruise community feels that it's Maven that has the problem...perhaps holding onto memory and not letting it go or something. Everything runs fine outside of cruisecontrol. I can run the same goals that cruise is running on each individual project and get no OutOfMemory errors. I've ensured that each of the 10 projects only has 256 as a compiler arg in it's project.properties and reduced the memory supplied to cruisecontrol to 256 also. Still getting OutOfMemory when I get to the Testsuite project. The strange thing is this was all working a short time ago. Now I've spent the last 4 days playing around with this...all to no avail. If anyone has any ideas I'd be very, very grateful for any input. Thanks a lot, Ian. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.766 / Virus Database: 513 - Release Date: 17/09/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.766 / Virus Database: 513 - Release Date: 17/09/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.766 / Virus Database: 513 - Release Date: 17/09/2004 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven with CruiseControl
It's windows. It's really odd, because sometimes it works, then the next
build it doesn't,
And then it does (Etc., etc)
I can run the maven build by hand and it's fine, so I'm guessing it
might be CC to blame :(
---Original Message-
--From: Brett Porter [mailto:[EMAIL PROTECTED]
--Sent: 20 May 2004 00:16
--To: 'Maven Users List'
--Subject: RE: Maven with CruiseControl
--
--Works for me... Might be environmental?
--
--Is this on windows or unix?
--
--IS CC running as the user you expect?
--
--- Brett
--
-- -Original Message-
-- From: Nigel Magnay [mailto:[EMAIL PROTECTED]
-- Sent: Wednesday, 19 May 2004 9:15 PM
-- To: [EMAIL PROTECTED]
-- Subject: Maven with CruiseControl
--
--
--
-- I'm getting some very odd behaviour running Maven from CC.
--
-- It seems that every other build, my
-- ${user.home}/build.properties file is not being read, so my build
-- fails, thus 50% of them seem to fail all the time.
--
-- Is there any reason this file would not get read?
--
--
--
---
-- 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: Maven with CruiseControl
On successive tries or when you close the prompt and open it again? I use CC on unix, so I'm not sure I can help more here, although I think dIon has worked with it on Windows quite a bit? - Brett -Original Message- From: Nigel Magnay [mailto:[EMAIL PROTECTED] Sent: Friday, 21 May 2004 5:48 AM To: Maven Users List Subject: RE: Maven with CruiseControl It's windows. It's really odd, because sometimes it works, then the next build it doesn't, And then it does (Etc., etc) I can run the maven build by hand and it's fine, so I'm guessing it might be CC to blame :(
Maven with CruiseControl
I'm getting some very odd behaviour running Maven from CC.
It seems that every other build, my ${user.home}/build.properties file
is not being
read, so my build fails, thus 50% of them seem to fail all the time.
Is there any reason this file would not get read?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven with CruiseControl
Works for me... Might be environmental?
Is this on windows or unix?
IS CC running as the user you expect?
- Brett
-Original Message-
From: Nigel Magnay [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 19 May 2004 9:15 PM
To: [EMAIL PROTECTED]
Subject: Maven with CruiseControl
I'm getting some very odd behaviour running Maven from CC.
It seems that every other build, my
${user.home}/build.properties file is not being read, so my
build fails, thus 50% of them seem to fail all the time.
Is there any reason this file would not get read?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
