[
http://jira.codehaus.org/browse/MJBOSS-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130751#action_130751
]
Corridor Software Developer commented on MJBOSS-3:
--------------------------------------------------
Here is a quick explanation of this solution:
- JBoss remote deployment tells the server to download a deployable file from a
web server somewhere.
- If you want to deploy to that jboss server, you must put your app on a web
server somewhere and pass the url to the jboss server.
- If you are running an internal maven repository, it is a web server and can
be used in this process, but you must "deploy" to that
server before calling jboss:deploy.
So "repo.server.domain" is the fully qualified name to the web server where you
deployed your artifact.
mvn install - builds the artifact
mvn deploy - pushes the artifact to the repository in your
distributionManagement section of the pom.xml.
mvn jboss:deploy - w/ an http url, jboss tries to download the artifact from
the location where you pushed the artifact w/ "mvn deploy".
Regarding the error you got - If you look at the end of the url, you have this:
file://opt/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/11/target/hw-0.0.8-SNAPSHOT.war
for the url to the file, but the file isn't on the remote server in that
location. You have to use an http: reference, but the quickest way to have
an http: reference that points to the artifact is the "mvn deploy" it to a
repository.
Make sense? There are three machines involved in this solution. Your continuum
box, the remote box, and a web server where you are
pushing your build results.
> 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
> Issue Type: Improvement
> Environment: maven 2.0.1
> Reporter: Corridor Software Developer
> Assignee: Corridor Software Developer
> Fix For: 1.3.2
>
> 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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
