Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Case-insensitive check for resource.exists() only when resource is case-sensitive

Description

Please review pull request https://github.com/lucee/Lucee/pull/3 for inclusion into the codebase.

While working on my Azure resourceProvider, I noticed an extra file listing is done when calling fileExists() on a non-existing file. This is done based on the Operating system being unix/linux, where it should actually check if the resourceProvider itself is case-sensitive.

As a side note: my current resource has thousands of files stored directly in the root directory. This case-insensitive check (dir listing) takes quite a while to load; are you sure this is the right way to do it?

Activity

Show:

Paul Klinkenberg 19 November 2015 at 09:14

This has meanwhile be pulled in. , you can close this issue now. (where did the regular workflow go...)

Sean Corfield 4 November 2015 at 21:59

OK, I didn't check the actual build failure. is the build known to be broken right now?

Paul Klinkenberg 4 November 2015 at 21:47

Well, the error which occured is due to:
{{Failed to transfer file: https://oss.sonatype.org/content/repositories/snapshots/org/lucee/lucee/5.0.0.98-SNAPSHOT/lucee-5.0.0.98-20151026.081056-5-javadoc.jar. Return code is: 401, ReasonPhrase: Unauthorized. }}
So it has not got to do with the PR / code change.

Sean Corfield 4 November 2015 at 21:42

The PR fails in Travis. Does it need updating or is Travis just broken at the moment?

Paul Klinkenberg 26 October 2015 at 09:04

Github pull request

Details

Assignee

Reporter

Labels

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Affects versions

Priority

Created 26 October 2015 at 09:02
Updated 19 November 2015 at 09:14

Flag notifications