I think we should make this a table instead of a list. This lets us keep track for each dependency we're proposing to put into the attic:
- Last update (excluding pom.xml or license changes) - Where the code is referenced (if anywhere) Otherwise, it's going to be really difficult for people without the time to go module-by-module to make an educated determination of what should stay or go. Sound good? On Fri, Sep 30, 2016 at 8:55 AM, Stefan Seifert <[email protected]> wrote: > looks good to me, some comments on the current list: > > - contrib/extensions/bgservlets => serveral releases on it this year > - contrib/scripting/groovy => last release this year > - contrib/sling-s3 => is not so old, perhaps move below crankstart as it > belongs to it? > > i assume in samples/ there are also some candidates. > > stefan > > >-----Original Message----- > >From: Carsten Ziegeler [mailto:[email protected]] > >Sent: Friday, September 30, 2016 1:55 PM > >To: [email protected] > >Subject: Re: sling attic / cleanup > > > >Started a wiki page to collect the modules: > > > > https://cwiki.apache.org/confluence/display/SLING/Module+Cleanup > > > >-- > >Carsten Ziegeler > >Adobe Research Switzerland > >[email protected] > > > > >
