[
https://issues.apache.org/jira/browse/SLING-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reopened SLING-5455:
-------------------------------------
Sorry, but I don't agree with the solution.
This adds another bundle with just a single class and using this util class
then requires this additional bundle (or the class can be embedded).
The name "commons" sounds too generic to me as well. I can already imagine that
all "useful" stuff will end up here, creating a collection of totally unrelated
things.
I think in the discussion java packages and how they are packaged have been
combined. We can easily have this in a package org.apache.sling.api.FOO, decide
today to include this in the api bundle and later on move it to a separate
bundle.
However I suggest we add this to the already existing
org.apache.sling.api.resource.util as this already contains path related
utility classes
> 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)
