Let's wait for Richard confirmation (he just left), but from his commits
I think at least part of the problem was basically the same Carlo's
mentioned in "Re: [jboss-dev] Integration of naming deployers failed"
regarding modules names that need to be unique.
Brian Stansberry wrote:
Can you give an example? If there was a change in AS behavior that
forced you to change your deployments, I'd like to understand better
what the change was.
On 01/14/2010 05:40 AM, Richard Opalka wrote:
> I fixed the tests (to have unique archive names inside ear).
> Now all JBossWS tests pass against AS trunk, see 601 jobs at:
> IOW MC upgrade is ok for JBossWS, no problems since now ;)
> On 01/13/2010 03:45 PM, Brian Stansberry wrote:
>> If you have some spare cycles to try and analyze the cause of some of
>> those failures, it would be very helpful. If you find anything, the "MC
>> 2.2.x update" thread on this list is the best place to report them.
>> On 01/13/2010 08:30 AM, Richard Opalka wrote:
>>> it's nice it boots faster.
>>> However there are still some issues, e.g.
>>> that have to be addressed/identified :(