[
https://issues.apache.org/jira/browse/SLING-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124830#comment-15124830
]
Carsten Ziegeler commented on SLING-5455:
-----------------------------------------
Yes, consolidating other stuff over time makes sense, that's why I started a
new package for the path based utilities. I'm fine with using .path
(o.a.s.resource.path) instead of .util - .text is imho too confusing.
I think the key point is that we're using a new package (and not
o.a.s.resource) - whether this ends up in a different bundle or not is a
different question. But having it in our API bundle makes things much easier.
> Add helper class to construct valid paths
> -----------------------------------------
>
> Key: SLING-5455
> URL: https://issues.apache.org/jira/browse/SLING-5455
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Minor
> Fix For: Commons 1.0.0
>
>
> When working with paths it's easy to combine two valid paths into an invalid
> one. For instance
> * '/parent/' + '/child' -> '/parent//child'
> * '/parent' + 'child' -> '/parentchild'
> We should add a simple helper class which allows to build paths, with a
> fluent syntax.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
