Good question Stefan. I had at one point intended for multiple resource providers to be able to register Service User creation / update faculties. Unfortunately, it ended up being more closely tied to the JCR than I'd initially hoped and I failed to clean up the package-info.java file.
Do we see this as a blocking issue? Should we proceed and I'll queue up a 1.0.2 release to remove this file? Thanks, Dan On Tue, Jan 16, 2018 at 4:44 AM, Stefan Seifert <[email protected]> wrote: > why has the bundle "Apache Sling Service User WebConsole version 1.0.0" an > export definition? > > > Export-Package: org.apache.sling.serviceuser.webconsole;version="1.0.0" > > it's an empty package containing no classes. i assume [1] can be just > removed. > > stefan > > [1] https://github.com/apache/sling-org-apache-sling- > serviceuser-webconsole/blob/master/src/main/java/org/ > apache/sling/serviceuser/webconsole/package-info.java > > > >-----Original Message----- > >From: Daniel Klco [mailto:[email protected]] > >Sent: Saturday, January 13, 2018 1:43 AM > >To: [email protected] > >Subject: [VOTE] Release Apache Sling Service User Mapper version 1.4.0 and > >Apache Sling Service User WebConsole version 1.0.0 > > > >Hi, > > > >We solved 1 issues in this release: > >https://issues.apache.org/jira/projects/SLING/versions/12342441 > > > >Staging repository: > >https://repository.apache.org/content/repositories/orgapachesling-1849/ > > > >You can use this UNIX script to download the release and verify the > >signatures: > >https://raw.githubusercontent.com/apache/sling-tooling- > >release/master/check_staged_release.sh > > > >Usage: > >curl > >https://raw.githubusercontent.com/apache/sling-tooling- > >release/master/check_staged_release.sh > >| bash -s 1849 > > > >Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] 0 Don't care > > [ ] -1 Don't release, because ... > > > >This majority vote is open for at least 72 hours. >
