Plugins jboss-maven-plugin and cargo-maven2-plugin with JBoss 5

[Jean-Claude Rouvinez]

Hi,

I'm trying to deploy EAR artifacts to a remote JBoss server using cargo or the JBoss Maven Plugin but unfortunately none of this plugin works.

Who has managed it? How?
Any help is greatly appreciated.

Best Regards
Jean-Claude

Further Details:

Configuration
Maven version: 2.0.9
Java version: 1.6.0_07
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

jBoss 5.0.0.CR2
build: SVNTag=JBoss_5_0_0_CR2
date=200809171140

cargo-maven2-plugin
It is officially not possible to deploy an EAR file to a remote JBoss server using cargo according to Nabble - cargo eploy

jboss-maven-plugin
No success with the jboss-maven-plugin. Further information under Nabble - jboss eploy

[Martijn Verburg]

Hi Jean-Claude,

How have you configured the maven plugin in particular? I not4ieced from the Nabble post that the final 'slash' is a forward one as opposed to a backwards one:

c:\jp\projects\ipi-ear-example\ipi-ear-example-ear\target/ear-example.ear

[Jean-Claude Rouvinez]

Hi Martijn,

The configuration is very simple. I didn't configure anything but the final name of the artifact:

<finalName>ear-example</finalName>

Configuration of the plugins:

1). jboss-maven-plugin

  <build>
    <finalName>ear-example</finalName>
    <plugins>
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>jboss-maven-plugin</artifactId>
        <configuration>
          <jbossHome>${jboss.home}</jbossHome>
          <hostName>${jboss.hostName}</hostName>
        </configuration>
      </plugin>
    </plugins>
  </build> 

2). cargo-maven2-plugin

    <profile>
      <id>remote-jboss</id>
      <build>
        <plugins>
          <plugin>
            <groupId>org.codehaus.cargo</groupId>
            <artifactId>cargo-maven2-plugin</artifactId>
            <configuration>
              <container>
                <containerId>jboss5x</containerId>
                <type>remote</type>
              </container>
 
              <configuration>
                <type>runtime</type>
                <properties>
                  <cargo.hostname>${jboss.hostName}</cargo.hostname>
                </properties>
              </configuration>
 
            </configuration>
 
          </plugin>
        </plugins>
      </build>
    </profile> 

[Martijn Verburg]

Hmm, I was hoping to spot something there but as you say it's pretty simple. I'm afraid I can't help any further at this stage (we still manually deploy by unzipping several files including the EAR to the correct directories).

[Peter Johnson]

Deploying to a remote JBoss AS has always been problematic because JBoss AS provides no help in this area (though with the new admin console, Embedded Jopr, there might be a way once tools, such as cargo, catch up).

The only way to do a remote deployment is to copy the file(s) to the remote host using network file copy, or ftp, or some other similar mechanism (or writing a web app that does deployment - I've done this before but like I said Embedded Jopr can do this now).

And a hint on doing a remote deploy: copy the file(s) to a temporary location first, and after the copy is complete, move the file(s) to the deploy directory. (You want to avoid having the hot deployer attempt to deploy your app when it is only partially copied, that can sometimes give bizarre error messages.)

Personally, I don't deploy often enough to worry about automation so I do it by hand. If I were to automate it, I would do it via an Ant script that did a network copy followed by a move. But then my PC and the server are both behind the firewall and I have the luxury of connecting to the server's disk.

[Jean-Claude Rouvinez]

Hi Peter,

Thank you for your answer. It makes me feel more confident using this solution:

1).
I define an ant target (deploy_ear_file) in build.xml to deploy the artifact. This target uses scp to copy the artifact remotely and sshexec to move it to the deploy directory.

2).
I call this ant target from Maven

3).
I deploy the artifact to the remote host with the command:
mvn clean deploy


Appendix:
The section of the file pom.xml

          <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-antrun-plugin</artifactId>
 
            <executions>
              <execution>
                <phase>deploy</phase>
 
                <configuration>
                  <tasks>
                    <property name="file" value="${project.build.directory}/${project.build.finalName}.ear" />
                    <property name="todir" value="user :-P	 assword@${jboss.hostName}:." />
 
                    <ant antfile="build.xml" inheritRefs="true" inheritAll="true">
                      <target name="deploy_ear_file" />
                    </ant>
                  </tasks>
                </configuration>
                <goals>
                  <goal>run</goal>
                </goals>
              </execution>
            </executions>
 
            <dependencies>
              <dependency>
                <groupId>org.apache.ant</groupId>
                <artifactId>ant-jsch</artifactId>
                <version>1.7.1</version>
              </dependency>
 
              <dependency>
                <groupId>com.jcraft</groupId>
                <artifactId>jsch</artifactId>
                <version>0.1.38</version>
              </dependency>
            </dependencies>
 
          </plugin>