[
https://issues.apache.org/jira/browse/SLING-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-2643.
----------------------------------
> org.apache.sling.commons.log Test Failure
> -----------------------------------------
>
> Key: SLING-2643
> URL: https://issues.apache.org/jira/browse/SLING-2643
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Log 3.0.0
> Environment: Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)
> Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
> Windows 7
> Reporter: Dan Klco
> Assignee: Ian Boston
> Fix For: Commons Log 3.0.2
>
> Attachments: maven-logs.txt,
> org.apache.sling.commons.log.internal.slf4j.SlingLogWriterTest.txt,
> SLING-2643-Skip-If-Writable.diff,
> TEST-org.apache.sling.commons.log.internal.slf4j.SlingLogWriterTest.xml
>
>
> When attempting to compile Sling from the source based on the README in the
> root of the project, the tests for the project org.apache.sling.commons.log
> fail. I think the problem here is that it's not making the protectedParent
> directory locked when it should. In this case the test should just abort
> instead of failing.
> Not sure if this is an JVM/OS issue, the code doesn't seem to be checking the
> response from the attempt to deny write access to the directory.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)