Re: Building continuum
what are your errors? On 1/2/07, Roald Bankras [EMAIL PROTECTED] wrote: Hey all All the best wishes for 2007! Last year I tried to do some work on continuum. But my checkout of the head failed to build successfully. Then I tried to checkout 1.0.3 but that also failed. Is there something specific I need to do, to make a successful build? Thx Roald Bankras Software Engineer JTeam b.v. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.1/611 - Release Date: 12/31/2006 12:47 PM -- jesse mcconnell [EMAIL PROTECTED]
RE: Building continuum
Continuum-core fails 1 testcase with 2 errors. --- Test set: org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest --- Tests run: 5, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 10.656 sec FAILURE! testCreateProjectsWithModules(org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest) Time elapsed: 1.594 sec FAILURE! junit.framework.AssertionFailedError: expected:1 but was:2 at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:282) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:201) at junit.framework.Assert.assertEquals(Assert.java:207) at org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest.testCreateProjectsWithModules(MavenTwoContinuumProjectBuilderTest.java:184) testCreateProjectWithoutModules(org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest) Time elapsed: 1.406 sec FAILURE! junit.framework.AssertionFailedError: expected:0 but was:1 at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:282) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:201) at junit.framework.Assert.assertEquals(Assert.java:207) at org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest.testCreateProjectWithoutModules(MavenTwoContinuumProjectBuilderTest.java:274) Roald Bankras Software Engineer JTeam b.v. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.2/613 - Release Date: 1/1/2007 2:50 PM
Re: Building continuum
updated trunk builds cleanly for me right now... what o/s jdk and mvn version are you using? and are you sure you don't have local modifications jesse On 1/2/07, Roald Bankras [EMAIL PROTECTED] wrote: Continuum-core fails 1 testcase with 2 errors. --- Test set: org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest --- Tests run: 5, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 10.656 sec FAILURE! testCreateProjectsWithModules(org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest) Time elapsed: 1.594 sec FAILURE! junit.framework.AssertionFailedError: expected:1 but was:2 at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:282) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:201) at junit.framework.Assert.assertEquals(Assert.java:207) at org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest.testCreateProjectsWithModules(MavenTwoContinuumProjectBuilderTest.java:184) testCreateProjectWithoutModules(org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest) Time elapsed: 1.406 sec FAILURE! junit.framework.AssertionFailedError: expected:0 but was:1 at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:282) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:201) at junit.framework.Assert.assertEquals(Assert.java:207) at org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilderTest.testCreateProjectWithoutModules(MavenTwoContinuumProjectBuilderTest.java:274) Roald Bankras Software Engineer JTeam b.v. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.2/613 - Release Date: 1/1/2007 2:50 PM -- jesse mcconnell [EMAIL PROTECTED]
Re: Building continuum
On 1/2/07, Roald Bankras [EMAIL PROTECTED] wrote: I have a clean checkout of the trunk, running on XP with JDK 1.5.0_06 and maven 2.0.4 It also builds fine here on WinXP, JDK 1.5.0_10 and Maven 2.0.4 or 2.0.5-SNAPSHOT. (However, I've seen odd intermittent problems before, especially on Windows.) -- Wendy
RE: Building continuum
Svn is 1.3.1 Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Thierry Lach [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 02, 2007 3:37 PM To: continuum-dev@maven.apache.org Subject: Re: Building continuum What is the svn version you are using? Every attempt I make fails during svn unit test. On 1/2/07, Wendy Smoak [EMAIL PROTECTED] wrote: On 1/2/07, Roald Bankras [EMAIL PROTECTED] wrote: I have a clean checkout of the trunk, running on XP with JDK 1.5.0_06and maven 2.0.4 It also builds fine here on WinXP, JDK 1.5.0_10 and Maven 2.0.4 or 2.0.5-SNAPSHOT. (However, I've seen odd intermittent problems before, especially on Windows.) -- Wendy -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.2/613 - Release Date: 1/1/2007 2:50 PM -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.2/613 - Release Date: 1/1/2007 2:50 PM
RE: Building continuum
I've updated to svn 1.4.2 and jdk 1.5.0_10, but still the same failure. Are there additional environment variable required? Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 02, 2007 3:31 PM To: continuum-dev@maven.apache.org Subject: Re: Building continuum On 1/2/07, Roald Bankras [EMAIL PROTECTED] wrote: I have a clean checkout of the trunk, running on XP with JDK 1.5.0_06 and maven 2.0.4 It also builds fine here on WinXP, JDK 1.5.0_10 and Maven 2.0.4 or 2.0.5-SNAPSHOT. (However, I've seen odd intermittent problems before, especially on Windows.) -- Wendy -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.2/613 - Release Date: 1/1/2007 2:50 PM -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.2/613 - Release Date: 1/1/2007 2:50 PM
Re: Building continuum
I've gotten past the svn problem by installing version 1.4.0 (I was using svn installed with cygwin). Now I'm getting the DataManagermentToolTest failure in http://jira.codehaus.org/browse/CONTINUUM-1092 . I'm running jdk 1.4.1_07 - I'll try it with 1.5.0_04 On 1/2/07, Roald Bankras [EMAIL PROTECTED] wrote: I've updated to svn 1.4.2 and jdk 1.5.0_10, but still the same failure. Are there additional environment variable required? Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 02, 2007 3:31 PM To: continuum-dev@maven.apache.org Subject: Re: Building continuum On 1/2/07, Roald Bankras [EMAIL PROTECTED] wrote: I have a clean checkout of the trunk, running on XP with JDK 1.5.0_06 and maven 2.0.4 It also builds fine here on WinXP, JDK 1.5.0_10 and Maven 2.0.4 or 2.0.5-SNAPSHOT. (However, I've seen odd intermittent problems before, especially on Windows.) -- Wendy -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.2/613 - Release Date: 1/1/2007 2:50 PM -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.2/613 - Release Date: 1/1/2007 2:50 PM
Re: Building continuum
Nope - same failure with 1.5.0 On 1/2/07, Thierry Lach [EMAIL PROTECTED] wrote: I've gotten past the svn problem by installing version 1.4.0 (I was using svn installed with cygwin). Now I'm getting the DataManagermentToolTest failure in http://jira.codehaus.org/browse/CONTINUUM-1092 . I'm running jdk 1.4.1_07 - I'll try it with 1.5.0_04 On 1/2/07, Roald Bankras [EMAIL PROTECTED] wrote: I've updated to svn 1.4.2 and jdk 1.5.0_10, but still the same failure. Are there additional environment variable required? Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] ] Sent: Tuesday, January 02, 2007 3:31 PM To: continuum-dev@maven.apache.org Subject: Re: Building continuum On 1/2/07, Roald Bankras [EMAIL PROTECTED] wrote: I have a clean checkout of the trunk, running on XP with JDK 1.5.0_06 and maven 2.0.4 It also builds fine here on WinXP, JDK 1.5.0_10 and Maven 2.0.4 or 2.0.5-SNAPSHOT . (However, I've seen odd intermittent problems before, especially on Windows.) -- Wendy -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.2/613 - Release Date: 1/1/2007 2:50 PM -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.2/613 - Release Date: 1/1/2007 2:50 PM
Re: Building continuum
Done. Also - opened the file (by accident) with notepad and it looks like the differences are in the line terminators. Added that to the issue also. Hope it helps. On 1/2/07, Wendy Smoak [EMAIL PROTECTED] wrote: On 1/2/07, Thierry Lach [EMAIL PROTECTED] wrote: Nope - same failure with 1.5.0 Please comment on the issue so we know it's still a problem for someone. If you just need to get it to build, you can skip the tests with: -Dmaven.test.skip=true -- Wendy
Building continuum
Hi everyone, Building continuum is kind of a pain and is not working out for me. The problem may be due to the apache snapshot repo being down, but even without a snapshot repo I should be able to build (even if it is trunk). First of all : the maven-release-plugin has been changed, where the shared part has been moved to the shared/maven-release-manager. Since the continuum-release module has a dependency on the SNAPSHOT version, it will not build when you acutally build the SNAPSHOT yourself. I can supply a patch for the changes needed for that, if someone is interested. Running mvn clean install from the root of continuum trunk, doesn't really do a great job either and it is quite confusing on what is used and not used anymore. Any clarification welcomed.. Mvgr, Martin
building continuum
Dear all, I'd like to get my hands diry on continuum, but I cannot build the continuum trunk http://svn.apache.org/repos/asf/maven/continuum/trunk by running mvn clean install Is this a temprary issue or am I doing something wrong? Also, can I compile (and run the tests) while I have a production continuum-1.0.3 running on the default ports? thanks Philippe --- Test set: org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest --- Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 2.773 sec FAILURE! testReleaseSimpleProject(org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest) Time elapsed: 1.724 sec FAILURE! junit.framework.AssertionFailedError: Test dev version at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleaseSimpleProject(ReleaseTaskExecutorTest.java:96) testReleaseSimpleProjectWithNextVersion(org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest) Time elapsed: 0.992 sec FAILURE! junit.framework.AssertionFailedError: Test dev version at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleaseSimpleProjectWithNextVersion(ReleaseTaskExecutorTest.java:132) -- ir. Philippe Faes Ghent University - Department ELIS Sint-Pietersnieuwstraat 41 -- B-9000 Gent Tel:+32 9 264 95 25 - Fax:+32 9 264 35 94 http://www.elis.UGent.be/~pfaes ON5DEU -- LPIC1 -- gpg-key:173720B6
Re: building continuum
Hi Philippe, I wanted to do the same to see if there where any cool new features andran into the same problem. if you do mvn -Dmaven.test.failure.ignore=true package you can grab the war and deploy it tomcat ( or an app server of your choice ) you'll then need to setup 2 jndi jdbc resources which you can see the names for in the log file. I was hoping to see the release stuff like the maestro project server has. I guess this is a feature that has been added by the guys at mergere. Anyway just set the flag and you will get a bit further. Ben On 10/18/06, Philippe Faes [EMAIL PROTECTED] wrote: Dear all, I'd like to get my hands diry on continuum, but I cannot build the continuum trunk http://svn.apache.org/repos/asf/maven/continuum/trunk by running mvn clean install Is this a temprary issue or am I doing something wrong? Also, can I compile (and run the tests) while I have a production continuum-1.0.3 running on the default ports? thanks Philippe --- Test set: org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest --- Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 2.773 sec FAILURE! testReleaseSimpleProject(org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest) Time elapsed: 1.724 sec FAILURE! junit.framework.AssertionFailedError: Test dev version at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleaseSimpleProject(ReleaseTaskExecutorTest.java:96) testReleaseSimpleProjectWithNextVersion(org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest) Time elapsed: 0.992 sec FAILURE! junit.framework.AssertionFailedError: Test dev version at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleaseSimpleProjectWithNextVersion(ReleaseTaskExecutorTest.java:132) -- ir. Philippe Faes Ghent University - Department ELIS Sint-Pietersnieuwstraat 41 -- B-9000 Gent Tel:+32 9 264 95 25 - Fax:+32 9 264 35 94 http://www.elis.UGent.be/~pfaes ON5DEU -- LPIC1 -- gpg-key:173720B6
Re: building continuum
The automated unit testing of continuum-release is very hit and miss. Hard to track down. For some people it works every time. For others it works randomly. Even a few people report that the tests work only after executing them multiple times. What I'd like to know is what the differences in environment are between all of these developers? What OS? What JDK? What version of Maven? etc ... - Joakim ben short wrote: Hi Philippe, I wanted to do the same to see if there where any cool new features andran into the same problem. if you do mvn -Dmaven.test.failure.ignore=true package you can grab the war and deploy it tomcat ( or an app server of your choice ) you'll then need to setup 2 jndi jdbc resources which you can see the names for in the log file. I was hoping to see the release stuff like the maestro project server has. I guess this is a feature that has been added by the guys at mergere. Anyway just set the flag and you will get a bit further. Ben On 10/18/06, Philippe Faes [EMAIL PROTECTED] wrote: Dear all, I'd like to get my hands diry on continuum, but I cannot build the continuum trunk http://svn.apache.org/repos/asf/maven/continuum/trunk by running mvn clean install Is this a temprary issue or am I doing something wrong? Also, can I compile (and run the tests) while I have a production continuum-1.0.3 running on the default ports? thanks Philippe --- Test set: org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest --- Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 2.773 sec FAILURE! testReleaseSimpleProject(org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest) Time elapsed: 1.724 sec FAILURE! junit.framework.AssertionFailedError: Test dev version at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleaseSimpleProject(ReleaseTaskExecutorTest.java:96) testReleaseSimpleProjectWithNextVersion(org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest) Time elapsed: 0.992 sec FAILURE! junit.framework.AssertionFailedError: Test dev version at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleaseSimpleProjectWithNextVersion(ReleaseTaskExecutorTest.java:132) -- ir. Philippe Faes Ghent University - Department ELIS Sint-Pietersnieuwstraat 41 -- B-9000 Gent Tel:+32 9 264 95 25 - Fax:+32 9 264 35 94 http://www.elis.UGent.be/~pfaes ON5DEU -- LPIC1 -- gpg-key:173720B6
Re: building continuum
always works for me on macosx, jdk 1.5, maven 2.0.4 On 10/18/06, Joakim Erdfelt [EMAIL PROTECTED] wrote: The automated unit testing of continuum-release is very hit and miss. Hard to track down. For some people it works every time. For others it works randomly. Even a few people report that the tests work only after executing them multiple times. What I'd like to know is what the differences in environment are between all of these developers? What OS? What JDK? What version of Maven? etc ... - Joakim ben short wrote: Hi Philippe, I wanted to do the same to see if there where any cool new features andran into the same problem. if you do mvn -Dmaven.test.failure.ignore=true package you can grab the war and deploy it tomcat ( or an app server of your choice ) you'll then need to setup 2 jndi jdbc resources which you can see the names for in the log file. I was hoping to see the release stuff like the maestro project server has. I guess this is a feature that has been added by the guys at mergere. Anyway just set the flag and you will get a bit further. Ben On 10/18/06, Philippe Faes [EMAIL PROTECTED] wrote: Dear all, I'd like to get my hands diry on continuum, but I cannot build the continuum trunk http://svn.apache.org/repos/asf/maven/continuum/trunk by running mvn clean install Is this a temprary issue or am I doing something wrong? Also, can I compile (and run the tests) while I have a production continuum-1.0.3 running on the default ports? thanks Philippe --- Test set: org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest --- Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 2.773 sec FAILURE! testReleaseSimpleProject(org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest) Time elapsed: 1.724 sec FAILURE! junit.framework.AssertionFailedError: Test dev version at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleaseSimpleProject(ReleaseTaskExecutorTest.java:96) testReleaseSimpleProjectWithNextVersion(org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest) Time elapsed: 0.992 sec FAILURE! junit.framework.AssertionFailedError: Test dev version at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleaseSimpleProjectWithNextVersion(ReleaseTaskExecutorTest.java:132) -- ir. Philippe Faes Ghent University - Department ELIS Sint-Pietersnieuwstraat 41 -- B-9000 Gent Tel:+32 9 264 95 25 - Fax:+32 9 264 35 94 http://www.elis.UGent.be/~pfaes ON5DEU -- LPIC1 -- gpg-key:173720B6 -- jesse mcconnell [EMAIL PROTECTED]
Re: building continuum
If somone could document the jndi resources and how to configure them in tomcat 5.5 that would be very nice. I couldn't figure it out, and am currently running it with: mvn jetty:run continuum.log Christian. ben short wrote: Hi Philippe, I wanted to do the same to see if there where any cool new features andran into the same problem. if you do mvn -Dmaven.test.failure.ignore=true package you can grab the war and deploy it tomcat ( or an app server of your choice ) you'll then need to setup 2 jndi jdbc resources which you can see the names for in the log file. I was hoping to see the release stuff like the maestro project server has. I guess this is a feature that has been added by the guys at mergere. Anyway just set the flag and you will get a bit further. Ben On 10/18/06, Philippe Faes [EMAIL PROTECTED] wrote: Dear all, I'd like to get my hands diry on continuum, but I cannot build the continuum trunk http://svn.apache.org/repos/asf/maven/continuum/trunk by running mvn clean install Is this a temprary issue or am I doing something wrong? Also, can I compile (and run the tests) while I have a production continuum-1.0.3 running on the default ports? thanks Philippe --- Test set: org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest --- Tests run: 2, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 2.773 sec FAILURE! testReleaseSimpleProject(org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest) Time elapsed: 1.724 sec FAILURE! junit.framework.AssertionFailedError: Test dev version at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleaseSimpleProject(ReleaseTaskExecutorTest.java:96) testReleaseSimpleProjectWithNextVersion(org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest) Time elapsed: 0.992 sec FAILURE! junit.framework.AssertionFailedError: Test dev version at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.apache.maven.continuum.release.executors.ReleaseTaskExecutorTest.testReleaseSimpleProjectWithNextVersion(ReleaseTaskExecutorTest.java:132) -- ir. Philippe Faes Ghent University - Department ELIS Sint-Pietersnieuwstraat 41 -- B-9000 Gent Tel:+32 9 264 95 25 - Fax:+32 9 264 35 94 http://www.elis.UGent.be/~pfaes ON5DEU -- LPIC1 -- gpg-key:173720B6 -- *christian** gruber + process coach and architect* *Israfil Consulting Services Corporation* *email** [EMAIL PROTECTED] + bus 905.640.1119 + mob 416.998.6023*
Re: FYI: building continuum today
The build works fine on windows and linux. Emmanuel Bob Herrmann a écrit : I checked out contiuum this morning and did a build... I get this... sh build.xml # I'm using cygwin on win2k. ... There was no such logger 'org.apache.maven.artifact.transform.ArtifactTransforma tion:latest' 15282461. [2006.03.15 10:13:50] Used 28859ms [surefire] Running org.apache.maven.continuum.it.ShellIntegrationTest [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 28.891 sec Results : [surefire] Tests run: 5, Failures: 3, Errors: 0 [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] There are some test failure. [INFO] - --- [INFO] For more information, run Maven with the -e switch [INFO] - --- [INFO] Total time: 36 minutes 8 seconds [INFO] Finished at: Wed Mar 15 10:13:51 EST 2006 [INFO] Final Memory: 57M/63M [INFO] - ---
FYI: building continuum today
I checked out contiuum this morning and did a build... I get this... sh build.xml # I'm using cygwin on win2k. ... There was no such logger 'org.apache.maven.artifact.transform.ArtifactTransforma tion:latest' 15282461. [2006.03.15 10:13:50] Used 28859ms [surefire] Running org.apache.maven.continuum.it.ShellIntegrationTest [surefire] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 28.891 sec Results : [surefire] Tests run: 5, Failures: 3, Errors: 0 [INFO] - --- [ERROR] BUILD ERROR [INFO] - --- [INFO] There are some test failure. [INFO] - --- [INFO] For more information, run Maven with the -e switch [INFO] - --- [INFO] Total time: 36 minutes 8 seconds [INFO] Finished at: Wed Mar 15 10:13:51 EST 2006 [INFO] Final Memory: 57M/63M [INFO] - ---
Re: problem building continuum
oops, sorry ;-)
On 2/3/06, Emmanuel Venisse [EMAIL PROTECTED] wrote:
no, the pb is in continuum build, not in continuum execution
Emmanuel
dan tran a écrit :
${continuum.home}/conf/wrapper.conf on win and linux i think
-Dan
On 2/2/06, Bob Herrmann [EMAIL PROTECTED] wrote:
Progress, but not yet happiness. I'm running Out of Memory when the
build is running.
I hunted down (google); activation, mail, jta, connector (note connector
is named connector-api on the maven mini guide, but is just connector in
the build)
mvn install:install-file -Dfile=jta-1_0_1B-classes.zip
-DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar
-DgroupId=javax.transaction
# I add connector with both names... Once using the maven's
recommended naming, once using what Continuum requires
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector-api -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=/ul/javamail-1_3_3_01.zip
-DartifactId=mail -Dversion=1.3.2 -Dpackaging=jar -DgroupId=javax.mail
mvn install:install-file -Dfile=/ul/jaf-1_0_2-upd2.zip
-DartifactId=activation -Dversion=1.0.2 -Dpackaging=jar
-DgroupId=javax.activation
I then I started again,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
2006-02-02 21:30:17,967 [main] INFO RDBMS -
Validated 1 unique key(s) for table PROJECTNOTIFIER
2006-02-02 21:30:21,639 [main] ERROR SCHEMA - An
exception was thrown while adding/validating class(es) : Java exception:
': java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
2006-02-02 21:30:21,639 [main] ERROR SCHEMA -
SQL Exception: Java exception: ': java.lang.OutOfMemoryError'.
2006-02-02 21:30:22,351 [main] ERROR SCHEMA -
Failed initialising database. Exception : An exception was thrown while
adding/validating class(es) : Java exception: ':
java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
...
I imagine I need to jam -Xmx1g somewhere, but I'm not sure how to set
that in the right place. Help?
Thanks
-bob
Emmanuel Venisse wrote:
Continuum use some SUN jars that can't be redistributed. So you need
to download them from sun site and copy them in the correct group in
your repository like describe there :
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html
Emmanuel
Bob Herrmann a écrit :
ok,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
required artifacts missing:
javax.resource:connector:jar:1.0
javax.transaction:jta:jar:1.0.1B
for the artifact:
org.codehaus.mojo:maven-jpox-plugin:maven-plugin:1.0.1
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
snapshots (http://snapshots.maven.codehaus.org/maven2)
Why am I getting these missing resources? I'm following the
building continuum instructions,
http://maven.apache.org/continuum/guides/development/guide-build-continuum.html
and dont see any reference to needed external stuff. (I did already
put maven-2.0.2 in my path.)
Cheers
-bob
Re: problem building continuum
Emmanuel Venisse wrote:
hmm, weird. You aren't the only one with this problem. I can build
continuum with 256Mo assigned to jvm.
If you want to increase memory, you need to set MAVEN_OPTS env var,
it's used by mvn.
ok, I still get an error when the tests run.
$ export MAVEN_OPTS=-Xmx500m
$ export PATH=$PATH:/usr/local/maven-2.0.2/bin
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
2006-02-03 11:43:35,417 [main] INFO Continuum -
Continuum 1.0.3-SNAPSHOT started!
...
2006-02-03 11:43:35,746 [main] INFO ContinuumInitializer -
Continuum initializer running ...
2006-02-03 11:43:36,076 [main] INFO SchedulesActivator -
Activating schedules ...
2006-02-03 11:43:36,082 [main] WARN ContinuumScheduler -
Will not schedule this job as a job {DEFAULT_SCHEDULE:DEFAULT} already
exists.
2006-02-03 11:43:36,286 [main] INFO SchedulesActivator - null
2006-02-03 11:43:36,286 [main] INFO PlexusContainer-
Loading on start [role,roleHint]:
[org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor,build-project]
2006-02-03 11:43:36,419 [main] ERROR VelocityComponent -
ResourceManager.getResource() parse exception:
org.apache.velocity.exception.ParseErrorException: Lexical error:
org.apache.velocity.runtime.parser.TokenMgrError: Lexical error at line
121, column 17. Encountered: EOF after :
-
this realm = plexus.core
urls[0] =
file:/usr/local/continuum-1.0.x/continuum-core-it/target/level1/level2/plexus-home/../../../../../continuum-web/src/main/resources/localization/
Number of imports: 0
-
[surefire] Running org.apache.maven.continuum.it.MavenTwoIntegrationTest
[surefire] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 9.513 sec
FAILURE !!
Results :
[surefire] Tests run: 5, Failures: 0, Errors: 5
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] There are some test failure.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 6 minutes 5 seconds
[INFO] Finished at: Fri Feb 03 11:43:36 EST 2006
[INFO] Final Memory: 77M/138M
[INFO]
Re: problem building continuum
${continuum.home}/conf/wrapper.conf on win and linux i think
-Dan
On 2/2/06, Bob Herrmann [EMAIL PROTECTED] wrote:
Progress, but not yet happiness. I'm running Out of Memory when the
build is running.
I hunted down (google); activation, mail, jta, connector (note connector
is named connector-api on the maven mini guide, but is just connector in
the build)
mvn install:install-file -Dfile=jta-1_0_1B-classes.zip
-DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar
-DgroupId=javax.transaction
# I add connector with both names... Once using the maven's
recommended naming, once using what Continuum requires
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector-api -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=/ul/javamail-1_3_3_01.zip
-DartifactId=mail -Dversion=1.3.2 -Dpackaging=jar -DgroupId=javax.mail
mvn install:install-file -Dfile=/ul/jaf-1_0_2-upd2.zip
-DartifactId=activation -Dversion=1.0.2 -Dpackaging=jar
-DgroupId=javax.activation
I then I started again,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
2006-02-02 21:30:17,967 [main] INFO RDBMS -
Validated 1 unique key(s) for table PROJECTNOTIFIER
2006-02-02 21:30:21,639 [main] ERROR SCHEMA - An
exception was thrown while adding/validating class(es) : Java exception:
': java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
2006-02-02 21:30:21,639 [main] ERROR SCHEMA -
SQL Exception: Java exception: ': java.lang.OutOfMemoryError'.
2006-02-02 21:30:22,351 [main] ERROR SCHEMA -
Failed initialising database. Exception : An exception was thrown while
adding/validating class(es) : Java exception: ':
java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
...
I imagine I need to jam -Xmx1g somewhere, but I'm not sure how to set
that in the right place. Help?
Thanks
-bob
Emmanuel Venisse wrote:
Continuum use some SUN jars that can't be redistributed. So you need
to download them from sun site and copy them in the correct group in
your repository like describe there :
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html
Emmanuel
Bob Herrmann a écrit :
ok,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
required artifacts missing:
javax.resource:connector:jar:1.0
javax.transaction:jta:jar:1.0.1B
for the artifact:
org.codehaus.mojo:maven-jpox-plugin:maven-plugin:1.0.1
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
snapshots (http://snapshots.maven.codehaus.org/maven2)
Why am I getting these missing resources? I'm following the
building continuum instructions,
http://maven.apache.org/continuum/guides/development/guide-build-continuum.html
and dont see any reference to needed external stuff. (I did already
put maven-2.0.2 in my path.)
Cheers
-bob
Re: problem building continuum
$ find . -name wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/solaris/wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/win32/wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/linux/wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/macosx/wrapper.conf
I tried changing the linux one (I'm running on Fedora 4), but I get identical results. Note that continuum is started when being built by maven. So I suspect the wrapper stuff is not used. I will attach result.log to this message (for those inclined to dig into what is not getting enough memory.)
Can anyone tell me how to raise the memory so I don't get these out of memory
errors when building contiuum?
Thanks
-bob
dan tran wrote:
${continuum.home}/conf/wrapper.conf on win and linux i think
-Dan
On 2/2/06, Bob Herrmann [EMAIL PROTECTED] wrote:
Progress, but not yet happiness. I'm running Out of Memory when the
build is running.
I hunted down (google); activation, mail, jta, connector (note connector
is named connector-api on the maven mini guide, but is just connector in
the build)
mvn install:install-file -Dfile=jta-1_0_1B-classes.zip
-DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar
-DgroupId=javax.transaction
# I add connector with both names... Once using the maven's
recommended naming, once using what Continuum requires
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector-api -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=/ul/javamail-1_3_3_01.zip
-DartifactId=mail -Dversion=1.3.2 -Dpackaging=jar -DgroupId=javax.mail
mvn install:install-file -Dfile=/ul/jaf-1_0_2-upd2.zip
-DartifactId=activation -Dversion=1.0.2 -Dpackaging=jar
-DgroupId=javax.activation
I then I started again,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
2006-02-02 21:30:17,967 [main] INFO RDBMS -
Validated 1 unique key(s) for table PROJECTNOTIFIER
2006-02-02 21:30:21,639 [main] ERROR SCHEMA - An
exception was thrown while adding/validating class(es) : Java exception:
': java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
2006-02-02 21:30:21,639 [main] ERROR SCHEMA -
SQL Exception: Java exception: ': java.lang.OutOfMemoryError'.
2006-02-02 21:30:22,351 [main] ERROR SCHEMA -
Failed initialising database. Exception : An exception was thrown while
adding/validating class(es) : Java exception: ':
java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
...
I imagine I need to jam -Xmx1g somewhere, but I'm not sure how to set
that in the right place. Help?
Thanks
-bob
Emmanuel Venisse wrote:
Continuum use some SUN jars that can't be redistributed. So you need
to download them from sun site and copy them in the correct group in
your repository like describe there :
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html
Emmanuel
Bob Herrmann a écrit :
ok,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
required artifacts missing:
javax.resource:connector:jar:1.0
javax.transaction:jta:jar:1.0.1B
for the artifact:
org.codehaus.mojo:maven-jpox-plugin:maven-plugin:1.0.1
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
snapshots (http://snapshots.maven.codehaus.org/maven2)
Why am I getting these missing resources? I'm following the
building continuum instructions,
http://maven.apache.org/continuum/guides/development/guide-build-continuum.html
and dont see any reference to needed external stuff. (I did already
put maven-2.0.2 in my path.)
Cheers
-bob
result.log.gz
Description: GNU Zip compressed data
Re: problem building continuum
did you take a look at continuum install directory/conf/wrapper.conf ?
-Dan
On 2/2/06, Bob Herrmann [EMAIL PROTECTED] wrote:
$ find . -name wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/solaris/wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/win32/wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/linux/wrapper.conf
./continuum-plexus-application/target/plexus-test-runtime/bin/macosx/wrapper.conf
I tried changing the linux one (I'm running on Fedora 4), but I get
identical results. Note that continuum is started when being built by
maven. So I suspect the wrapper stuff is not used. I will attach
result.log to this message (for those inclined to dig into what is not
getting enough memory.)
Can anyone tell me how to raise the memory so I don't get these out
of memory errors when building contiuum?
Thanks
-bob
dan tran wrote:
${continuum.home}/conf/wrapper.conf on win and linux i think
-Dan
On 2/2/06, Bob Herrmann [EMAIL PROTECTED] wrote:
Progress, but not yet happiness. I'm running Out of Memory when the
build is running.
I hunted down (google); activation, mail, jta, connector (note connector
is named connector-api on the maven mini guide, but is just connector in
the build)
mvn install:install-file -Dfile=jta-1_0_1B-classes.zip
-DartifactId=jta -Dversion=1.0.1B -Dpackaging=jar
-DgroupId=javax.transaction
# I add connector with both names... Once using the maven's
recommended naming, once using what Continuum requires
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector-api -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=j2ee_connector-1_0-fr-class.zip
-DartifactId=connector -Dversion=1.0 -Dpackaging=jar
-DgroupId=javax.resource
mvn install:install-file -Dfile=/ul/javamail-1_3_3_01.zip
-DartifactId=mail -Dversion=1.3.2 -Dpackaging=jar -DgroupId=javax.mail
mvn install:install-file -Dfile=/ul/jaf-1_0_2-upd2.zip
-DartifactId=activation -Dversion=1.0.2 -Dpackaging=jar
-DgroupId=javax.activation
I then I started again,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
2006-02-02 21:30:17,967 [main] INFO RDBMS -
Validated 1 unique key(s) for table PROJECTNOTIFIER
2006-02-02 21:30:21,639 [main] ERROR SCHEMA - An
exception was thrown while adding/validating class(es) : Java exception:
': java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
2006-02-02 21:30:21,639 [main] ERROR SCHEMA -
SQL Exception: Java exception: ': java.lang.OutOfMemoryError'.
2006-02-02 21:30:22,351 [main] ERROR SCHEMA -
Failed initialising database. Exception : An exception was thrown while
adding/validating class(es) : Java exception: ':
java.lang.OutOfMemoryError'.
java.lang.OutOfMemoryError
...
I imagine I need to jam -Xmx1g somewhere, but I'm not sure how to set
that in the right place. Help?
Thanks
-bob
Emmanuel Venisse wrote:
Continuum use some SUN jars that can't be redistributed. So you need
to download them from sun site and copy them in the correct group in
your repository like describe there :
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html
Emmanuel
Bob Herrmann a écrit :
ok,
$ svn co
http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/
$ cd continuum-1.0.x
$ sh build.sh
...
[WARNING] Unable to get resource from repository central
(http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
required artifacts missing:
javax.resource:connector:jar:1.0
javax.transaction:jta:jar:1.0.1B
for the artifact:
org.codehaus.mojo:maven-jpox-plugin:maven-plugin:1.0.1
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
snapshots (http://snapshots.maven.codehaus.org/maven2)
Why am I getting these missing resources? I'm following the
building continuum instructions,
http://maven.apache.org/continuum/guides/development/guide-build-continuum.html
and dont see any reference to needed external stuff. (I did already
put maven-2.0.2 in my path.)
Cheers
-bob
Re: problem building continuum
Continuum use some SUN jars that can't be redistributed. So you need to download them from sun site and copy them in the correct group in your repository like describe there : http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html Emmanuel Bob Herrmann a écrit : ok, $ svn co http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-1.0.x/ $ cd continuum-1.0.x $ sh build.sh ... [WARNING] Unable to get resource from repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. required artifacts missing: javax.resource:connector:jar:1.0 javax.transaction:jta:jar:1.0.1B for the artifact: org.codehaus.mojo:maven-jpox-plugin:maven-plugin:1.0.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) Why am I getting these missing resources? I'm following the building continuum instructions, http://maven.apache.org/continuum/guides/development/guide-build-continuum.html and dont see any reference to needed external stuff. (I did already put maven-2.0.2 in my path.) Cheers -bob
Re: problem building continuum
Why do you want to build sources? Emmanuel Thats a good question. I wanted to change the build report to be briefer. In particular we like to keep the Subject line as ProjcectName BUILD-NUM PASS. We also like the summary to just include the tests that fail (our project has 3000 tests.) I'm using the ant builder. We also would like the list of changes to include check in comments. (This isnt working currently under Starteam.) So I might cowboy in there and have it use the build report to lookup the last comment. Not perfect, but would work until something gets fixed in the Starteam driver. Cheers -bob
Re: problem building continuum
... and we certainly encourage folks wanting to do that. Even more so if they want to contribute changes back :) Email customisation would be a useful feature to have. I think the main thing we try to discourage is people just wanting to check out the latest features building from sources - that's what the integration builds are for. Cheers, Brett Bob Herrmann wrote: Why do you want to build sources? Emmanuel Thats a good question. I wanted to change the build report to be briefer. In particular we like to keep the Subject line as ProjcectName BUILD-NUM PASS. We also like the summary to just include the tests that fail (our project has 3000 tests.) I'm using the ant builder. We also would like the list of changes to include check in comments. (This isnt working currently under Starteam.) So I might cowboy in there and have it use the build report to lookup the last comment. Not perfect, but would work until something gets fixed in the Starteam driver. Cheers -bob
Re: problem building continuum
It's a connection problem with ibiblio Retry. but this code isn't stable and you won't can use the generated war. Emmanuel Bob Herrrmann a écrit : I downloaded maven 2.0.2 and put it in my path. $ svn co http://svn.apache.org/repos/asf/maven/continuum/trunk/ continuum ... $ sh build.sh [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Continuum Parent Project [INFO] Continuum Model [INFO] Continuum API [INFO] Continuum Test [INFO] Continuum Notifiers [INFO] Continuum Notifier API [INFO] Continuum Store [INFO] Continuum Core [INFO] Continuum Cruise Control Importer [INFO] Continuum XMLRPC Interface [INFO] Continuum MSN Notifier [INFO] Continuum Jabber Notifier [INFO] Continuum IRC Notifier [INFO] Continuum Web APP [INFO] Continuum Core Integration Test [INFO] Searching repository for plugin with prefix: 'clean'. [INFO] org.apache.maven.plugins: checking for updates from central [INFO] org.codehaus.mojo: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from central Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.0/maven-clean-plugin-2.0.pom 470b downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugin-parent/2.0/maven-plugin-parent-2.0.pom 6K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.0/maven-clean-plugin-2.0.jar 5K downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-maven-plugin/1.1.3/plexus-maven-plugin-1.1.3.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom 5K downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-maven-plugin/1.1.3/plexus-maven-plugin-1.1.3.jar 14K downloaded [INFO] [INFO] Building Continuum Parent Project [INFO]task-segment: [clean:clean, install] [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-api/2.0/maven-plugin-api-2.0.pom 601b downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven/2.0/maven-2.0.pom 8K downloaded [INFO] [clean:clean] [INFO] artifact org.apache.maven.plugins:maven-site-plugin: checking for updates from central Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin/2.0-beta-4/maven-site-plugin-2.0-beta-4.pom 1K downloaded [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven.plugins:maven-site-plugin Reason: Error getting POM for 'org.apache.maven.plugins:maven-site-plugin' from the repository: Error transferring file org.apache.maven.plugins:maven-site-plugin:pom:2.0-beta-4 from the specified remote repositories: central (http://repo1.maven.org/maven2), snapshots (http://snapshots.maven.codehaus.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 7 seconds [INFO] Finished at: Thu Jan 26 20:48:13 EST 2006 [INFO] Final Memory: 2M/4M [INFO] + ret=0 + '[' 0 '!=' 0 ']'
