Yeah, it seems the package is missing, given all the other packages are embedded in the jar. I'll try to cut a new release after adding the missing package tomorrow.
2015-05-20 11:35 GMT+02:00 Pierre De Rop <pierre.de...@gmail.com>: > Hello Guillaume, > > before voting, I have a question: > > I was using so far the initial version of Felix connect that was initially > committed in the felix-trunk, and this very first release was using using > the osgi core 4.3.1 api. > > So, I just did a non regression test, but got a NoClassDefFoundError on the > org/osgi/resource/Capability class because the candidate release is now > based on osgi core 5.0.0 api. For example, the > org/apache/felix/connect/felix/framework/capabilityset/CapabilitySet.java > is importing the org.osgi.resource.Capability. > > so, I had to include in the classpath the osgi.core-5.0.0.jar and then my > non regression test passed OK. > > but I just wonder if the org/osgi/resource/Capability class should be > included in the connect.jar ? > and more generally, does the connect.jar contains all the osgi core 5.0.0 > API ? (it's the case for the Felix framework, if I'm correct ?) > > thanks; > /Pierre > > On Mon, May 18, 2015 at 2:49 PM, Guillaume Nodet <gno...@apache.org> > wrote: > > > I've cut a release of Felix Connect 0.1.0 > > > > > > > http://svn.apache.org/repos/asf/felix/releases/org.apache.felix.connect-0.1.0/ > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachefelix-1068 > > > > 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 1068 /tmp/felix-staging > > > > Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] -1 Veto the release (please provide specific comments) > > > > Cheers, > > Guillaume Nodet > > >
