You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Guillaume Nodet <gn...@apache.org> on 2015/05/18 14:49:28 UTC
[VOTE] Release Apache Felix Connect 0.1.0
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
Re: [VOTE] Release Apache Felix Connect 0.1.0
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1 (non binding)
Regards
JB
On 05/18/2015 02:49 PM, Guillaume Nodet 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
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [VOTE] Release Apache Felix Connect 0.1.0
Posted by Pierre De Rop <pi...@gmail.com>.
Thanks for the information Karl.
/Pierre
On Thu, May 21, 2015 at 11:10 PM, Karl Pauls <ka...@gmail.com> wrote:
> I think it would be great if you could fix this!
>
> To answer the question of Pierre: I don't think we contain all core API in
> Felix framework nor do we necessarily have to include all in connect IMO.
> We should however (and do so for framework) include the one we need to run.
>
> btw.: there is some bug report here:
>
> https://groups.google.com/forum/#!topic/pojosr-discuss/saPAJS25s2Q
>
> which I think is still relevant atm. It sounds like it should be pretty
> straight forward and worthwhile to fix so if you had a moment to do it that
> would be great (I'm not going to get to it by tomorrow) - otherwise, I'll
> create a JIRA issue for it and we fix it in a later release.
>
> regards,
>
> Karl
>
> On Thu, May 21, 2015 at 10:13 PM, Guillaume Nodet <gn...@apache.org>
> wrote:
>
> > 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 <pi...@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 <gn...@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
> > > >
> > >
> >
>
>
>
> --
> Karl Pauls
> karlpauls@gmail.com
> http://twitter.com/karlpauls
> http://www.linkedin.com/in/karlpauls
> https://profiles.google.com/karlpauls
>
Re: [VOTE] Release Apache Felix Connect 0.1.0
Posted by Karl Pauls <ka...@gmail.com>.
I think it would be great if you could fix this!
To answer the question of Pierre: I don't think we contain all core API in
Felix framework nor do we necessarily have to include all in connect IMO.
We should however (and do so for framework) include the one we need to run.
btw.: there is some bug report here:
https://groups.google.com/forum/#!topic/pojosr-discuss/saPAJS25s2Q
which I think is still relevant atm. It sounds like it should be pretty
straight forward and worthwhile to fix so if you had a moment to do it that
would be great (I'm not going to get to it by tomorrow) - otherwise, I'll
create a JIRA issue for it and we fix it in a later release.
regards,
Karl
On Thu, May 21, 2015 at 10:13 PM, Guillaume Nodet <gn...@apache.org> wrote:
> 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 <pi...@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 <gn...@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
> > >
> >
>
--
Karl Pauls
karlpauls@gmail.com
http://twitter.com/karlpauls
http://www.linkedin.com/in/karlpauls
https://profiles.google.com/karlpauls
Re: [VOTE] Release Apache Felix Connect 0.1.0
Posted by Guillaume Nodet <gn...@apache.org>.
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 <pi...@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 <gn...@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
> >
>
Re: [VOTE] Release Apache Felix Connect 0.1.0
Posted by Pierre De Rop <pi...@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 <gn...@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
>
Re: [VOTE] Release Apache Felix Connect 0.1.0
Posted by Chetan Mehrotra <ch...@gmail.com>.
All checks passed
+1 (non binding)
Chetan Mehrotra