You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2016/10/17 16:22:59 UTC
[jira] [Resolved] (SLING-6161) Correctly implement Path.matches
[ https://issues.apache.org/jira/browse/SLING-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-6161.
-------------------------------------
Resolution: Fixed
> Correctly implement Path.matches
> --------------------------------
>
> Key: SLING-6161
> URL: https://issues.apache.org/jira/browse/SLING-6161
> Project: Sling
> Issue Type: Task
> Components: API
> Affects Versions: API 2.14.2
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Blocker
> Fix For: API 2.15.0
>
>
> With SLING-5909 a new behaviour has been introduced to Path.matches() which supports matches a Path against a glob pattern.
> The attached test only convers a Path object with "/", but it is unclear what the intend of this change actually is - and what the semantics is.
> The javadoc of matches() right now clearly states that the argument should be a path, therefore glob pattern is not supported in that method.
> [~radu.cotescu] Could you please comment on the intended behaviour?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)