The following comment has been added to this issue:
Author: Archimedes Trajano
Created: Thu, 27 Nov 2003 1:48 PM
Body:
Actually one thing we should do, but need to create another defect for this is to make
jboss:start terminate but leave the app server running. Not really sure how to do
that.
Forking out with "start" though it may work will not solve the problem because we have
to make it wait till the server finishes loading before we can deploy our code.
That way we can do
maven jboss:start jboss:deploy-ear test jboss:stop
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPJBOSS-3
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPJBOSS-3
Summary: jboss 3.2 JXM deploy/undeploy URL is slightly different from what's in
jboss plugin project.properties
Type: Bug
Status: Unassigned
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-jboss-plugin
Fix Fors:
1.4
Versions:
1.3
Assignee:
Reporter: Dima Berastau
Created: Tue, 1 Jul 2003 3:53 AM
Updated: Thu, 27 Nov 2003 1:48 PM
Description:
default maven.jboss.jmx.url.deploy and maven.jboss.jmx.url.undeploy seem to be missing
0 at the end (should read 'arg0=' rather than 'arg=', tested in jboss 3.2).
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
