Why don't you create a Jira item and attach the entire trace as an attachment. Like this "mvn clean install > mytrace".
We can then get a better idea of what is going on. D. On Tue, Nov 3, 2009 at 3:39 PM, Xuefeng Wu <[email protected]> wrote: > Thank you for your response. > > @D > I checked out new from SVN but failed too. > > @David > I run 'mvn -U clean install jetty:run' and failed too , get the same error: > command line returned non-zero value:1 > I didn't rename .m2 folder and my other maven projects are working. > > > > On Tue, Nov 3, 2009 at 9:59 PM, David Pollak > <[email protected]>wrote: > >> Did you do a successful "mvn -U clean install jetty:run" before trying to >> apply the "-o" switch? Did you do an rm -rf ~/.m2 before starting the >> process? >> >> On Tue, Nov 3, 2009 at 6:52 AM, Xuefeng Wu <[email protected]> wrote: >> >> > I run mvn clean install -e >> > get: >> > >> > [WARNING] 204 errors found >> > [INFO] >> > ------------------------------------------------------------------------ >> > [ERROR] BUILD FAILURE >> > [INFO] >> > ------------------------------------------------------------------------ >> > [INFO] command line returned non-zero value:1 >> > [INFO] >> > ------------------------------------------------------------------------ >> > [INFO] Trace >> > org.apache.maven.BuildFailureException: command line returned non-zero >> > value:1 >> > at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa >> > ultLifecycleExecutor.java:715) >> > at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi >> > fecycle(DefaultLifecycleExecutor.java:556) >> > at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau >> > ltLifecycleExecutor.java:535) >> > at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan >> > dleFailures(DefaultLifecycleExecutor.java:387) >> > at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen >> > ts(DefaultLifecycleExecutor.java:348) >> > at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi >> > fecycleExecutor.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:6 >> > 0) >> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> > at >> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. >> > java:39) >> > at >> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces >> > sorImpl.java:25) >> > at java.lang.reflect.Method.invoke(Method.java:597) >> > 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.MojoFailureException: command line >> > returned n >> > on-zero value:1 >> > at org.scala_tools.maven.JavaCommand.run(JavaCommand.java:196) >> > at >> > org.scala_tools.maven.ScalaCompilerSupport.compile(ScalaCompilerSuppo >> > rt.java:124) >> > at >> > org.scala_tools.maven.ScalaCompilerSupport.doExecute(ScalaCompilerSup >> > port.java:54) >> > at >> > org.scala_tools.maven.ScalaMojoSupport.execute(ScalaMojoSupport.java: >> > 208) >> > at >> > org.scala_tools.maven.ScalaCompilerSupport.execute(ScalaCompilerSuppo >> > rt.java:29) >> > at >> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi >> > nManager.java:490) >> > at >> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa >> > ultLifecycleExecutor.java:694) >> > ... 17 more >> > [INFO] >> > ------------------------------------------------------------------------ >> > [INFO] Total time: 23 seconds >> > >> > >> > >> > On Tue, Nov 3, 2009 at 6:16 PM, Vassil Dichev <[email protected]> wrote: >> > >> > > > Yes >> > > > I'm on line and run mvn jetty:run and get the same error: >> > > > >> > > > What's the mean " command line returned non-zero value:1" in maven? >> > > >> > > Depends on these "204 errors found". Why don't you do as maven >> > > suggests and "run Maven with the -e switch"? >> > > >> > >> > >> > >> > -- >> > Scala中文社区: http://groups.google.com/group/scalacn >> > >> >> >> >> -- >> Lift, the simply functional web framework http://liftweb.net >> Beginning Scala http://www.apress.com/book/view/1430219890 >> Follow me: http://twitter.com/dpp >> Surf the harmonics >> > > > > -- > Scala中文社区: http://groups.google.com/group/scalacn >
