I've seen http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-534, I'm not sure if this is the same problem.
I'm using JBoss-3.2.1-Tomcat-4.1.24 jboss:deploy-warfile invokes war:war. I can run war:war, do some postGoal to copy it into my JBoss-Tomcat deploy directory, and successfully have it deploy. No bugs there. I run my project with jboss:deploy-warfile. Even though it fails, the .war produced still works just fine if I copy it over. I go into the jmx-console to the jboss.deployment MBean Inspector, flavor=URL,type=DeploymentScanner scroll down to the addURL() MBean operation, type in the file:///projects/myproject.war in the text field, press invoke, and all is well again. aha! http://maven.apache.org/reference/plugins/jboss/properties.html says that I can set the maven.jboss.jmx.url.deploy in the hopes of fixing the url used, go arg0 as in the jira issue, I try it in both project.properties and in build.properties ..... Several wrong things happen: maven doesn't see it. It still uses the wrong url. it uses arg, instead of arg0. if uses a relative url: file:target/myproject.war instead of a full file path url. It uses "undeploy" instead of "deploy" in the query string and fails on that. other problems, anybody else successfully get past this problem? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
