[jira] [Updated] (FELIX-6173) Enhance log message for events

2019-08-22 Thread Carsten Ziegeler (Jira)


 [ 
https://issues.apache.org/jira/browse/FELIX-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler updated FELIX-6173:

Fix Version/s: (was: log-1.2.2)

> Enhance log message for events
> --
>
> Key: FELIX-6173
> URL: https://issues.apache.org/jira/browse/FELIX-6173
> Project: Felix
>  Issue Type: Improvement
>  Components: Log Service
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>Priority: Major
>
> When a framework, bundle or service event is received, the logger name is 
> currently hard-coded. We could improve the logging by using the bundle 
> symbolic name instead.
> In addition for start level events it would be nice to also log the start 
> level



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Resolved] (FELIX-6173) Enhance log message for events

2019-08-22 Thread Carsten Ziegeler (Jira)


 [ 
https://issues.apache.org/jira/browse/FELIX-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler resolved FELIX-6173.
-
Resolution: Invalid

Reverted in rev 1865690.

> Enhance log message for events
> --
>
> Key: FELIX-6173
> URL: https://issues.apache.org/jira/browse/FELIX-6173
> Project: Felix
>  Issue Type: Improvement
>  Components: Log Service
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>Priority: Major
>
> When a framework, bundle or service event is received, the logger name is 
> currently hard-coded. We could improve the logging by using the bundle 
> symbolic name instead.
> In addition for start level events it would be nice to also log the start 
> level



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


Re: [VOTE] Release Felix Converter 1.0.10

2019-08-22 Thread Raymond Auge
+1

- Ray

On Thu, Aug 22, 2019 at 10:09 AM Carsten Ziegeler 
wrote:

> +1
>
> Am 22.08.2019 um 04:22 schrieb dav...@apache.org:
> > I would like to call a vote on the Apache Felix Converter 1.0.10
> >
> > The following issues were fixed:
> > https://issues.apache.org/jira/browse/FELIX/fixforversion/12345401
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1315/
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1315 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This majority vote is open for at least 72 hours.
> >
> > Best regards,
> >
> > David Bosschaert
> >
>
> --
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)


Re: [VOTE] Release Apache Felix Webconsole 4.3.16

2019-08-22 Thread Raymond Auge
+1

- Ray

On Thu, Aug 22, 2019 at 2:47 AM Karl Pauls  wrote:

> +1
>
> regards,
>
> Karl
>
> On Thu, Aug 22, 2019 at 8:37 AM Jean-Baptiste Onofré 
> wrote:
> >
> > +1 (binding)
> >
> > Regards
> > JB
> >
> > On 20/08/2019 13:10, dav...@apache.org wrote:
> > > I would like to call a vote on the Apache Felix Webconsole 4.3.16
> > >
> > > The recent release 4.3.14 introduced a potential 'already registered'
> > > servlet exception.
> > >
> > > The following issue was fixed:
> > > https://issues.apache.org/jira/projects/FELIX/versions/12346022
> > >
> > > Staging repositories:
> > >
> https://repository.apache.org/content/repositories/orgapachefelix-1314/
> > >
> > > You can use this UNIX script to download the release and verify the
> > > signatures:
> > > http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
> > >
> > > Usage:
> > > sh check_staged_release.sh 1314 /tmp/felix-staging
> > >
> > > Please vote to approve this release:
> > >
> > > [ ] +1 Approve the release
> > > [ ] -1 Veto the release (please provide specific comments)
> > >
> > > This majority vote is open for at least 72 hours.
> > >
> > > Best regards,
> > >
> > > David Bosschaert
> > >
> >
> > --
> > Jean-Baptiste Onofré
> > jbono...@apache.org
> > http://blog.nanthrax.net
> > Talend - http://www.talend.com
>
>
>
> --
> Karl Pauls
> karlpa...@gmail.com
>


-- 
*Raymond Augé* 
 (@rotty3000)
Senior Software Architect *Liferay, Inc.* 
 (@Liferay)


Re: [VOTE] Release Felix Converter 1.0.10

2019-08-22 Thread Carsten Ziegeler

+1

Am 22.08.2019 um 04:22 schrieb dav...@apache.org:

I would like to call a vote on the Apache Felix Converter 1.0.10

The following issues were fixed:
https://issues.apache.org/jira/browse/FELIX/fixforversion/12345401

Staging repositories:
https://repository.apache.org/content/repositories/orgapachefelix-1315/

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1315 /tmp/felix-staging

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)

This majority vote is open for at least 72 hours.

Best regards,

David Bosschaert



--
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org


[jira] [Closed] (FELIX-6171) Webconsole OsgiManager throws NPE

2019-08-22 Thread Rakesh Kumar (Jira)


 [ 
https://issues.apache.org/jira/browse/FELIX-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh Kumar closed FELIX-6171.
---

v4.3.16 fixed the issue, closing the defect.

> Webconsole OsgiManager throws NPE
> -
>
> Key: FELIX-6171
> URL: https://issues.apache.org/jira/browse/FELIX-6171
> Project: Felix
>  Issue Type: Bug
>  Components: Web Console
>Affects Versions: webconsole-4.3.14
>Reporter: Rakesh Kumar
>Priority: Major
> Fix For: webconsole-4.3.16
>
>
> I am running Felix in bridge mode and registered a servlet using System 
> BundleContext but when I stop the server I get an NPE. It was working with 
> 4.3.12.
> {code:java}
> 2019-08-20 15:18:27.314 [FelixLogListener] ERROR 
> com.adeptj.modules.commons.logging.osgi.Logger - unbindHttpService: Failed 
> unregistering Resources
> java.lang.NullPointerException: null
>   at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager.unregisterHttpService(OsgiManager.java:1015)
>   at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager.updateRegistrationState(OsgiManager.java:411)
>   at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager.unbindHttpService(OsgiManager.java:1007)
>   at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager$HttpServiceTracker.removedService(OsgiManager.java:914)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:969)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:871)
>   at 
> org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:911)
>   at 
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
>   at 
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
>   at 
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
>   at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
>   at org.apache.felix.framework.Felix.access$000(Felix.java:112)
>   at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:434)
>   at 
> org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:170)
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:145)
>   at 
> org.apache.felix.http.base.internal.service.HttpServiceFactory.stop(HttpServiceFactory.java:111)
>   at 
> org.apache.felix.http.base.internal.HttpServiceController.unregister(HttpServiceController.java:135)
>   at 
> org.apache.felix.http.bridge.internal.BridgeActivator$1.destroy(BridgeActivator.java:71)
>   at 
> com.adeptj.runtime.osgi.DispatcherServletWrapper.destroy(DispatcherServletWrapper.java:73)
>   at 
> com.adeptj.runtime.osgi.DispatcherServletTracker.removedService(DispatcherServletTracker.java:83)
>   at 
> com.adeptj.runtime.osgi.DispatcherServletTracker.removedService(DispatcherServletTracker.java:36)
>   at 
> com.adeptj.runtime.osgi.BridgeServiceTracker.removedService(BridgeServiceTracker.java:82)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:969)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:871)
>   at 
> org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
>   at org.osgi.util.tracker.ServiceTracker.close(ServiceTracker.java:380)
>   at 
> com.adeptj.runtime.osgi.ServiceTrackers.closeServiceTracker(ServiceTrackers.java:87)
>   at 
> com.adeptj.runtime.osgi.ServiceTrackers.closeDispatcherServletTracker(ServiceTrackers.java:58)
>   at 
> com.adeptj.runtime.osgi.FrameworkShutdownHandler.contextDestroyed(FrameworkShutdownHandler.java:50)
>   at 
> io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:202)
>   at 
> io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:291)
>   at 
> io.undertow.servlet.core.DeploymentManagerImpl$4.call(DeploymentManagerImpl.java:676)
>   at 
> io.undertow.servlet.core.DeploymentManagerImpl$4.call(DeploymentManagerImpl.java:666)
>   at 
> io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
>   at 
> io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
>   at 
> io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:681)
>   at com.adeptj.runtime.server.Server.stop(Server.java:220)
>   at com.adeptj.runtime.common.ShutdownHook.run(ShutdownHook.java:42)
>  {code}

[jira] [Resolved] (FELIX-6171) Webconsole OsgiManager throws NPE

2019-08-22 Thread Rakesh Kumar (Jira)


 [ 
https://issues.apache.org/jira/browse/FELIX-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rakesh Kumar resolved FELIX-6171.
-
Fix Version/s: webconsole-4.3.16
   Resolution: Fixed

v4.3.16 fixed the issue

> Webconsole OsgiManager throws NPE
> -
>
> Key: FELIX-6171
> URL: https://issues.apache.org/jira/browse/FELIX-6171
> Project: Felix
>  Issue Type: Bug
>  Components: Web Console
>Affects Versions: webconsole-4.3.14
>Reporter: Rakesh Kumar
>Priority: Major
> Fix For: webconsole-4.3.16
>
>
> I am running Felix in bridge mode and registered a servlet using System 
> BundleContext but when I stop the server I get an NPE. It was working with 
> 4.3.12.
> {code:java}
> 2019-08-20 15:18:27.314 [FelixLogListener] ERROR 
> com.adeptj.modules.commons.logging.osgi.Logger - unbindHttpService: Failed 
> unregistering Resources
> java.lang.NullPointerException: null
>   at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager.unregisterHttpService(OsgiManager.java:1015)
>   at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager.updateRegistrationState(OsgiManager.java:411)
>   at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager.unbindHttpService(OsgiManager.java:1007)
>   at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager$HttpServiceTracker.removedService(OsgiManager.java:914)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:969)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:871)
>   at 
> org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:911)
>   at 
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
>   at 
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
>   at 
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
>   at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
>   at org.apache.felix.framework.Felix.access$000(Felix.java:112)
>   at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:434)
>   at 
> org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:170)
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:145)
>   at 
> org.apache.felix.http.base.internal.service.HttpServiceFactory.stop(HttpServiceFactory.java:111)
>   at 
> org.apache.felix.http.base.internal.HttpServiceController.unregister(HttpServiceController.java:135)
>   at 
> org.apache.felix.http.bridge.internal.BridgeActivator$1.destroy(BridgeActivator.java:71)
>   at 
> com.adeptj.runtime.osgi.DispatcherServletWrapper.destroy(DispatcherServletWrapper.java:73)
>   at 
> com.adeptj.runtime.osgi.DispatcherServletTracker.removedService(DispatcherServletTracker.java:83)
>   at 
> com.adeptj.runtime.osgi.DispatcherServletTracker.removedService(DispatcherServletTracker.java:36)
>   at 
> com.adeptj.runtime.osgi.BridgeServiceTracker.removedService(BridgeServiceTracker.java:82)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:969)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:871)
>   at 
> org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
>   at org.osgi.util.tracker.ServiceTracker.close(ServiceTracker.java:380)
>   at 
> com.adeptj.runtime.osgi.ServiceTrackers.closeServiceTracker(ServiceTrackers.java:87)
>   at 
> com.adeptj.runtime.osgi.ServiceTrackers.closeDispatcherServletTracker(ServiceTrackers.java:58)
>   at 
> com.adeptj.runtime.osgi.FrameworkShutdownHandler.contextDestroyed(FrameworkShutdownHandler.java:50)
>   at 
> io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:202)
>   at 
> io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:291)
>   at 
> io.undertow.servlet.core.DeploymentManagerImpl$4.call(DeploymentManagerImpl.java:676)
>   at 
> io.undertow.servlet.core.DeploymentManagerImpl$4.call(DeploymentManagerImpl.java:666)
>   at 
> io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
>   at 
> io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
>   at 
> io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:681)
>   at com.adeptj.runtime.server.Server.stop(Server.java:220)
>   at 

[jira] [Commented] (FELIX-6171) Webconsole OsgiManager throws NPE

2019-08-22 Thread Rakesh Kumar (Jira)


[ 
https://issues.apache.org/jira/browse/FELIX-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16913314#comment-16913314
 ] 

Rakesh Kumar commented on FELIX-6171:
-

just checked with 4.3.17-SNAPSHOT and the issue is fixed. 

> Webconsole OsgiManager throws NPE
> -
>
> Key: FELIX-6171
> URL: https://issues.apache.org/jira/browse/FELIX-6171
> Project: Felix
>  Issue Type: Bug
>  Components: Web Console
>Affects Versions: webconsole-4.3.14
>Reporter: Rakesh Kumar
>Priority: Major
>
> I am running Felix in bridge mode and registered a servlet using System 
> BundleContext but when I stop the server I get an NPE. It was working with 
> 4.3.12.
> {code:java}
> 2019-08-20 15:18:27.314 [FelixLogListener] ERROR 
> com.adeptj.modules.commons.logging.osgi.Logger - unbindHttpService: Failed 
> unregistering Resources
> java.lang.NullPointerException: null
>   at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager.unregisterHttpService(OsgiManager.java:1015)
>   at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager.updateRegistrationState(OsgiManager.java:411)
>   at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager.unbindHttpService(OsgiManager.java:1007)
>   at 
> org.apache.felix.webconsole.internal.servlet.OsgiManager$HttpServiceTracker.removedService(OsgiManager.java:914)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:969)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:871)
>   at 
> org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:911)
>   at 
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
>   at 
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
>   at 
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
>   at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
>   at org.apache.felix.framework.Felix.access$000(Felix.java:112)
>   at org.apache.felix.framework.Felix$1.serviceChanged(Felix.java:434)
>   at 
> org.apache.felix.framework.ServiceRegistry.unregisterService(ServiceRegistry.java:170)
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.unregister(ServiceRegistrationImpl.java:145)
>   at 
> org.apache.felix.http.base.internal.service.HttpServiceFactory.stop(HttpServiceFactory.java:111)
>   at 
> org.apache.felix.http.base.internal.HttpServiceController.unregister(HttpServiceController.java:135)
>   at 
> org.apache.felix.http.bridge.internal.BridgeActivator$1.destroy(BridgeActivator.java:71)
>   at 
> com.adeptj.runtime.osgi.DispatcherServletWrapper.destroy(DispatcherServletWrapper.java:73)
>   at 
> com.adeptj.runtime.osgi.DispatcherServletTracker.removedService(DispatcherServletTracker.java:83)
>   at 
> com.adeptj.runtime.osgi.DispatcherServletTracker.removedService(DispatcherServletTracker.java:36)
>   at 
> com.adeptj.runtime.osgi.BridgeServiceTracker.removedService(BridgeServiceTracker.java:82)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:969)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerRemoved(ServiceTracker.java:871)
>   at 
> org.osgi.util.tracker.AbstractTracked.untrack(AbstractTracked.java:341)
>   at org.osgi.util.tracker.ServiceTracker.close(ServiceTracker.java:380)
>   at 
> com.adeptj.runtime.osgi.ServiceTrackers.closeServiceTracker(ServiceTrackers.java:87)
>   at 
> com.adeptj.runtime.osgi.ServiceTrackers.closeDispatcherServletTracker(ServiceTrackers.java:58)
>   at 
> com.adeptj.runtime.osgi.FrameworkShutdownHandler.contextDestroyed(FrameworkShutdownHandler.java:50)
>   at 
> io.undertow.servlet.core.ApplicationListeners.contextDestroyed(ApplicationListeners.java:202)
>   at 
> io.undertow.servlet.core.DeploymentImpl.destroy(DeploymentImpl.java:291)
>   at 
> io.undertow.servlet.core.DeploymentManagerImpl$4.call(DeploymentManagerImpl.java:676)
>   at 
> io.undertow.servlet.core.DeploymentManagerImpl$4.call(DeploymentManagerImpl.java:666)
>   at 
> io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
>   at 
> io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
>   at 
> io.undertow.servlet.core.DeploymentManagerImpl.undeploy(DeploymentManagerImpl.java:681)
>   at com.adeptj.runtime.server.Server.stop(Server.java:220)
>   at 

Re: [VOTE] Release Felix Converter 1.0.10

2019-08-22 Thread davidb
+1

David

On Thu, 22 Aug 2019 at 12:22,  wrote:

> I would like to call a vote on the Apache Felix Converter 1.0.10
>
> The following issues were fixed:
> https://issues.apache.org/jira/browse/FELIX/fixforversion/12345401
>
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-1315/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1315 /tmp/felix-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> This majority vote is open for at least 72 hours.
>
> Best regards,
>
> David Bosschaert
>


[VOTE] Release Felix Converter 1.0.10

2019-08-22 Thread davidb
I would like to call a vote on the Apache Felix Converter 1.0.10

The following issues were fixed:
https://issues.apache.org/jira/browse/FELIX/fixforversion/12345401

Staging repositories:
https://repository.apache.org/content/repositories/orgapachefelix-1315/

You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1315 /tmp/felix-staging

Please vote to approve this release:

[ ] +1 Approve the release
[ ] -1 Veto the release (please provide specific comments)

This majority vote is open for at least 72 hours.

Best regards,

David Bosschaert


[jira] [Updated] (FELIX-6150) Converter bundle should not embed osgi functions

2019-08-22 Thread David Bosschaert (Jira)


 [ 
https://issues.apache.org/jira/browse/FELIX-6150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Bosschaert updated FELIX-6150:

Fix Version/s: (was: converter-1.0.10)
   converter-1.0.12

> Converter bundle should not embed osgi functions
> 
>
> Key: FELIX-6150
> URL: https://issues.apache.org/jira/browse/FELIX-6150
> Project: Felix
>  Issue Type: Improvement
>  Components: Converter
>Affects Versions: converter-1.0.8
>Reporter: Carsten Ziegeler
>Priority: Major
> Fix For: converter-1.0.12
>
>
> The converter bundle is currently also containing a copy of the OSGi function 
> bundle. While this works exporting a package like functions is not a good 
> idea anyway. It is only a convenience, functions have nothing to do with the 
> converter in itself and that will always back fire in the end. It causes 
> unnecessary version constraints since the order of resolving cannot be 
> controlled. 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


[jira] [Created] (FELIX-6174) org.apache.felix.utils.properties.TypedProperties does not parse arrays correctly

2019-08-22 Thread Mike Rumpf (Jira)
Mike Rumpf created FELIX-6174:
-

 Summary: org.apache.felix.utils.properties.TypedProperties does 
not parse arrays correctly
 Key: FELIX-6174
 URL: https://issues.apache.org/jira/browse/FELIX-6174
 Project: Felix
  Issue Type: Bug
  Components: Utils
Affects Versions: utils-1.10.4
 Environment: Windows 7 / tested with 
org.apache.felix.org.apache.felix.utils_1.11.2.jar
Reporter: Mike Rumpf
 Attachments: TypedPropertiesTest.java

org.apache.felix.utils.properties.TypedProperties does not parse arrays in OSGi 
configurations correctly.

While a single line config with

key=["val1","val2"] works fine

just adding a standard key value pair

key2=val2

has the consequence that the value for "key" is not parsed as an array anymore.

(see attached JUnit test to demonstrate the problem)

 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)


RE: [RESULT] [VOTE] Release Apache Felix Maven Bundle Plugin 4.2.1

2019-08-22 Thread Stefan Seifert
thanks!

>-Original Message-
>From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
>Sent: Thursday, August 22, 2019 8:43 AM
>To: dev@felix.apache.org
>Subject: Re: [RESULT] [VOTE] Release Apache Felix Maven Bundle Plugin 4.2.1
>
>It's done, maven-bundle-plugin 4.2.1 is on dist thanks to Karl:
>
>https://dist.apache.org/repos/dist/release/felix/maven-bundle-plugin-
>4.2.1.jar
>
>Regards
>JB


Re: [VOTE] Release Apache Felix Webconsole 4.3.16

2019-08-22 Thread Karl Pauls
+1

regards,

Karl

On Thu, Aug 22, 2019 at 8:37 AM Jean-Baptiste Onofré  wrote:
>
> +1 (binding)
>
> Regards
> JB
>
> On 20/08/2019 13:10, dav...@apache.org wrote:
> > I would like to call a vote on the Apache Felix Webconsole 4.3.16
> >
> > The recent release 4.3.14 introduced a potential 'already registered'
> > servlet exception.
> >
> > The following issue was fixed:
> > https://issues.apache.org/jira/projects/FELIX/versions/12346022
> >
> > Staging repositories:
> > https://repository.apache.org/content/repositories/orgapachefelix-1314/
> >
> > You can use this UNIX script to download the release and verify the
> > signatures:
> > http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
> >
> > Usage:
> > sh check_staged_release.sh 1314 /tmp/felix-staging
> >
> > Please vote to approve this release:
> >
> > [ ] +1 Approve the release
> > [ ] -1 Veto the release (please provide specific comments)
> >
> > This majority vote is open for at least 72 hours.
> >
> > Best regards,
> >
> > David Bosschaert
> >
>
> --
> Jean-Baptiste Onofré
> jbono...@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com



-- 
Karl Pauls
karlpa...@gmail.com


Re: [RESULT] [VOTE] Release Apache Felix Maven Bundle Plugin 4.2.1

2019-08-22 Thread Jean-Baptiste Onofré
It's done, maven-bundle-plugin 4.2.1 is on dist thanks to Karl:

https://dist.apache.org/repos/dist/release/felix/maven-bundle-plugin-4.2.1.jar

Regards
JB

On 21/08/2019 17:59, Stefan Seifert wrote:
> 
> 
> => @any PMC member: please copy this release to the Felix dist directory
> 
> 
> 
>> -Original Message-
>> From: Stefan Seifert [mailto:sseif...@pro-vision.de]
>> Sent: Tuesday, August 20, 2019 5:53 PM
>> To: dev@felix.apache.org
>> Subject: FW: [RESULT] [VOTE] Release Apache Felix Maven Bundle Plugin 4.2.1
>>
>>
>>
>> => @any PMC member: please copy this release to the Felix dist directory
>>
>>
>>
>>
>> -Original Message-
>> From: Stefan Seifert 
>> Sent: Monday, August 19, 2019 10:02 AM
>> To: dev@felix.apache.org
>> Subject: [RESULT] [VOTE] Release Apache Felix Maven Bundle Plugin 4.2.1
>>
>> Hi,
>>
>> The vote has passed with the following result :
>>
>>  +1 (binding): Carsten Ziegeler, David Bosschaert, Georg Henzler
>>  +1 (non binding): Stefan Seifert, Raymond Auge, Francois Papon
>>
>>
>> => @any PMC member: please copy this release to the Felix dist directory
>>
>>
>> i will take care of the other steps and promote the artifacts to the
>> central Maven repository.
>>
>> stefan
>>
>>
>>
> 
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com


Re: [VOTE] Release Apache Felix Webconsole 4.3.16

2019-08-22 Thread Jean-Baptiste Onofré
+1 (binding)

Regards
JB

On 20/08/2019 13:10, dav...@apache.org wrote:
> I would like to call a vote on the Apache Felix Webconsole 4.3.16
> 
> The recent release 4.3.14 introduced a potential 'already registered'
> servlet exception.
> 
> The following issue was fixed:
> https://issues.apache.org/jira/projects/FELIX/versions/12346022
> 
> Staging repositories:
> https://repository.apache.org/content/repositories/orgapachefelix-1314/
> 
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
> 
> Usage:
> sh check_staged_release.sh 1314 /tmp/felix-staging
> 
> Please vote to approve this release:
> 
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
> 
> This majority vote is open for at least 72 hours.
> 
> Best regards,
> 
> David Bosschaert
> 

-- 
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com


Re: [VOTE] Release Apache Felix Webconsole 4.3.16

2019-08-22 Thread davidb
We need 2 more binding +1s would anyone be interested in casting a vote?

Many thanks!

David

On Tue, 20 Aug 2019 at 12:23,  wrote:

> +1
>
> David
>
> On Tue, 20 Aug 2019 at 12:10,  wrote:
>
>> I would like to call a vote on the Apache Felix Webconsole 4.3.16
>>
>> The recent release 4.3.14 introduced a potential 'already registered'
>> servlet exception.
>>
>> The following issue was fixed:
>> https://issues.apache.org/jira/projects/FELIX/versions/12346022
>>
>> Staging repositories:
>> https://repository.apache.org/content/repositories/orgapachefelix-1314/
>>
>> You can use this UNIX script to download the release and verify the
>> signatures:
>> http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
>>
>> Usage:
>> sh check_staged_release.sh 1314 /tmp/felix-staging
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Veto the release (please provide specific comments)
>>
>> This majority vote is open for at least 72 hours.
>>
>> Best regards,
>>
>> David Bosschaert
>>
>