2013-04-07 188 views
10

我有点新Maven和我假设这是一个Maven的事情,不是与我的外壳,但是当我与-e开关运行,试图找出一个错误,我得到的东西不完全是这样:mvn -e完整的堆栈跟踪?

[INFO] ------------------------------------------------------------------------ 
[ERROR] BUILD ERROR 
[INFO] ------------------------------------------------------------------------ 
[INFO] Deployment failed and was rolled back. 
[INFO] ------------------------------------------------------------------------ 
[INFO] Trace 
org.apache.maven.lifecycle.LifecycleExecutionException: Deployment failed and was rolled back. 
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:348) 
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:57) 
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
at java.lang.reflect.Method.invoke(Method.java:601) 
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.jboss.as.plugin.common.DeploymentExecutionException: Deployment failed and was rolled back. 
at org.jboss.as.plugin.deployment.standalone.StandaloneDeployment.execute(StandaloneDeployment.java:140) 
at org.jboss.as.plugin.deployment.AbstractDeployment.executeDeployment(AbstractDeployment.java:119) 
at org.jboss.as.plugin.deployment.AbstractDeployment.doExecute(AbstractDeployment.java:141) 
at org.jboss.as.plugin.deployment.AbstractAppDeployment.doExecute(AbstractAppDeployment.java:70) 
at org.jboss.as.plugin.deployment.AbstractDeployment.execute(AbstractDeployment.java:111) 
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) 
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) 
... 17 more 
[INFO] ------------------------------------------------------------------------ 

我怎样才能看到“... 17更多”的东西?我相信这会帮助我确定哪个maven任务失败了?感谢您提供任何帮助或文档链接!

P.S.如果你是好奇,我就不再帮我搞清楚实际的问题,我只是跑“MVN清洁包的jboss-如:部署”部署,我可以提供另一个问题具体到如果我不将问题的详细信息我自己弄明白了。

+0

“更多的东西”应该已经存在于其他地方的堆栈跟踪 - http://stackoverflow.com/questions/1167888/howto-increase-lines-of-java-stack-trace-dump,但我不是100%肯定。 – 2013-04-07 17:38:05

+0

@PaulGrime看起来是这样的,谢谢你的链接! – mwillson 2013-04-07 17:49:54

+0

你可以尝试使用'-e -X' Maven开关来获取完整的日志。 – 2013-04-07 17:51:11

回答

1

这不是严格意义上的答案,但它可能会帮助你的调查。

StandaloneDeployment (line 140)的源代码(警告,这可能不是你正在使用的版本)表示DeploymentExecutionException被抛出的地方:传递给该DeploymentExecutionException

case ROLLED_BACK: 
    throw new DeploymentExecutionException("Deployment failed and was rolled back.", actionResult.getDeploymentException()); 

和根异常(actionResult.getDeploymentException()) 。

我还以为你会得到看到Maven的堆栈跟踪这根异常,但似乎不是在你的情况。

你总是可以尝试debugging the plugin itself,并把一个断点上面显示的线。

+0

再次,谢谢。这是很好的信息,即使我没有使用Eclipse。如果我在太久之后仍然无法弄清楚,我会在另一个问题中发布更详细的服务器信息。 – mwillson 2013-04-07 17:58:54

+0

调试本身不依赖于Eclipse。如果您有另一个IDE,它将具有类似的功能,以将其自身附加到调试Java过程。 – 2013-04-07 18:01:49

相关问题