[
https://issues.apache.org/jira/browse/FELIX-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-4019.
-
Resolution: Fixed
Assignee: Carsten Ziegeler (was: Felix Meschberger)
Fixed in rev
[
https://issues.apache.org/jira/browse/FELIX-5397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-5397.
-
Resolution: Duplicate
Fix Version/s: (was: webconsole-memoryusage-plugin-1.0.8)
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
David Leangen created FELIX-5571:
Summary: Replace JSONParser in Serializer with the new one from
utils
Key: FELIX-5571
URL: https://issues.apache.org/jira/browse/FELIX-5571
Project: Felix
I
+1 (binding)
(DISCLAIMER: not fully tested)
Regards
JB
On 02/27/2017 09:46 PM, Karl Pauls wrote:
I would like to call a vote on a release of a quick fix of the Felix
framework convenience distribution i.e.,
main.distribution 5.6.2-update1
The main change is tracked by FELIX-5569 - in a nutsh
[
https://issues.apache.org/jira/browse/FELIX-5570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886987#comment-15886987
]
David Jencks commented on FELIX-5570:
-
I wonder if the most reliable and simplest fix
Thomas Watson created FELIX-5570:
Summary: Immediate service component that provides a WeavingHook
results in an NPE
Key: FELIX-5570
URL: https://issues.apache.org/jira/browse/FELIX-5570
Project: Feli
[
https://issues.apache.org/jira/browse/FELIX-5558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886637#comment-15886637
]
Karl Pauls commented on FELIX-5558:
---
You basically create a bnd file with the packages y
[
https://issues.apache.org/jira/browse/FELIX-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls resolved FELIX-5569.
---
Resolution: Fixed
Assignee: Karl Pauls
The vote for a replacement distribution is on the way and
I would like to call a vote on a release of a quick fix of the Felix
framework convenience distribution i.e.,
main.distribution 5.6.2-update1
The main change is tracked by FELIX-5569 - in a nutshell, we are
missing a bundle in the distribution required by jline to be able to
run on windows out of
[
https://issues.apache.org/jira/browse/FELIX-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated FELIX-5569:
--
Fix Version/s: (was: framework-5.6.4)
Yes, adding the jansi bundle is making things work. Ok - I wil
[
https://issues.apache.org/jira/browse/FELIX-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15886347#comment-15886347
]
Guillaume Nodet commented on FELIX-5569:
It should work with jansi or jna on the c
[
https://issues.apache.org/jira/browse/FELIX-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated FELIX-5569:
--
Affects Version/s: (was: gogo.jline-1.0.0)
framework-5.6.2
Fix Version
Karl Pauls created FELIX-5569:
-
Summary: JLine shell not working on Windows
Key: FELIX-5569
URL: https://issues.apache.org/jira/browse/FELIX-5569
Project: Felix
Issue Type: Bug
Componen
[
https://issues.apache.org/jira/browse/FELIX-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-4984:
Fix Version/s: (was: scr-2.1.0)
> Issues in CircularReferenceTest
>
[
https://issues.apache.org/jira/browse/FELIX-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-4755:
Fix Version/s: (was: scr-2.1.0)
> [DS] avoid churn when changing global extender propert
[
https://issues.apache.org/jira/browse/FELIX-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-4984.
-
Resolution: Won't Fix
assuming this is fixed, if not feel free to reopen
> Issues in Circ
[
https://issues.apache.org/jira/browse/FELIX-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-5559.
-
Resolution: Fixed
Added in rev 1784564
> Add change count property to runtime service
> -
On Mon, Feb 27, 2017 at 1:56 PM, Carsten Ziegeler wrote:
> Karl Pauls wrote
Yeah, something like this sounds like the way to go. I was wondering
if it isn't a possibility to overload the init() method on the system
bundle to optionally accept a logging object of some kind...
>>
Karl Pauls wrote
>>> Yeah, something like this sounds like the way to go. I was wondering
>>> if it isn't a possibility to overload the init() method on the system
>>> bundle to optionally accept a logging object of some kind...
>>>
>> I think that's already too late. You want to have logging start
>> Yeah, something like this sounds like the way to go. I was wondering
>> if it isn't a possibility to overload the init() method on the system
>> bundle to optionally accept a logging object of some kind...
>>
> I think that's already too late. You want to have logging starting with
> the Framewo
Karl Pauls wrote
>>> Shouldn’t we try to get the specification extended to define a well known
>>> property for configuration map handed to the FrameworkFactory.newFramework
>>> method which names some sort of logger ?
>>>
>>> Unfortunately that configuration map is Map so the logger
>>> itself
>> Shouldn’t we try to get the specification extended to define a well known
>> property for configuration map handed to the FrameworkFactory.newFramework
>> method which names some sort of logger ?
>>
>> Unfortunately that configuration map is Map so the logger
>> itself cannot be provided … bu
[
https://issues.apache.org/jira/browse/FELIX-5566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls resolved FELIX-5566.
---
Resolution: Fixed
Fix Version/s: webconsole-4.3.2
I committed support for this in r1784546.
F
Felix Meschberger wrote
> Hi all
>
> Hmm, thinking a bit more about this and looking at the FrameworkFactory class
> which is targeted at launching frameworks in an implementation independent
> manner, I wonder, whether logging being a crucial function in each and every
> application should not
Hi all
Hmm, thinking a bit more about this and looking at the FrameworkFactory class
which is targeted at launching frameworks in an implementation independent
manner, I wonder, whether logging being a crucial function in each and every
application should not get special treatment on a specific
[
https://issues.apache.org/jira/browse/FELIX-5564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885529#comment-15885529
]
David Bosschaert commented on FELIX-5564:
-
It seems like this got fixed betweem 2.
27 matches
Mail list logo
