Re: [jboss-dev] 2 weeks to AS5 code freeze
It was just that the HDScanner bean was being deployed differently based
on the profile service implementation. Now the HDScanner bean is
deployed as deploy/profileservice-hdscanner-jboss-beans.xml in every
profile independent of which profile service implementation is used.
Scott Stark wrote:
The immediate problem that shows up is that hot deployment is not
working, so the tests don't run because the minimal configuration
requires this in order to shutdown. Its failure to shutdown causes the
testsuite run to fail because the naming ports are still active when
the all configuration is started.
https://jira.jboss.org/jira/browse/JBAS-6190