+1
Jean-baptiste Onofré wrote
Hi all,
We fixed an issue on this release (release notes):
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12344918
This is actually a backport of the fix from Framework 6.0.2 to work with
JDK 11.0.2.
As Felix Framework 5.6.10 is the
+1 (non-binding)
Thanks!
Regards,
François Papon
fpa...@apache.org
Le 01/02/2019 à 19:17, Jean-Baptiste Onofré a écrit :
> Hi all,
>
> We fixed an issue on this release (release notes):
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12344918
>
> This is actually a
+1 (binding)
Regards
JB
On 01/02/2019 16:00, Georg Henzler wrote:
> Hi all,
>
> this is a "test release" to be able to validate the modules as version
> 0.1.1 (now with correct export version for API) before releasing 2.0.0.
>
> We solved 11 issues in this release:
>
[
https://issues.apache.org/jira/browse/FELIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated FELIX-6045:
Component/s: File Install
> FileInstall creates bundles from directories
>
[
https://issues.apache.org/jira/browse/FELIX-6045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned FELIX-6045:
---
Assignee: Jean-Baptiste Onofré
> FileInstall creates bundles from
+1
regards,
Karl
On Fri, Feb 1, 2019 at 5:58 PM David Bosschaert
wrote:
>
> +1
>
> David
>
> On Fri, 1 Feb 2019 at 15:17, Jean-Baptiste Onofré wrote:
>
> > Hi all,
> >
> > We fixed an issue on this release (release notes):
> >
> >
[
https://issues.apache.org/jira/browse/FELIX-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758689#comment-16758689
]
ASF GitHub Bot commented on FELIX-6046:
---
GitHub user sebratton opened a pull request:
GitHub user sebratton opened a pull request:
https://github.com/apache/felix/pull/181
FELIX-6046 - fix gogo shell thread interrupt.
proposed fix for FELIX-6046
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sebratton/felix
Samuel Bratton created FELIX-6046:
-
Summary: gogo shell interrupts wrong thread on Activator stop
Key: FELIX-6046
URL: https://issues.apache.org/jira/browse/FELIX-6046
Project: Felix
Issue
[
https://issues.apache.org/jira/browse/FELIX-5986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758611#comment-16758611
]
Scott Leschke commented on FELIX-5986:
--
The ClosedWatchServerException now only appears to happen on
Scott Leschke created FELIX-6045:
Summary: FileInstall creates bundles from directories
Key: FELIX-6045
URL: https://issues.apache.org/jira/browse/FELIX-6045
Project: Felix
Issue Type: Bug
+1
- Ray
On Fri, Feb 1, 2019 at 12:43 PM Andrei Dulvac wrote:
> +1 (non-binding)
>
> - Andrei
>
> On Fri, Feb 1, 2019 at 6:33 PM Karl Pauls wrote:
>
> > +1
> >
> > regards,
> >
> > Karl
> >
> > On Fri, Feb 1, 2019 at 6:20 PM Christian Schneider
> > wrote:
> > >
> > > +1 (non binding)
> > >
>
[
https://issues.apache.org/jira/browse/FELIX-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758550#comment-16758550
]
ASF GitHub Bot commented on FELIX-6044:
---
GitHub user tjwatson opened a pull request:
GitHub user tjwatson opened a pull request:
https://github.com/apache/felix/pull/180
FELIX-6044 - avoid calling ungetServiceObject too early for simple case of
SingleRefPair
You can merge this pull request into a Git repository by running:
$ git pull
+1 (non-binding)
- Andrei
On Fri, Feb 1, 2019 at 6:33 PM Karl Pauls wrote:
> +1
>
> regards,
>
> Karl
>
> On Fri, Feb 1, 2019 at 6:20 PM Christian Schneider
> wrote:
> >
> > +1 (non binding)
> >
> > Christian
> >
> > Am Fr., 1. Feb. 2019 um 16:00 Uhr schrieb Georg Henzler <
>
+1
regards,
Karl
On Fri, Feb 1, 2019 at 6:20 PM Christian Schneider
wrote:
>
> +1 (non binding)
>
> Christian
>
> Am Fr., 1. Feb. 2019 um 16:00 Uhr schrieb Georg Henzler :
>
> > Hi all,
> >
> > this is a "test release" to be able to validate the modules as version
> > 0.1.1 (now with correct
[
https://issues.apache.org/jira/browse/FELIX-5974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758512#comment-16758512
]
Thomas Watson commented on FELIX-5974:
--
Notice that this fix has caused a regression with FELIX-6044
Thomas Watson created FELIX-6044:
Summary: Component deactivation does not cause reference services
to be ungotten
Key: FELIX-6044
URL: https://issues.apache.org/jira/browse/FELIX-6044
Project: Felix
[
https://issues.apache.org/jira/browse/FELIX-6044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Watson updated FELIX-6044:
-
Description:
The fix to FELIX-5974 has caused an issue for the default reference scope of
+1 (non binding)
Christian
Am Fr., 1. Feb. 2019 um 16:00 Uhr schrieb Georg Henzler :
> Hi all,
>
> this is a "test release" to be able to validate the modules as version
> 0.1.1 (now with correct export version for API) before releasing 2.0.0.
>
> We solved 11 issues in this release:
>
>
+1
David
On Fri, 1 Feb 2019 at 15:17, Jean-Baptiste Onofré wrote:
> Hi all,
>
> We fixed an issue on this release (release notes):
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12344918
>
> This is actually a backport of the fix from Framework 6.0.2 to work with
+1
- Ray
On Fri, Feb 1, 2019 at 10:17 AM Jean-Baptiste Onofré
wrote:
> Hi all,
>
> We fixed an issue on this release (release notes):
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12344918
>
> This is actually a backport of the fix from Framework 6.0.2 to work
GitHub user pleeplop opened a pull request:
https://github.com/apache/felix/pull/179
Update SCR dependencies to R7
SCR export some OSGi packages (org.osgi.util.promise and uses
org.osgi.util.function).
So we should update them to the latest release.
You can merge this
Hi all,
We fixed an issue on this release (release notes):
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12344918
This is actually a backport of the fix from Framework 6.0.2 to work with
JDK 11.0.2.
As Felix Framework 5.6.10 is the last version using OSGi R6
Hi all,
this is a "test release" to be able to validate the modules as version
0.1.1 (now with correct export version for API) before releasing 2.0.0.
We solved 11 issues in this release:
Sigh - we'll have a fixed version in a minute.
On 2019-02-01 15:03, Christian Schneider wrote:
Seems I was too quick.
I just checked the package version of the API packages. It stayed at
2.0.0.
We must use 0.1.0 there, else the 0.1.0 release would not really help.
So I revert to
-1 (non
+1 (non binding)
Christian
Am Fr., 1. Feb. 2019 um 14:11 Uhr schrieb Georg Henzler :
> Hi all,
>
> this is a "test release" to be able to validate the modules as version
> 0.1.0 before releasing 2.0.0.
>
> We solved 11 issues in this release:
>
>
[
https://issues.apache.org/jira/browse/FELIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated FELIX-6035:
Affects Version/s: framework-5.6.10
> Allow urlhandlers to create urls for jrt
[
https://issues.apache.org/jira/browse/FELIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758330#comment-16758330
]
Jean-Baptiste Onofré commented on FELIX-6035:
-
Here's the backport on the branch:
[
https://issues.apache.org/jira/browse/FELIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved FELIX-6035.
-
Resolution: Fixed
> Allow urlhandlers to create urls for jrt protocol without an
Seems I was too quick.
I just checked the package version of the API packages. It stayed at 2.0.0.
We must use 0.1.0 there, else the 0.1.0 release would not really help.
So I revert to
-1 (non binding)
Christian
Am Fr., 1. Feb. 2019 um 14:48 Uhr schrieb Christian Schneider <
With the 0.1.0 release we now have the chance to look into the API without
too much hurry.
So lets check if we would like to have bigger changes but we should not
hold off a stable release for too long.
I think aiming for a stable release in 1-2 weeks should be realistic.
About the release
[
https://issues.apache.org/jira/browse/FELIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758299#comment-16758299
]
Jean-Baptiste Onofré commented on FELIX-6035:
-
[~karlpauls] but new framework 6 is OSGi R7
[
https://issues.apache.org/jira/browse/FELIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758310#comment-16758310
]
Jean-Baptiste Onofré commented on FELIX-6035:
-
[~karlpauls] OSGi R7 is planned for Karaf
[
https://issues.apache.org/jira/browse/FELIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758308#comment-16758308
]
Karl Pauls commented on FELIX-6035:
---
[~jbonofre], ah ok - yeah, framework 6 is OSGi R7. If you can't
Hi Georg.
I don't want to get into a flaming debate about versioning. I've seen on
the internet what happens.
> So to me it really boils down to not counting down when moving forward for
people upgrading the health checks - it would feel awkward if you had 1.0.2
and then you use 1.0.0 again
It
Hi all,
this is a "test release" to be able to validate the modules as version
0.1.0 before releasing 2.0.0.
We solved 11 issues in this release:
I'm taking the hat of the many developers out there in the world that
use the API (the ones we cannot talk to and that do not read this
mailing list) - 2.0.0 it is to not confuse them. See my response from
this morning [1]
Also the Sling API has been stable for long (Bertrand has done a
Hi,
(Unfortunately I haven't had a chance to look over it properly)
I'd just like to say I agree with Christian and Ray - a 2.0.0 initial
release is not only weird, but confusing. Why?
I support doing 0.X.0 releases until the api is proven to be stable and
then release *1.0.0*. Why 2.0.0?
-
Hi Bertrand,
Testing that on snapshots is not optimal IMO as those are potentially
moving targets.
Let's do it like this then: I'll push a release 0.1.0 today (with
another short [VOTE] today that I would ask you to quickly vote +1 for)
and I'll leave this vote and [1] open until Christian
On Thu, Jan 31, 2019 at 5:37 PM Christian Schneider
wrote:
> ...How about releasing 0.1.0 now and release a 2.0.0 in two weeks?
> It would give people time to test the new project and still allow us to do
> incompatible changes
I'm also strongly in favor of that, especially as these modules
[
https://issues.apache.org/jira/browse/FELIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758231#comment-16758231
]
Karl Pauls commented on FELIX-6035:
---
[~jbonofre], I'm not totally against it but are you sure it isn't
[
https://issues.apache.org/jira/browse/FELIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated FELIX-6035:
Fix Version/s: framework-5.6.11
> Allow urlhandlers to create urls for jrt
[
https://issues.apache.org/jira/browse/FELIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758229#comment-16758229
]
Jean-Baptiste Onofré commented on FELIX-6035:
-
[~coheigea] I'm tackling that !
> Allow
[
https://issues.apache.org/jira/browse/FELIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reopened FELIX-6035:
-
Assignee: Jean-Baptiste Onofré (was: Karl Pauls)
> Allow urlhandlers to
[
https://issues.apache.org/jira/browse/FELIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758227#comment-16758227
]
Jean-Baptiste Onofré commented on FELIX-6035:
-
In order to support JDK 11.0.2 in Karaf, I
[
https://issues.apache.org/jira/browse/FELIX-6035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16758228#comment-16758228
]
Colm O hEigeartaigh commented on FELIX-6035:
Please backport to 5.x as well, as it's causing
GitHub user lefou opened a pull request:
https://github.com/apache/felix/pull/178
Added PojoServiceRegistry.registerBundle method
Added support to not automatically start scanned bundles. That way, one can
selectively start (and stop) bundles.
I also added a new config
48 matches
Mail list logo
