Re: Proposal for slight amendment to Felix provisional OSGi API policy

2017-01-03 Thread Carsten Ziegeler
Thomas Watson wrote > This has come to my attention because I am working on some fixes in the SCR > implementation. I noticed the latest SCR in trunk now depends on > org.apache.felix.configadmin 1.9.0-SNAPSHOT. And I think > org.apache.felix.configadmin 1.9.0 is being used to implement OSGi R7.

[jira] [Created] (FELIX-5474) Do not call no-arg Bundle.getHeaders() method

2017-01-03 Thread Thomas Watson (JIRA)
Thomas Watson created FELIX-5474: Summary: Do not call no-arg Bundle.getHeaders() method Key: FELIX-5474 URL: https://issues.apache.org/jira/browse/FELIX-5474 Project: Felix Issue Type: Bug

Re: Proposal for slight amendment to Felix provisional OSGi API policy

2017-01-03 Thread Thomas Watson
This has come to my attention because I am working on some fixes in the SCR implementation. I noticed the latest SCR in trunk now depends on org.apache.felix.configadmin 1.9.0-SNAPSHOT. And I think org.apache.felix.configadmin 1.9.0 is being used to implement OSGi R7. So now we have OSGi R7 API

Re: Proposal for slight amendment to Felix provisional OSGi API policy

2017-01-03 Thread David Bosschaert
Hi Tom, My proposal here only applies to implementations of entirely new specs. Updates on existing specs are not covered, hence the point around versions <1. I completely agree that updates to existing specs should be done on a branch to keep trunk releasable. Cheers, David On 3 January 2017

Re: Proposal for slight amendment to Felix provisional OSGi API policy

2017-01-03 Thread Thomas Watson
Why do OSGi R-next work directly in trunk where I would expect releases could be done at any time. It seems to me that trunk should remain 'releasable'. It would be much more simple to do OSGi R-next work in a dedicated branch where you have the freedom to put interim OSGi APIs assuming we would

Re: Proposal for slight amendment to Felix provisional OSGi API policy

2017-01-03 Thread Richard S. Hall
On 1/3/17 11:59 , David Bosschaert wrote: Hi Felix and Richard, On 3 January 2017 at 16:40, Richard S. Hall wrote: On 1/3/17 11:21 , Felix Meschberger wrote: Hi Upfront I like the amended proposal of using a version < 1 and a mandatory attribute „provisional“ with value „felix“. As Neil s

Re: Proposal for slight amendment to Felix provisional OSGi API policy

2017-01-03 Thread David Bosschaert
Hi Felix and Richard, On 3 January 2017 at 16:40, Richard S. Hall wrote: > > On 1/3/17 11:21 , Felix Meschberger wrote: > >> Hi >> >> Upfront I like the amended proposal of using a version < 1 and a >> mandatory attribute „provisional“ with value „felix“. As Neil said, BND >> will solve this for

Re: Proposal for slight amendment to Felix provisional OSGi API policy

2017-01-03 Thread Richard S. Hall
On 1/3/17 11:21 , Felix Meschberger wrote: Hi Upfront I like the amended proposal of using a version < 1 and a mandatory attribute „provisional“ with value „felix“. As Neil said, BND will solve this for imports be it the bndtools or the maven bundle plugin. Not declaring a version and thus u

Re: Proposal for slight amendment to Felix provisional OSGi API policy

2017-01-03 Thread Felix Meschberger
Hi Upfront I like the amended proposal of using a version < 1 and a mandatory attribute „provisional“ with value „felix“. As Neil said, BND will solve this for imports be it the bndtools or the maven bundle plugin. Not declaring a version and thus using 0.0.0 will have BND generate a version-l

Re: Proposal for slight amendment to Felix provisional OSGi API policy

2017-01-03 Thread David Bosschaert
Hi Christian, On 3 January 2017 at 10:00, Christian Schneider wrote: > >> Why do we need the mandatory provisional attribute? With the version < 1 > we already ensure that we have a clean cut when the > final API is released. > > I think this extra protection only makes it harder to use the API.

Re: Proposal for slight amendment to Felix provisional OSGi API policy

2017-01-03 Thread Christian Schneider
On 03.01.2017 10:46, David Bosschaert wrote: Hi Richard, On 23 December 2016 at 19:19, Richard S. Hall wrote: I'm not for changing the policy. The whole point behind the policy is that anything that we released is in some way blessed and lives forever. If we release packages in the OSGi names

Re: Proposal for slight amendment to Felix provisional OSGi API policy

2017-01-03 Thread David Bosschaert
Hi Richard, On 23 December 2016 at 19:19, Richard S. Hall wrote: > I'm not for changing the policy. The whole point behind the policy is that > anything that we released is in some way blessed and lives forever. If we > release packages in the OSGi namespace, they look official even potentially

Re: [VOTE] Release FileInstall 3.5.8

2017-01-03 Thread Guillaume Nodet
2017-01-03 10:10 GMT+01:00 Ferry Huberts : > > > On 03/01/17 10:06, Guillaume Nodet wrote: > >> 2017-01-03 10:03 GMT+01:00 Ferry Huberts : >> >> >>> >>> On 19/12/16 10:11, Guillaume Nodet wrote: >>> >>> I've staged a FileInstall 3.5.8 release. It contains the following fix: [FELIX-513

Re: [VOTE] Release FileInstall 3.5.8

2017-01-03 Thread Ferry Huberts
On 03/01/17 10:06, Guillaume Nodet wrote: 2017-01-03 10:03 GMT+01:00 Ferry Huberts : On 19/12/16 10:11, Guillaume Nodet wrote: I've staged a FileInstall 3.5.8 release. It contains the following fix: [FELIX-5133][fileinstall] Remove properties that are not present in updated

Re: [VOTE] Release FileInstall 3.5.8

2017-01-03 Thread Guillaume Nodet
2017-01-03 10:03 GMT+01:00 Ferry Huberts : > > > On 19/12/16 10:11, Guillaume Nodet wrote: > >> I've staged a FileInstall 3.5.8 release. >> It contains the following fix: >>[FELIX-5133][fileinstall] Remove properties that are not present in >> updated

Re: [VOTE] Release FileInstall 3.5.8

2017-01-03 Thread Ferry Huberts
On 19/12/16 10:11, Guillaume Nodet wrote: I've staged a FileInstall 3.5.8 release. It contains the following fix: [FELIX-5133][fileinstall] Remove properties that are not present in updated configuration It seems that it's only fixed for

[jira] [Created] (FELIX-5473) [RFC 222] 5.3 Implement multipart handling

2017-01-03 Thread Carsten Ziegeler (JIRA)
Carsten Ziegeler created FELIX-5473: --- Summary: [RFC 222] 5.3 Implement multipart handling Key: FELIX-5473 URL: https://issues.apache.org/jira/browse/FELIX-5473 Project: Felix Issue Type: Su

[RESULT] [VOTE] Release FileInstall 3.5.8

2017-01-03 Thread Guillaume Nodet
Sure, sorry about the delay, I was in vacation. Closing this vote with 6 +1s and no other votes. Thx to everyone ! 2017-01-02 10:37 GMT+01:00 Grzegorz Grzybek : > Guillaume, any chance to have the release? > > regards > Grzegorz Grzybek > > 2016-12-19 15:10 GMT+01:00 Raymond Auge : > > > +1 (non

Re: [VOTE] Release FileInstall 3.5.8

2017-01-03 Thread Guillaume Nodet
+1 2016-12-19 10:11 GMT+01:00 Guillaume Nodet : > I've staged a FileInstall 3.5.8 release. > It contains the following fix: >[FELIX-5133][fileinstall] Remove properties that are not present in > updated configuration > The repository is avail

[jira] [Resolved] (FELIX-5299) [RFC 223] 5.4 Support Servlets without a pattern

2017-01-03 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-5299. - Resolution: Fixed > [RFC 223] 5.4 Support Servlets without a pattern > ---

[jira] [Updated] (FELIX-5299) [RFC 223] 5.4 Support Servlets without a pattern

2017-01-03 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-5299: Fix Version/s: http.bridge-3.1.0 http.jetty-3.5.0 http.

[jira] [Resolved] (FELIX-5298) [RFC 223] 5.2 Request Preprocessing

2017-01-03 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-5298. - Resolution: Fixed > [RFC 223] 5.2 Request Preprocessing >

[jira] [Updated] (FELIX-5298) [RFC 223] 5.2 Request Preprocessing

2017-01-03 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-5298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-5298: Fix Version/s: http.bridge-3.1.0 http.jetty-3.5.0 http.

[jira] [Updated] (FELIX-5297) [RFC 223] 5.1 Whiteboard Services and Http Service

2017-01-03 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-5297: Fix Version/s: http.bridge-3.1.0 http.jetty-3.5.0 http.

[jira] [Resolved] (FELIX-5297) [RFC 223] 5.1 Whiteboard Services and Http Service

2017-01-03 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-5297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-5297. - Resolution: Fixed > [RFC 223] 5.1 Whiteboard Services and Http Service > -

[jira] [Updated] (FELIX-5296) Implement Http Whiteboard Service Updates (RFC 223)

2017-01-03 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-5296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated FELIX-5296: Fix Version/s: http.bridge-3.1.0 http.jetty-3.5.0 http.

[jira] [Assigned] (FELIX-5173) Metatype service's BundleResources ignore properties provided by fragment bundles

2017-01-03 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/FELIX-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned FELIX-5173: --- Assignee: J.W. Janssen > Metatype service's BundleResources ignore properties provide