No, the idea is that these packages should be provided by the security provider (as they are just bloat without it). The work on getting the resolver separated apparently did drag in some additional osgi core packages due to the transitivity of maven deps which get picked up because we use org.osgi.service.* in the bnd rule. I guess we could just remove them in the next release and don't worry about it for now but on the other hand we might get people to depend on them being delivered by the framework (i.e., we maybe should redo this release) - thoughts?
regards, Karl On Mon, Apr 20, 2015 at 3:14 PM, David Bosschaert < david.bosscha...@gmail.com> wrote: > I noticed that this release now contains the following two packages > that it previously didn't: > > org.osgi.service.condpermadmin > org.osgi.service.permissionadmin > > Is that the intention? > > Thanks, > > David > > On 20 April 2015 at 14:22, Karl Pauls <karlpa...@gmail.com> wrote: > > I would like to call a vote on the following subproject releases: > > > > resolver 1.2.0 > > framework 5.0.0 > > main 5.0.0 > > main.distribution 5.0.0 > > > > The main changelogs are in jira and at: > > > https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.resolver-1.2.0/doc/changelog.txt > > > https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.framework-5.0.0/doc/changelog.txt > > > > Staging repositories: > > https://repository.apache.org/content/repositories/orgapachefelix-1062/ > > > > You can use this UNIX script to download the release and verify the > > signatures: > > http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh > > > > Usage: > > sh check_staged_release.sh 1062 /tmp/felix-staging > > > > Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] -1 Veto the release (please provide specific comments) > -- Karl Pauls karlpa...@gmail.com http://twitter.com/karlpauls http://www.linkedin.com/in/karlpauls https://profiles.google.com/karlpauls
