On 21/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
On 21/06/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> IT doesn't quite sound right - I would have expected it still select
> nearest and apply the alternate scope from my recollection. But IIRC
> behaviour was changed ~2.0.4 in relation to scopes, for some
> particular reason and perhaps this is it: Carlos?
That's what I would have thought too. Anyone have any insight into this?
Ping..?
This is appearing to prevent a solution to the artifact filtering
problem detailed in "Artifact filtering in DefaultArtifactCollector",
since filtering listener events causes only DACT.testScopeUpdate to
fail.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
