On 9 April 2010 13:58, Lin Sun <[email protected]> wrote: > Hmm this worked on my machine to skip the itest when doing mvn clean > install in blueprint dir.
cool, if I can get configured the same way as you then that would be perfect. > Anyway, I saw you've removed the > blueprint-itests off the blueprint pom > while this is true, it has only got me a little further. After building blueprint-api it goes straight on to blueprint-core which depends on blueprint-api but complains it can't find blueprint-api in the repo. Sure enough it's not there. Looks like an install hasn't been done of the blueprint-api..... > Lin > > On Fri, Apr 9, 2010 at 5:59 AM, Jeremy Hughes <[email protected]> wrote: > > On 9 April 2010 03:14, Lin Sun <[email protected]> wrote: > > > >> Hi Jeremy > >> > >> I think -Dmaven.test.skip=true would skip the unit test for you, but > >> not the itest. You can use -Dmaven.itest.skip=true to skip the itest. > >> > > > > Sadly this didn't help. I've been looking for info on that flag. Is it > used > > by the Geronimo maven.itest.plugin ? I don't believe we use that one - it > > certainly isn't in my local repo. > > > > > >> HTH > >> > >> Lin > >> > >> On Thu, Apr 8, 2010 at 10:01 PM, Jeremy Hughes <[email protected]> > wrote: > >> > I've hit a road block with the blueprint module. While executing mvn > >> > release:prepare when the blueprint-itests module is reached and > executed > >> I > >> > get an exception: > >> > > >> > [INFO] [INFO] There are test failures. > >> > [INFO] > >> > [INFO] Please refer to > >> > > >> > C:\cygwin\home\hughesj\oss\aries\trunk-again\blueprint\blueprint-itests\target\surefire-reports > >> > for the individual test results > >> > > >> > This happens before the surefire-reports directory is even created. > Even > >> > running with -Dmaven.test.skip=true surefire still runs. I tried > changing > >> > the configuration of surefire in the pom so that it doesn't fork a > >> process > >> > for each test. The only way I could get it to succeed is by commenting > >> out > >> > the <module>blueprint-itests</module> line in the blueprint/pom.xml > ... > >> is > >> > this acceptable though for a release? I would have to check in that > >> change > >> > in order to release like that. Right now it's my only option. > >> > > >> > The exact error (using the -X flag for full verbosity) is below: > >> > > >> > [INFO] [INFO] Surefire report directory: > >> > > >> > C:\cygwin\home\hughesj\oss\aries\trunk-again\blueprint\blueprint-itests\target\surefire-reports > >> > [INFO] Forking command line: cmd.exe /X /C > "C:\inst\j2se160\jre\bin\java > >> > -Dorg.ops4j.pax.url.mvn.localRepository=C:\Documents and > >> > Settings\Administrat > >> > or\.m2\repository -jar > >> > C:\cygwin\tmp\mytmp\surefirebooter7571094216390397671.jar > >> > C:\cygwin\tmp\mytmp\surefire3450019939594901752tmp C:\cygwin\tmp\mytm > >> > p\surefire7725688157744438252tmp" > >> > [INFO] [INFO] > >> > > ------------------------------------------------------------------------ > >> > [INFO] [ERROR] BUILD FAILURE > >> > [INFO] [INFO] > >> > > ------------------------------------------------------------------------ > >> > [INFO] [INFO] There are test failures. > >> > [INFO] > >> > [INFO] Please refer to > >> > > >> > C:\cygwin\home\hughesj\oss\aries\trunk-again\blueprint\blueprint-itests\target\surefire-reports > >> > for the individual test results > >> > . > >> > [INFO] [INFO] > >> > > ------------------------------------------------------------------------ > >> > [INFO] [DEBUG] Trace > >> > [INFO] org.apache.maven.BuildFailureException: There are test > failures. > >> > [INFO] > >> > [INFO] Please refer to > >> > > >> > C:\cygwin\home\hughesj\oss\aries\trunk-again\blueprint\blueprint-itests\target\surefire-reports > >> > for the individual test results > >> > . > >> > [INFO] at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715) > >> > [INFO] at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > >> > [INFO] at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > >> > [INFO] at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > >> > [INFO] at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > >> > [INFO] at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > >> > [INFO] at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > >> > [INFO] at > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > >> > [INFO] at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > >> > [INFO] at > >> > > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > >> > [INFO] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > >> > [INFO] at > >> > > >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) > >> > [INFO] at > >> > > >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > >> > [INFO] at java.lang.reflect.Method.invoke(Method.java:600) > >> > [INFO] at > >> > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > >> > [INFO] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > >> > [INFO] at > >> > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > >> > [INFO] at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > >> > [INFO] Caused by: org.apache.maven.plugin.MojoFailureException: There > are > >> > test failures. > >> > [INFO] > >> > [INFO] Please refer to > >> > > >> > C:\cygwin\home\hughesj\oss\aries\trunk-again\blueprint\blueprint-itests\target\surefire-reports > >> > for the individual test results > >> > . > >> > [INFO] at > >> > > >> > org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:575) > >> > [INFO] at > >> > > >> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > >> > [INFO] at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > >> > [INFO] ... 17 more > >> > [INFO] [INFO] > >> > > ------------------------------------------------------------------------ > >> > [INFO] [INFO] Total time: 1 minute 24 seconds > >> > [INFO] [INFO] Finished at: Fri Apr 09 02:55:28 BST 2010 > >> > [INFO] [INFO] Final Memory: 99M/156M > >> > [INFO] [INFO] > >> > > ------------------------------------------------------------------------ > >> > [INFO] > >> > > ------------------------------------------------------------------------ > >> > [ERROR] BUILD ERROR > >> > [INFO] > >> > > ------------------------------------------------------------------------ > >> > [INFO] Maven execution failed, exit code: '1' > >> > > >> > [INFO] > >> > > ------------------------------------------------------------------------ > >> > [DEBUG] Trace > >> > org.apache.maven.lifecycle.LifecycleExecutionException: Maven > execution > >> > failed, exit code: '1' > >> > at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) > >> > at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) > >> > at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) > >> > at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > >> > at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:284) > >> > at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > >> > at > org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > >> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > >> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > >> > at > >> > > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > >> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > >> > at > >> > > >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) > >> > at > >> > > >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > >> > at java.lang.reflect.Method.invoke(Method.java:600) > >> > at > >> > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > >> > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > >> > at > >> > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > >> > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > >> > Caused by: org.apache.maven.plugin.MojoExecutionException: Maven > >> execution > >> > failed, exit code: '1' > >> > at > >> > > >> > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:186) > >> > at > >> > > >> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > >> > at > >> > > >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > >> > ... 17 more > >> > Caused by: org.apache.maven.shared.release.ReleaseExecutionException: > >> Maven > >> > execution failed, exit code: '1' > >> > at > >> > > >> > org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:89) > >> > at > >> > > >> > org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.execute(RunPrepareGoalsPhase.java:42) > >> > at > >> > > >> > org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.simulate(RunPrepareGoalsPhase.java:54) > >> > at > >> > > >> > org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:192) > >> > at > >> > > >> > org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:133) > >> > at > >> > > >> > org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:96) > >> > at > >> > > >> > org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:182) > >> > ... 19 more > >> > Caused by: > org.apache.maven.shared.release.exec.MavenExecutorException: > >> > Maven execution failed, exit code: '1' > >> > at > >> > > >> > org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecutor.java:395) > >> > at > >> > > >> > org.apache.maven.shared.release.exec.InvokerMavenExecutor.executeGoals(InvokerMavenExecutor.java:413) > >> > at > >> > > >> > org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(AbstractRunGoalsPhase.java:81) > >> > ... 25 more > >> > [INFO] > >> > > ------------------------------------------------------------------------ > >> > [INFO] Total time: 1 minute 37 seconds > >> > [INFO] Finished at: Fri Apr 09 02:55:29 BST 2010 > >> > [INFO] Final Memory: 25M/94M > >> > [INFO] > >> > > ------------------------------------------------------------------------ > >> > > >> > On 9 April 2010 01:44, Jeremy Hughes <[email protected]> wrote: > >> >> I've started to upload the release candidate artifacts to the staging > >> >> repo, this may take some time. I'd appreciate a lull in commits to > the > >> >> modules below until I've sent out the vote email and preferably the > >> >> vote has closed. If this is a problem we should discuss. > >> >> > >> >> Thanks, > >> >> Jeremy > >> >> > >> >> On 8 April 2010 21:54, Jeremy Hughes <[email protected]> wrote: > >> >>> Just lately I've been carrying out a final push to get release > >> >>> candidates for the Aries top level modules onto the staging repo. If > >> >>> the maven release plugin is kind to me I hope to get that out in > >> >>> what's left of today or early tomorrow. The modules with RCs will > be: > >> >>> > >> >>> parent > >> >>> eba-maven-plugin > >> >>> testsupport > >> >>> util > >> >>> blueprint > >> >>> jndi > >> >>> transaction > >> >>> web > >> >>> application > >> >>> jmx > >> >>> jpa > >> >>> samples (I'll be moving the transaction sample out into a > >> >>> samples-sandbox top level module as I don't think this works right > >> >>> now) > >> >>> > >> >>> Cheers, > >> >>> Jeremy > >> >>> > >> >> > >> > > >> > > >
