[jira] [Created] (FELIX-5947) ClassLoader memory leak

Raymond Augé created FELIX-5947: --- Summary: ClassLoader memory leak Key: FELIX-5947 URL: https://issues.apache.org/jira/browse/FELIX-5947 Project: Felix Issue Type: Bug Components: Dec

[jira] [Commented] (FELIX-5947) ClassLoader memory leak

[ https://issues.apache.org/jira/browse/FELIX-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16634253#comment-16634253 ] Raymond Augé commented on FELIX-5947: - See https://issues.liferay.com/browse/LPS-8175

[jira] [Assigned] (FELIX-5947) ClassLoader memory leak

[ https://issues.apache.org/jira/browse/FELIX-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Augé reassigned FELIX-5947: --- Assignee: Raymond Augé > ClassLoader memory leak > --- > >

[jira] [Updated] (FELIX-5947) ClassLoader memory leak

[ https://issues.apache.org/jira/browse/FELIX-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Augé updated FELIX-5947: Fix Version/s: scr-2.1.10 > ClassLoader memory leak > --- > > K

[jira] [Created] (FELIX-5948) Collection of performance and memory optimizations

Raymond Augé created FELIX-5948: --- Summary: Collection of performance and memory optimizations Key: FELIX-5948 URL: https://issues.apache.org/jira/browse/FELIX-5948 Project: Felix Issue Type: Im

[jira] [Work started] (FELIX-5947) ClassLoader memory leak

[ https://issues.apache.org/jira/browse/FELIX-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-5947 started by Raymond Augé. --- > ClassLoader memory leak > --- > > Key: FELIX

[jira] [Updated] (FELIX-5948) Collection of performance and memory optimizations

[ https://issues.apache.org/jira/browse/FELIX-5948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Augé updated FELIX-5948: Description: https://issues.liferay.com/browse/LPS-84286 https://issues.liferay.com/browse/LPS-8444

[jira] [Work started] (FELIX-5948) Collection of performance and memory optimizations

[ https://issues.apache.org/jira/browse/FELIX-5948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on FELIX-5948 started by Raymond Augé. --- > Collection of performance and memory optimizations > ---

[jira] [Resolved] (FELIX-5948) Collection of performance and memory optimizations

[ https://issues.apache.org/jira/browse/FELIX-5948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Augé resolved FELIX-5948. - Resolution: Fixed https://svn.apache.org/repos/asf/felix/trunk@1842516 > Collection of performan

[jira] [Resolved] (FELIX-5947) ClassLoader memory leak

[ https://issues.apache.org/jira/browse/FELIX-5947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raymond Augé resolved FELIX-5947. - Resolution: Fixed https://svn.apache.org/repos/asf/felix/trunk@1842515 > ClassLoader memory leak

Re: Felix Logback with logback >= 1.3.0-alpha4

I'm not sure I can agree with your position on the use of Service Loader Mediator. We, as an OSGi community, have no choice but to make certain accommodations for the development of libraries which are not always going to be used in OSGi but DO want to support it in the least intrusive way. Servic

felix scr release

Hey All, Anyone object to having another release of Felix SCR? I've addressed two more issues making for 3 issues resolved since the last release. Barring any objections I'll start a release Wednesday. -- *Raymond Augé* (@rotty3000) Senior Sof

Re: felix scr release

+1 for releasing Raymond Auge wrote > Hey All, > > Anyone object to having another release of Felix SCR? > > I've addressed two more issues making for 3 issues resolved since the last > release. > > Barring any objections I'll start a release Wednesday. > -- Carsten Ziegeler Adobe Research S

Re: Felix Logback with logback >= 1.3.0-alpha4

On 2018-10-01T12:42:18 -0400 Raymond Auge wrote: > I'm not sure I can agree with your position on the use of Service Loader > Mediator. > > We, as an OSGi community, have no choice but to make certain accommodations > for the development of libraries which are not always going to be used in > OS