org.apache.sling.commons and testing

[Oliver Lietz <ap...@oliverlietz.de>]

hi,

the package namespace org.apache.sling.commons and the spaces under 
/bundles/commons and /contrib/commons are usually used for modules (bundles) 
*NOT* depending on Sling (which can be run outside of Sling).

Can we keep that rule and move resourcebuilder and js and adjust their 
packages?

This would strictly speaking also apply to the very old and released testing 
module.

I would prefer to have all test-related modules (also the ones in /launchpad) 
under /testing in general.

WDYT?

Happy New Year!
O.

Re: org.apache.sling.commons and testing

[Bertrand Delacretaz <bd...@apache.org>]

Hi,

On Wed, Jan 6, 2016 at 12:49 PM, Oliver Lietz <ap...@oliverlietz.de> wrote:
> the package namespace org.apache.sling.commons and the spaces under
> /bundles/commons and /contrib/commons are usually used for modules (bundles)
> *NOT* depending on Sling (which can be run outside of Sling).
>
> Can we keep that rule and move resourcebuilder and js and adjust their
> packages? ...

Makes sense, I moved the resourcebuilder module under bundles/extensions.

> Happy New Year!

Indeed, happy new year to all! It's great to see lots of good ideas
floating around in this new year ;-)

-Bertrand

Re: org.apache.sling.commons and testing

[Carsten Ziegeler <cz...@apache.org>]

+1

Oliver Lietz wrote
> hi,
> 
> the package namespace org.apache.sling.commons and the spaces under 
> /bundles/commons and /contrib/commons are usually used for modules (bundles) 
> *NOT* depending on Sling (which can be run outside of Sling).
> 
> Can we keep that rule and move resourcebuilder and js and adjust their 
> packages?
> 
> This would strictly speaking also apply to the very old and released testing 
> module.
> 
> I would prefer to have all test-related modules (also the ones in /launchpad) 
> under /testing in general.
> 
> WDYT?
> 
> Happy New Year!
> O.
> 
> 


 
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org