[ http://jira.codehaus.org/browse/MJBOSS-3?page=all ]

Corridor Software Developer updated MJBOSS-3:
---------------------------------------------

    Attachment: jboss-remote.patch

> JBoss: Slight modification supports deployment to remote jboss instance.
> ------------------------------------------------------------------------
>
>          Key: MJBOSS-3
>          URL: http://jira.codehaus.org/browse/MJBOSS-3
>      Project: Maven 2.x JBoss Plugin
>         Type: Improvement

>  Environment: maven 2.0.1
>     Reporter: Corridor Software Developer
>     Assignee: Corridor Software Developer
>  Attachments: jboss-remote.patch
>
>
> The jboss plugin uses the jmx deployment interface to perform deployments. 
> Currently only local deployments can be done and the code is biased towards 
> that end.
> With a slight modification and the help of the mvn deploy goal, we can 
> support remote deployment as well. The use case would be "developer deploys a 
> j2ee artifact to a remote development jboss instance". The command would be:
> mvn deploy jboss:deploy
> The initial deploy is required because remote deployment requires that the 
> server can reach the artifact via a url, and a file:// url isn't sufficient.
> The code change to the deployer is a simple check for an existing protocol in 
> the url given from the configuration. If it's not present, prepend "file://". 
> This avoids damaging the existing local deployment support.
> The configuration would appear as such:
>             <plugin>
>                 <groupId>org.codehaus.mojo</groupId>
>                 <artifactId>jboss-maven-plugin</artifactId>
>                 <configuration>
>                     <server>server.id</server>
>                     <hostName>server.domain<hostName>
>                     
> <fileName>http://repo.server.domain/path-to-artifact/filename-ear-version.ear</fileName>
>                     <port>port</port>
>                 </configuration>
>             </plugin>
> I'll attach a patch and commit the change soon.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to