maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (MPJBOSS-7) jboss:deploy-exploded-warfile no worky
Date Thu, 18 Dec 2003 16:21:54 GMT
The following comment has been added to this issue:

     Author: Jim Crossley
    Created: Thu, 18 Dec 2003 10:21 AM
After looking at this a bit more closely, I now realize it's not a jboss plugin issue but
a war plugin issue.  I *think* it's just a matter of making this the default setting in the
war plugin:

maven.war.webapp.dir = ${}/exploded/${pom.artifactId}.war/

I don't believe it breaks any existing functionality and it makes all the JBoss goals work
out of the box.
View the issue:

Here is an overview of the issue:
        Key: MPJBOSS-7
    Summary: jboss:deploy-exploded-warfile no worky
       Type: Bug

     Status: Unassigned
   Priority: Minor

 Original Estimate: 1 day
 Time Spent: Unknown
  Remaining: 1 day

    Project: maven-jboss-plugin

   Reporter: Jim Crossley

    Created: Thu, 11 Dec 2003 7:50 AM
    Updated: Thu, 18 Dec 2003 10:21 AM
Environment: Any

It is often convenient to deploy an exploded warfile to jboss so that jsp changes don't require
a redeploy.

JBoss requires that the exploded directory name have a J2EE suffix, e.g. .war, .ear, etc.
 Because the exploded directory and the war file are both created in the target directory,
they cannot have the same name.

I propose that the exploded warfile go in target/exploded/${id}.war/ so that both it and target/${id}.war
(the actual war) can peacefully coexist.  That way, both jboss:deploy-warfile and jboss:deploy-exploded-warfile
will work correctly out of the box.

I'll try to submit a patch soon (s/b trivial).

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message