> 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.
They used to be in the same. ;-)
Then we did an easy fix == move it to different stage,
as there was really no reason why the need to be in the same,
or why AOP cannot be in the next one.