It makes sense to have all scripting stuff underneath scripting; I think it also makes sense to move it to contrib.
Actually, the bundles under "extensions" should never have "extensions" in their artifact name or in package names as this clearly creates problems when moving them around. However, we didn't follow that rule in the beginning very strictly...but it makes sense to remove this when moving as well - maybe not from the artifact name as this would break compatibility though :( Carsten 2014-08-27 9:10 GMT+02:00 Robert Munteanu <[email protected]>: > On Tue, Aug 26, 2014 at 11:41 PM, Oliver Lietz <[email protected]> > wrote: > > On Tuesday 26 August 2014 21:00:29 Robert Munteanu wrote: > >> Hi, > >> > >> We solved 6 issues in this release: > >> https://issues.apache.org/jira/browse/SLING/fixforversion/12315240 > >> > >> There are still some outstanding issues: > >> https://issues.apache.org/jira/browse/SLING/component/12312240 > > > > Shouldn't we move this module to contrib/scripting and change the > package from > > extensions to scripting (to be in line with the other scripting modules, > e.g. > > freemarker, jsp, javascript, ...)? > > Good question, let's discuss it separately from the release. I see two > proposal here: > > 1. Move the groovy extensions bundle to contrib > 2. Move the groovy extensions bundle to scripting ( contrib or not ) > > I have no strong opinion on either, maybe others have some thoughts on > this. > > Robert > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
