You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2009/03/31 14:19:51 UTC

[jira] Closed: (SLING-903) Access-control related integration tests run "too early" and fail

     [ https://issues.apache.org/jira/browse/SLING-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz closed SLING-903.
-------------------------------------

    Resolution: Invalid

I was wrong, the problem was caused by a stale "sling" folder with old repository data, and "mvn clean" doesn't delete all such sling test folders. Will bring this up on the dev list.

> Access-control related integration tests run "too early" and fail
> -----------------------------------------------------------------
>
>                 Key: SLING-903
>                 URL: https://issues.apache.org/jira/browse/SLING-903
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>
> Some integration tests to fail on my macosx JDK 1.5 system: org.apache.sling.launchpad.webapp.integrationtest.accessManager.RemoveAcesTest, UpdateGroupTest, ModifyAceTest, etc.
> The tests pass when run against a separate Sling instance that's been started from some time, but when run as part of a full build they fail with the NPE of SLING-868
> I assume that's because the tests run "too early", before the required authenticator is started. Implementing a better readyness detection test (SLING-490) should help.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.