start-and-wait mojo should disable automatic discovery
------------------------------------------------------
Key: MJBOSS-60
URL: http://jira.codehaus.org/browse/MJBOSS-60
Project: Maven 2.x JBoss Plugin
Issue Type: Bug
Affects Versions: 1.5.0
Reporter: Ivan S. Dubrov
Attachments: discovery-disable.patch
When start-and-wait mojo checks if server is started by doing JNDI lookups, it
should disable automatic discovery of JNDI. Otherwise, JBoss JNDI client will
try to find JNDI via multicast using the default address of 230.0.0.4, so it is
possible that it will find JBoss running somewhere else and query its status.
As a result, it will think that local JBoss is already started, which is wrong.
In our case, build script tries to deploy the application to run the functional
tests and fails.
http://community.jboss.org/wiki/NamingContextFactory
See the patch attached that disabled automatic discovery.
--
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
