On 01/29/2010 04:12 PM, Ales Justin wrote:
> On 01/27/2010 04:50 PM, Ales Justin wrote:
>
>> Looking at the code, I don't see a reason why it cannot be at POST_PARSE.
>>
>> Another thing we can notice from this issue is that deployers ordering
>> has changed -- it seems we (already) no longer use relative order for
>> ordering.
>>
>>
> This is not true.
>
You don't know that. ;-)
As DependenciesTopologicalDeployerSorter is actually currently not used,
aha, ok
and I have no other explanation on why that Web deployer kicked in
before AOP deployer -- their relative order was an explicit order hack:
AOP = Web + 1.
It's because some input/output changed in some deployer and it caused
AOP deployer is not in the same "processing level" like Web deployer.
IOW both AOP and Web deployers are never relatively compared like before.
This could be either good or bad:
* good: exposed some issues; e.g. alt-dd order
* bad: it didn't expose some issues :-); e.g. we might have bad/random order
We can try switching to this sort alg,
doing it on a clean Hudson run would be best - to expose any changes.
Believe me, there are no changes in new sorting algorithm ;)
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Richard Opalka
ropalka(a)redhat.com
JBoss, by Red Hat
Office: +420 222 365 200
Mobile: +420 731 186 942