Cargo 插件在 Glassfish 上部署时抛出 CargoException - 部署失败：null

Question

我正在尝试使用 Cargo Maven 插件在远程 Glassfish 服务器（版本 3.1.1（版本 12））上部署 Web 应用程序。 Glassfish 服务器以及位于不同 Linux 服务器 (Ubuntu) 上的 Java 代码。我已经在 pom 文件中配置了所有必需的属性，并在 Windows 计算机上测试了部署。有用。但它在 Linux Ubuntu 上失败了，有一个有趣的例外：

27-Jun-2012 14:36:05    [ERROR] Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.2.1:deploy (default-cli) on project my-web-project-app: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.2.1:deploy failed: Deployment has failed: null -> [Help 1]
27-Jun-2012 14:36:05    org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.cargo:cargo-maven2-plugin:1.2.1:deploy (default-cli) on project mca-staff-app: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.2.1:deploy failed: Deployment has failed: null
27-Jun-2012 14:36:05            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
27-Jun-2012 14:36:05            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
27-Jun-2012 14:36:05            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
27-Jun-2012 14:36:05            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
27-Jun-2012 14:36:05            at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
27-Jun-2012 14:36:05            at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
27-Jun-2012 14:36:05            at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
27-Jun-2012 14:36:05            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
27-Jun-2012 14:36:05            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
27-Jun-2012 14:36:05            at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
27-Jun-2012 14:36:05            at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
27-Jun-2012 14:36:05            at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
27-Jun-2012 14:36:05            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
27-Jun-2012 14:36:05            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
27-Jun-2012 14:36:05            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
27-Jun-2012 14:36:05            at java.lang.reflect.Method.invoke(Method.java:597)
27-Jun-2012 14:36:05            at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
27-Jun-2012 14:36:05            at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
27-Jun-2012 14:36:05            at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
27-Jun-2012 14:36:05            at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
27-Jun-2012 14:36:05    Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-cli of goal org.codehaus.cargo:cargo-maven2-plugin:1.2.1:deploy failed: Deployment has failed: null
27-Jun-2012 14:36:05            at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
27-Jun-2012 14:36:05            at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
27-Jun-2012 14:36:05            ... 19 more
27-Jun-2012 14:36:05    Caused by: org.codehaus.cargo.util.CargoException: Deployment has failed: null
27-Jun-2012 14:36:05            at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.waitForProgressObject(AbstractJsr88Deployer.java:285)
27-Jun-2012 14:36:05            at org.codehaus.cargo.container.spi.deployer.AbstractJsr88Deployer.deploy(AbstractJsr88Deployer.java:126)
27-Jun-2012 14:36:05            at org.codehaus.cargo.maven2.DeployerDeployMojo.performDeployerActionOnSingleDeployable(DeployerDeployMojo.java:56)
27-Jun-2012 14:36:05            at org.codehaus.cargo.maven2.AbstractDeployerMojo.performDeployerActionOnAllDeployables(AbstractDeployerMojo.java:178)
27-Jun-2012 14:36:05            at org.codehaus.cargo.maven2.AbstractDeployerMojo.doExecute(AbstractDeployerMojo.java:98)
27-Jun-2012 14:36:05            at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:311)
27-Jun-2012 14:36:05            at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
27-Jun-2012 14:36:05            ... 20 more

有人在 Linux 上使用 maven Cargo 插件进行远程应用程序部署吗？或者也许有人知道这里有什么问题？

Answer 1

服务器上执行的完整路径可能存在故障。据我所知，应用程序通常构建在服务器上，因此不会发生这种情况。 Windows 也使用反斜杠，Linux 不接受路径中的反斜杠。如果编译是在 Win 上，请通过 Linux 盒子再次进行。

Answer 2

默认密码是adminadmin。如果您没有密码，则使用 Cargo 作为密码时使用“”，如果密码字段为空，将会导致错误。

使用以下代码

<plugin>
   <groupId>org.codehaus.cargo</groupId>
   <artifactId>cargo-maven2-plugin</artifactId>
   <version>1.7.16</version>
   <executions>
      ...
   </executions>
</plugin>

<execution>
   <id>deploy</id>
   <phase>pre-integration-test</phase>
   <goals>
      <goal>start</goal <goal>redeploy</goal>
   </goals>
</execution>
<execution>
   <id>undeploy</id>
   <phase>post-integration-test</phase>
   <goals>
      <goal>undeploy</goal>
      <goal>stop</goal>
   </goals>
</execution>