maven 3 - Why does jboss-as:deploy fail? -

i wanted deploy war file jboss 7.1.1 after compilation. fails following line in output (setting maven debug output -x , -e not create more verbose output).

my maven command use invoke is: clean install -pintegration jboss-as:deploy

[info] --- jboss-as-maven-plugin:7.1.1.final:deploy (default-cli) @ webapp --- aug 28, 2013 11:58:26 org.xnio.xnio <clinit> info: xnio version 3.0.3.ga aug 28, 2013 11:58:26 org.xnio.nio.nioxnio <clinit> info: xnio nio implementation version 3.0.3.ga aug 28, 2013 11:58:26 org.jboss.remoting3.endpointimpl <clinit> info: jboss remoting version 3.2.3.ga mojofailed org.jboss.as.plugins:jboss-as-maven-plugin:7.1.1.final(default-cli) projectfailed com.foo:webapp:0.0.1-snapshot [hudson] archiving c:\users\administrator\.hudson\jobs\ccms\workspace\pom.xml c:\users\administrator\.hudson\jobs\ccms\modules\com.foo$webapp\builds\2013-08-28_11-57-43\archive\com.foo\webapp\0.0.1-snapshot\pom.xml [hudson] archiving c:\users\administrator\.hudson\jobs\ccms\workspace\target\webapp.war c:\users\administrator\.hudson\jobs\ccms\modules\com.foo$webapp\builds\2013-08-28_11-57-43\archive\com.foo\webapp\0.0.1-snapshot\webapp.war sessionended [info] ------------------------------------------------------------------------ [info] build failure [info] ------------------------------------------------------------------------ [info] total time: 57.908s [info] finished at: wed aug 28 11:58:49 cest 2013 [info] final memory: 21m/250m [info] ------------------------------------------------------------------------ maven builder waiting mavenexecutionresult exceptions not empty org.apache.maven.lifecycle.lifecycleexecutionexception: failed execute goal org.jboss.as.plugins:jboss-as-maven-plugin:7.1.1.final:deploy (default-cli) on project webapp: deployment failed , rolled back.     @ org.apache.maven.lifecycle.internal.mojoexecutor.execute(mojoexecutor.java:217)     @ org.apache.maven.lifecycle.internal.mojoexecutor.execute(mojoexecutor.java:153)     @ org.apache.maven.lifecycle.internal.mojoexecutor.execute(mojoexecutor.java:145)     @ org.apache.maven.lifecycle.internal.lifecyclemodulebuilder.buildproject(lifecyclemodulebuilder.java:84)     @ org.apache.maven.lifecycle.internal.lifecyclemodulebuilder.buildproject(lifecyclemodulebuilder.java:59)     @ org.apache.maven.lifecycle.internal.lifecyclestarter.singlethreadedbuild(lifecyclestarter.java:183)     @ org.apache.maven.lifecycle.internal.lifecyclestarter.execute(lifecyclestarter.java:161)     @ org.apache.maven.defaultmaven.doexecute(defaultmaven.java:320)     @ org.apache.maven.defaultmaven.execute(defaultmaven.java:156)     @ org.jvnet.hudson.maven3.launcher.maven3launcher.main(maven3launcher.java:79)     @ sun.reflect.nativemethodaccessorimpl.invoke0(native method)     @ sun.reflect.nativemethodaccessorimpl.invoke(nativemethodaccessorimpl.java:57)     @ sun.reflect.delegatingmethodaccessorimpl.invoke(delegatingmethodaccessorimpl.java:43)     @ java.lang.reflect.method.invoke(method.java:601)     @ org.codehaus.plexus.classworlds.launcher.launcher.launchstandard(launcher.java:329)     @ org.codehaus.plexus.classworlds.launcher.launcher.launch(launcher.java:239)     @ org.jvnet.hudson.maven3.agent.maven3main.launch(maven3main.java:146)     @ hudson.maven.maven3builder.call(maven3builder.java:124)     @ hudson.maven.maven3builder.call(maven3builder.java:71)     @ hudson.remoting.userrequest.perform(userrequest.java:107)     @ hudson.remoting.userrequest.perform(userrequest.java:41)     @ hudson.remoting.request$2.run(request.java:276)     @ java.util.concurrent.executors$runnableadapter.call(executors.java:471)     @ java.util.concurrent.futuretask$sync.innerrun(futuretask.java:334)     @ java.util.concurrent.futuretask.run(futuretask.java:166)     @ java.util.concurrent.threadpoolexecutor.runworker(threadpoolexecutor.java:1110)     @ java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:603)     @ java.lang.thread.run(thread.java:722) caused by: org.apache.maven.plugin.mojoexecutionexception: deployment failed , rolled back.     @ org.jboss.as.plugin.deployment.standalone.standalonedeployment.execute(standalonedeployment.java:147)     @ org.jboss.as.plugin.deployment.abstractdeployment.execute(abstractdeployment.java:138)     @ org.apache.maven.plugin.defaultbuildpluginmanager.executemojo(defaultbuildpluginmanager.java:101)     @ org.apache.maven.lifecycle.internal.mojoexecutor.execute(mojoexecutor.java:209)     ... 27 more 

before that, added mgmtuser batch files jboss management realm. profile pom.xml configuration is:

<profile>             <!-- profile build in integration environment -->             <id>integration</id>             <build>                 <plugins>                     <!-- use plugin cleanly deploy application -->                     <plugin>                         <groupid>org.jboss.as.plugins</groupid>                         <artifactid>jboss-as-maven-plugin</artifactid>                         <version>7.1.1.final</version>                         <configuration>                             <hostname>localhost</hostname>                             <username>mgmtuser</username>                             <password>pwd</password>                             <force>true</force>                         </configuration>                     </plugin>                 </plugins>             </build>                         </profile> 

how retrieve detailed information error?

i looked server.log , spoted can't find persistence unit named foo in deployment.

altough worked in local development eclipse, failed on integration. reason: persistence.xml not included in classpath. in war file is: /web-inf/classes/meta-inf/persistence.xml

any place else results in error.