I just got an it failure email, apparently it has been in the tank for some time. What changed since the person who upgraded scm tested that change?
On February 21, 2014 2:44:10 PM EST, Robert Scholte <rfscho...@apache.org> wrote: >Ok, I found the cause and you're not gonna to like it. >put scmVersion 1.9 back to 1.7 and see the magic. >Seems like I missed something here, but why? > >Robert > >Op Fri, 21 Feb 2014 20:24:39 +0100 schreef Dennis Lundberg ><denn...@apache.org>: > >> I see those errors as well. >> >> >> Also I have found that I cannot build maven-release using Java 5. >Have >> tried on Win 7 and Ubuntu - same problem. After downgrading to >> maven-compiler-plugin:2.5.1 I was able to get the real error message >> (3.0 seems to swallow it): >> >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to >> execute goal >org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile >> (default-compile) on project maven-release-manager: Compilation >> failure >> Failure executing javac, but could not parse the error: >> An exception has occurred in the compiler (1.5.0_22). Please file a >> bug at the Java Developer Connection >> (http://java.sun.com/webapps/bugreport) after checking the Bug >Parade >> for duplicates. Include your program and the following diagnostic in >> your report. Thank you. >> com.sun.tools.javac.code.Symbol$CompletionFailure: file >> org\codehaus\plexus\component\annotations\Component.class not found >> >> I doubt that Sun (Oracle) will accept bug reports for Java 5 >though... >> >> Any idea on what could be the cause? >> >> >> On Fri, Feb 21, 2014 at 4:56 PM, Benson Margulies >> <bimargul...@gmail.com> wrote: >>> I checked out the trunk and tried a simple 'mvn test', and I'm >>> drowning in test failures. Anyone have a hint? >>> >>> >------------------------------------------------------------------------------- >>> Test set: org.apache.maven.shared.release.DefaultReleaseManagerTest >>> >------------------------------------------------------------------------------- >>> Tests run: 30, Failures: 0, Errors: 30, Skipped: 0, Time elapsed: >>> 0.875 sec <<< FAILURE! - in >>> org.apache.maven.shared.release.DefaultReleaseManagerTest >>> >testPrepareNoCompletedPhase(org.apache.maven.shared.release.DefaultReleaseManagerTest) >>> Time elapsed: 0.062 sec <<< ERROR! >>> org.codehaus.plexus.PlexusContainerException: Error starting >container >>> at >>> >org.codehaus.plexus.component.repository.DefaultComponentRepository.addComponentDescriptor(DefaultComponentRepository.java:184) >>> at >>> >org.codehaus.plexus.DefaultPlexusContainer.addComponentDescriptor(DefaultPlexusContainer.java:515) >>> at >>> >org.codehaus.plexus.DefaultPlexusContainer.discoverComponents(DefaultPlexusContainer.java:738) >>> at >>> >org.codehaus.plexus.DefaultPlexusContainer.start(DefaultPlexusContainer.java:779) >>> at >>> org.codehaus.plexus.PlexusTestCase.setUp(PlexusTestCase.java:121) >>> at >>> >org.apache.maven.shared.release.DefaultReleaseManagerTest.setUp(DefaultReleaseManagerTest.java:75) >>> >>> >--------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >> >> > >--------------------------------------------------------------------- >To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >For additional commands, e-mail: dev-h...@maven.apache.org -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
