Re: Bug fix release for resolver / framework

Yes, I see: - r1685100 | gnodet | 2015-06-12 17:10:01 +0200 (Fri, 12 Jun 2015) | 1 line [FELIX-4914] Resolution problem with fragments and identity requirements - so, I think we are good. @Karl, you can go ahead for the release during the week end. Thanks guys ! Regards JB On 06/12/

[jira] [Comment Edited] (FELIX-4908) X-Forward Header support when running behind a proxy/load balancer

[ https://issues.apache.org/jira/browse/FELIX-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584357#comment-14584357 ] Martin Petrovsky edited comment on FELIX-4908 at 6/13/15 1:15 AM: --

[jira] [Commented] (FELIX-4908) X-Forward Header support when running behind a proxy/load balancer

[ https://issues.apache.org/jira/browse/FELIX-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584357#comment-14584357 ] Martin Petrovsky commented on FELIX-4908: - I wonder if there is 4th option. Jetty

[jira] [Commented] (FELIX-4881) DOAP needs to provide value for implements/Standard

[ https://issues.apache.org/jira/browse/FELIX-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584312#comment-14584312 ] Sebb commented on FELIX-4881: - Can someone fix this please? It's a trivial edit. > DOAP needs

[jira] [Commented] (FELIX-4926) Investigate rewriting the resolver algorithm to use loops instead of recursion

[ https://issues.apache.org/jira/browse/FELIX-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14584198#comment-14584198 ] Guillaume Nodet commented on FELIX-4926: The original problem for the preparation

[jira] [Updated] (FELIX-4926) Investigate rewriting the resolver algorithm to use loops instead of recursion

[ https://issues.apache.org/jira/browse/FELIX-4926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet updated FELIX-4926: --- Description: The resolver algorithm for {{Candidates#populate}} currently uses a recursive al

[jira] [Resolved] (FELIX-4927) Felix reports itself as an OSGi R4/R5 Framework

[ https://issues.apache.org/jira/browse/FELIX-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert resolved FELIX-4927. - Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revision&revision=1685172 >

[jira] [Updated] (FELIX-4927) Felix reports itself as an OSGi R4/R5 Framework

[ https://issues.apache.org/jira/browse/FELIX-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert updated FELIX-4927: Summary: Felix reports itself as an OSGi R4/R5 Framework (was: Felix reports itself as an O

[jira] [Assigned] (FELIX-4927) Felix reports itself as an OSGi R5 Framework

[ https://issues.apache.org/jira/browse/FELIX-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert reassigned FELIX-4927: --- Assignee: David Bosschaert > Felix reports itself as an OSGi R5 Framework > -

[jira] [Work started] (FELIX-4927) Felix reports itself as an OSGi R5 Framework

[ https://issues.apache.org/jira/browse/FELIX-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-4927 started by David Bosschaert. --- > Felix reports itself as an OSGi R5 Framework > --

[jira] [Created] (FELIX-4927) Felix reports itself as an OSGi R5 Framework

David Bosschaert created FELIX-4927: --- Summary: Felix reports itself as an OSGi R5 Framework Key: FELIX-4927 URL: https://issues.apache.org/jira/browse/FELIX-4927 Project: Felix Issue Type:

Re: Bug fix release for resolver / framework

I think Guillaume has since committed this fix. See https://issues.apache.org/jira/browse/FELIX-4914 David On 12 June 2015 at 17:30, Jean-Baptiste Onofré wrote: > That would be great. AFAIR, Guillaume has to commit a fix on the resolver. > > @Guillaume, is it correct ? > > Regards > JB > > > On

[jira] [Commented] (FELIX-3712) FileInstall throws Interrupted exception when refreshed

[ https://issues.apache.org/jira/browse/FELIX-3712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583940#comment-14583940 ] Raymond Augé commented on FELIX-3712: - FYI, this issue can be avoided in Equinox by se

[jira] [Commented] (FELIX-4925) Request path is not decoded

[ https://issues.apache.org/jira/browse/FELIX-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583734#comment-14583734 ] J.W. Janssen commented on FELIX-4925: - [~cziegeler]: returning the servletPath + pathI

Re: Bug fix release for resolver / framework

That would be great. AFAIR, Guillaume has to commit a fix on the resolver. @Guillaume, is it correct ? Regards JB On 06/12/2015 06:24 PM, Karl Pauls wrote: ok - I can do the release over the weekend. regards, Karl On Friday, June 12, 2015, David Bosschaert wrote: Would be great to see a

Re: Bug fix release for resolver / framework

ok - I can do the release over the weekend. regards, Karl On Friday, June 12, 2015, David Bosschaert wrote: > Would be great to see a Framework release. A lot of improvements went > in recently. > > +1 from me. > > David > > On 12 June 2015 at 16:28, Jean-Baptiste Onofré > wrote: > > Big +1 f

Re: Bug fix release for resolver / framework

Would be great to see a Framework release. A lot of improvements went in recently. +1 from me. David On 12 June 2015 at 16:28, Jean-Baptiste Onofré wrote: > Big +1 from my side !!! ;) > > Regards > JB > > > On 06/12/2015 05:26 PM, Guillaume Nodet wrote: >> >> Can we start a bug fix release of t

Re: Bug fix release for resolver / framework

Big +1 from my side !!! ;) Regards JB On 06/12/2015 05:26 PM, Guillaume Nodet wrote: Can we start a bug fix release of the framework / resolver ? Here is a list of fixed issues: [FELIX-4914] Resolution problem with fragments and identity requirements [FELIX-4897] Make sure fragment dynamic

Bug fix release for resolver / framework

Can we start a bug fix release of the framework / resolver ? Here is a list of fixed issues: [FELIX-4914] Resolution problem with fragments and identity requirements [FELIX-4897] Make sure fragment dynamic candidates are properly inserted into the candidates list FELIX-4866 Improve Service Reg

[jira] [Commented] (FELIX-4925) Request path is not decoded

[ https://issues.apache.org/jira/browse/FELIX-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583556#comment-14583556 ] Carsten Ziegeler commented on FELIX-4925: - Looking at this, simply using servletPa

[jira] [Commented] (FELIX-4914) Resolution problem with identity requirements on fragments

[ https://issues.apache.org/jira/browse/FELIX-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583550#comment-14583550 ] Guillaume Nodet commented on FELIX-4914: Committed r1685090 Committed r1685100 >

[jira] [Commented] (FELIX-4914) Resolution problem with identity requirements on fragments

[ https://issues.apache.org/jira/browse/FELIX-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583544#comment-14583544 ] Guillaume Nodet commented on FELIX-4914: Yeah, of course, sorry about that. It see

[jira] [Created] (FELIX-4926) Investigate rewriting the resolver algorithm to use loops instead of recursion

Guillaume Nodet created FELIX-4926: -- Summary: Investigate rewriting the resolver algorithm to use loops instead of recursion Key: FELIX-4926 URL: https://issues.apache.org/jira/browse/FELIX-4926 Pro

[jira] [Commented] (FELIX-4914) Resolution problem with identity requirements on fragments

[ https://issues.apache.org/jira/browse/FELIX-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583529#comment-14583529 ] David Bosschaert commented on FELIX-4914: - [~gnt] That commit only contains test c

[jira] [Resolved] (FELIX-4914) Resolution problem with identity requirements on fragments

[ https://issues.apache.org/jira/browse/FELIX-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved FELIX-4914. Resolution: Fixed Fix Version/s: resolver-1.4.0 framework-5.0.1 Co

[jira] [Commented] (FELIX-4925) Request path is not decoded

[ https://issues.apache.org/jira/browse/FELIX-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583387#comment-14583387 ] Carsten Ziegeler commented on FELIX-4925: - Previous versions of the http service d

[jira] [Comment Edited] (FELIX-4925) Request path is not decoded

[ https://issues.apache.org/jira/browse/FELIX-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583318#comment-14583318 ] Carsten Ziegeler edited comment on FELIX-4925 at 6/12/15 12:54 PM: -

[jira] [Reopened] (FELIX-4925) Request path is not decoded

[ https://issues.apache.org/jira/browse/FELIX-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reopened FELIX-4925: - > Request path is not decoded > --- > > Key: FELIX-492

[jira] [Resolved] (FELIX-4925) Request path is not decoded

[ https://issues.apache.org/jira/browse/FELIX-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved FELIX-4925. - Resolution: Fixed Fixed in rev 1685074 > Request path is not decoded > --

[jira] [Created] (FELIX-4925) Request path is not decoded

Carsten Ziegeler created FELIX-4925: --- Summary: Request path is not decoded Key: FELIX-4925 URL: https://issues.apache.org/jira/browse/FELIX-4925 Project: Felix Issue Type: Bug Com

[jira] [Resolved] (FELIX-4919) Enable not escaping property values as Metatype default values

[ https://issues.apache.org/jira/browse/FELIX-4919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fryderyk Wysocki resolved FELIX-4919. - Resolution: Fixed Fix Version/s: maven-scr-plugin 1.21.0 [~cziegeler] I've updated

[jira] [Created] (FELIX-4924) ConfigAdmin update results in empty file or corrupt file.

Neil Wightman created FELIX-4924: Summary: ConfigAdmin update results in empty file or corrupt file. Key: FELIX-4924 URL: https://issues.apache.org/jira/browse/FELIX-4924 Project: Felix Issue

[jira] [Created] (FELIX-4923) SslFilterResponse doesn 't take in account ssl-forward.header property

Antonio Sanso created FELIX-4923: Summary: SslFilterResponse doesn 't take in account ssl-forward.header property Key: FELIX-4923 URL: https://issues.apache.org/jira/browse/FELIX-4923 Project: Felix

[jira] [Commented] (FELIX-4908) X-Forward Header support when running behind a proxy/load balancer

[ https://issues.apache.org/jira/browse/FELIX-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583158#comment-14583158 ] Antonio Sanso commented on FELIX-4908: -- [~cziegeler] right, hence we might go with a)

[jira] [Updated] (FELIX-4922) Simplify DM changelog management

[ https://issues.apache.org/jira/browse/FELIX-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre De Rop updated FELIX-4922: - Description: Currently, each DM sub module has its own changelog. but it's hard to maintain. Inst

[jira] [Commented] (FELIX-4908) X-Forward Header support when running behind a proxy/load balancer

[ https://issues.apache.org/jira/browse/FELIX-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583123#comment-14583123 ] Carsten Ziegeler commented on FELIX-4908: - For sure we can't rename the symbolic n

[jira] [Commented] (FELIX-4908) X-Forward Header support when running behind a proxy/load balancer

[ https://issues.apache.org/jira/browse/FELIX-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583101#comment-14583101 ] Antonio Sanso commented on FELIX-4908: -- [~cziegeler] is similar on what they would do

[jira] [Commented] (FELIX-4908) X-Forward Header support when running behind a proxy/load balancer

[ https://issues.apache.org/jira/browse/FELIX-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583098#comment-14583098 ] Carsten Ziegeler commented on FELIX-4908: - Right, but isn't it similar :) and inst

[jira] [Commented] (FELIX-4908) X-Forward Header support when running behind a proxy/load balancer

[ https://issues.apache.org/jira/browse/FELIX-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583086#comment-14583086 ] Antonio Sanso commented on FELIX-4908: -- [~cziegeler] actually not it can stand in

[jira] [Commented] (FELIX-4908) X-Forward Header support when running behind a proxy/load balancer

[ https://issues.apache.org/jira/browse/FELIX-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583080#comment-14583080 ] Carsten Ziegeler commented on FELIX-4908: - [~asanso] I assume this would be part o

[jira] [Commented] (FELIX-4908) X-Forward Header support when running behind a proxy/load balancer

[ https://issues.apache.org/jira/browse/FELIX-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14583078#comment-14583078 ] Antonio Sanso commented on FELIX-4908: -- [~fmeschbe] [~cziegeler] it makes a lot of se