[
https://issues.apache.org/jira/browse/SLING-2643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco updated SLING-2643:
----------------------------
Attachment: SLING-2643-Skip-If-Writable.diff
I think the problem occurs when a user with administrative access runs this
test. The user will still have write privileges in Windows at least.
Attached is a patch which only executes the actual tests if the file is not
writable instead of failing if the file is writable.
> 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
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
