Thanks Robert! David
On Wed, 7 Nov 2018 at 12:47, Robert Munteanu <romb...@apache.org> wrote: > Hi David, > > On Wed, 2018-11-07 at 12:01 +0000, David Bosschaert wrote: > > Hi all, > > > > I started migrating the code from the sling-whiteboard to individual > > repositories. > > The final step is to add the sources to the kibble demo instance > > http://demo.kibble.apache.org > > > > When I add > > https://github.com/apache/sling-org-apache-sling-feature-apiregions.git > > > https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions.git > > as new github sources, Kibble responds with: > > "You don't have permission to add sources to this organisation." > > > > Anyone an idea? > > Apparently the demo user does not have rights, you need to sign up with > a different user. I've added them myself and will update the > documentation to reflect that information. > > Thanks, > > Robert > > > > > David > > > > On Wed, 7 Nov 2018 at 10:57, Carsten Ziegeler <cziege...@apache.org> > > wrote: > > > > > +1 to gradudate > > > > > > Carsten > > > > > > Am 06.11.2018 um 16:50 schrieb David Bosschaert: > > > > Hi all, > > > > > > > > Over the past little while I have worked on an implementation for > > > > a > > > runtime > > > > enforcement component for API Regions for Sling Features [1]. > > > > > > > > The implementation is based on 2 components. > > > > > > > > a. Merge/PostProcessor handlers that work on the 'api-regions' > > > > section in > > > > the feature files. These components know how to merge api-regions > > > sections > > > > into a target feature and the PostProcessor handlers generate a > > > > number of > > > > properties files that drive the runtime enforcement > > > > implementation of > > > this. > > > > For details see [2]. > > > > > > > > b. The runtime component which is implemented as an OSGi > > > > Framework > > > > extension bundle. Registers a ResolverHookFactory service with > > > > the > > > > framework which is consulted by the OSGi resolver. The hook can > > > > prevent > > > > certain resolutions from happening and is driven by the > > > > properties files > > > > generated by the process in a. to enforce the regions as defined > > > > in the > > > > feature files. For details see [3]. > > > > > > > > Currently these two new components [2][3] are in the sling- > > > > whiteboard, > > > but > > > > it would be great to graduate them out of there into their own > > > > Sling > > > > repositories. Does the sling community think that this would be > > > > the right > > > > thing to do? > > > > > > > > Many thanks, > > > > > > > > David > > > > > > > > [1] > > > > > > > > https://github.com/apache/sling-org-apache-sling-feature/blob/master/apicontroller.md > > > > [2] > > > > > > > > https://github.com/apache/sling-whiteboard/tree/master/featuremodel/feature-extension-apiregions > > > > [3] > > > > > > > > https://github.com/apache/sling-whiteboard/tree/master/featuremodel/feature-apiregions > > > > > > -- > > > Carsten Ziegeler > > > Adobe Research Switzerland > > > cziege...@apache.org > > > > > >
