[jira] [Commented] (FELIX-6039) Check for "webconsole.configurationFactory.nameHint" property for configuration factories
[
https://issues.apache.org/jira/browse/FELIX-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754131#comment-16754131
]
Carsten Ziegeler commented on FELIX-6039:
-
sure, or you enable strict mode which fails on all warnings
> Check for "webconsole.configurationFactory.nameHint" property for
> configuration factories
> -
>
> Key: FELIX-6039
> URL: https://issues.apache.org/jira/browse/FELIX-6039
> Project: Felix
> Issue Type: Improvement
> Components: Tooling
>Affects Versions: osgicheck-maven-plugin 0.1.0
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: osgicheck-maven-plugin 0.2.0
>
>
> Not only the existence of the property with name
> {{webconsole.configurationFactory.nameHint}} should be enforced
> (http://felix.apache.org/documentation/subprojects/apache-felix-web-console.html#configuration-factories)
> whenever a configuration factory is used, but also the existence of
> referenced properties in the underlying metatype (by checking all
> placeholderrs within that property).
> Compare also with
> https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1728
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FELIX-6039) Check for "webconsole.configurationFactory.nameHint" property for configuration factories
[
https://issues.apache.org/jira/browse/FELIX-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754103#comment-16754103
]
Georg Henzler commented on FELIX-6039:
--
I could be configuration switch in the plugin to either warn or fail - for
platforms that always use the webconsole (like for the use case
https://github.com/Adobe-Consulting-Services/acs-aem-commons) it would be
beneficiary to fail early/hard.
> Check for "webconsole.configurationFactory.nameHint" property for
> configuration factories
> -
>
> Key: FELIX-6039
> URL: https://issues.apache.org/jira/browse/FELIX-6039
> Project: Felix
> Issue Type: Improvement
> Components: Tooling
>Affects Versions: osgicheck-maven-plugin 0.1.0
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: osgicheck-maven-plugin 0.2.0
>
>
> Not only the existence of the property with name
> {{webconsole.configurationFactory.nameHint}} should be enforced
> (http://felix.apache.org/documentation/subprojects/apache-felix-web-console.html#configuration-factories)
> whenever a configuration factory is used, but also the existence of
> referenced properties in the underlying metatype (by checking all
> placeholderrs within that property).
> Compare also with
> https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1728
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (FELIX-6040) Felix Web Console: Configuration Manager does only expose OCD name which does not allow to disambiguate multiple designates pointing to the same OCD
Konrad Windszus created FELIX-6040:
--
Summary: Felix Web Console: Configuration Manager does only expose
OCD name which does not allow to disambiguate multiple designates pointing to
the same OCD
Key: FELIX-6040
URL: https://issues.apache.org/jira/browse/FELIX-6040
Project: Felix
Issue Type: Improvement
Components: Web Console
Affects Versions: webconsole-4.3.8
Reporter: Konrad Windszus
If one metatype OCD is referred to by multiple designates, all of those appear
with the OCD's name only below {{/system/console/configMgr}}. So you cannot
distinguish between those in the web UI. Compare also with
https://mail.osgi.org/pipermail/osgi-dev/2019-January/007382.html.
In this case it would be good to also include the factory PID of the designate
element in it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FELIX-6039) Check for "webconsole.configurationFactory.nameHint" property for configuration factories
[
https://issues.apache.org/jira/browse/FELIX-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754077#comment-16754077
]
Carsten Ziegeler commented on FELIX-6039:
-
lgtm, I think this should generate a warning - not everyone is using the
webconsole
> Check for "webconsole.configurationFactory.nameHint" property for
> configuration factories
> -
>
> Key: FELIX-6039
> URL: https://issues.apache.org/jira/browse/FELIX-6039
> Project: Felix
> Issue Type: Improvement
> Components: Tooling
>Affects Versions: osgicheck-maven-plugin 0.1.0
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: osgicheck-maven-plugin 0.2.0
>
>
> Not only the existence of the property with name
> {{webconsole.configurationFactory.nameHint}} should be enforced
> (http://felix.apache.org/documentation/subprojects/apache-felix-web-console.html#configuration-factories)
> whenever a configuration factory is used, but also the existence of
> referenced properties in the underlying metatype (by checking all
> placeholderrs within that property).
> Compare also with
> https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1728
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] felix pull request #173: Delegate timezone and date format properties to Jet...
GitHub user ponziani opened a pull request: https://github.com/apache/felix/pull/173 Delegate timezone and date format properties to Jetty When using Felix-Jetty we need to be able to configure the timezone and date format used in the request logging. This Pull request enables these options. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ponziani/felix trunk Alternatively you can review and apply these changes as the patch at: https://github.com/apache/felix/pull/173.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #173 commit 5076676c6a15ed27aa864f220699b77a02277063 Author: HUYPENS Steven Date: 2019-01-28T15:27:43Z Delegate timezone and dateformat properties to Jetty ---
Re: [VOTE] Apache Felix Framework 6.0.2 and related subproject releases
+1 (binding) Quickly tested on incoming Karaf 4.3.0 R7 branch. So far so good ! Thanks a lot ! Regards JB On 28/01/2019 15:29, Karl Pauls wrote: > I would like to call a vote on the following subproject releases: > > framework 6.0.2 > main 6.0.2 > main.distribution 6.0.2 > > The main changelogs are in jira and at: > https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.framework-6.0.2/doc/changelog.txt > > Staging repositories: > https://repository.apache.org/content/repositories/orgapachefelix-1280/ > > 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 1280 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: [VOTE] Apache Felix Framework 6.0.2 and related subproject releases
+1 Karl Pauls wrote I would like to call a vote on the following subproject releases: framework 6.0.2 main 6.0.2 main.distribution 6.0.2 The main changelogs are in jira and at: https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.framework-6.0.2/doc/changelog.txt Staging repositories: https://repository.apache.org/content/repositories/orgapachefelix-1280/ 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 1280 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
[jira] [Updated] (FELIX-6039) Check for "webconsole.configurationFactory.nameHint" property for configuration factories
[
https://issues.apache.org/jira/browse/FELIX-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated FELIX-6039:
---
Fix Version/s: osgicheck-maven-plugin 0.2.0
> Check for "webconsole.configurationFactory.nameHint" property for
> configuration factories
> -
>
> Key: FELIX-6039
> URL: https://issues.apache.org/jira/browse/FELIX-6039
> Project: Felix
> Issue Type: Improvement
> Components: Tooling
>Affects Versions: osgicheck-maven-plugin 0.1.0
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: osgicheck-maven-plugin 0.2.0
>
>
> Not only the existence of the property with name
> {{webconsole.configurationFactory.nameHint}} should be enforced
> (http://felix.apache.org/documentation/subprojects/apache-felix-web-console.html#configuration-factories)
> whenever a configuration factory is used, but also the existence of
> referenced properties in the underlying metatype (by checking all
> placeholderrs within that property).
> Compare also with
> https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1728
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: [VOTE] Apache Felix Framework 6.0.2 and related subproject releases
Grumpf thanks - fixed in trunk! regards, Karl On Mon, Jan 28, 2019 at 3:32 PM David Bosschaert wrote: > > +1 > > Thanks Karl! > > BTW the changelog states: > > Changes from 6.0.1 to 6.0.1 > I guess you mean 6.0.1 to 6.0.2 :) > > Best regards, > > David > > > > On Mon, 28 Jan 2019 at 14:29, Karl Pauls wrote: > > > I would like to call a vote on the following subproject releases: > > > > framework 6.0.2 > > main 6.0.2 > > main.distribution 6.0.2 > > > > The main changelogs are in jira and at: > > > > https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.framework-6.0.2/doc/changelog.txt > > > > Staging repositories: > > https://repository.apache.org/content/repositories/orgapachefelix-1280/ > > > > 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 1280 /tmp/felix-staging > > > > Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] -1 Veto the release (please provide specific comments) > > -- Karl Pauls karlpa...@gmail.com
[jira] [Created] (FELIX-6039) Check for "webconsole.configurationFactory.nameHint" property for configuration factories
Konrad Windszus created FELIX-6039:
--
Summary: Check for "webconsole.configurationFactory.nameHint"
property for configuration factories
Key: FELIX-6039
URL: https://issues.apache.org/jira/browse/FELIX-6039
Project: Felix
Issue Type: Improvement
Components: Tooling
Affects Versions: osgicheck-maven-plugin 0.1.0
Reporter: Konrad Windszus
Not only the existence of the property with name
{{webconsole.configurationFactory.nameHint}} should be enforced
(http://felix.apache.org/documentation/subprojects/apache-felix-web-console.html#configuration-factories)
whenever a configuration factory is used, but also the existence of referenced
properties in the underlying metatype (by checking all placeholderrs within
that property).
Compare also with
https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1728
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FELIX-6039) Check for "webconsole.configurationFactory.nameHint" property for configuration factories
[
https://issues.apache.org/jira/browse/FELIX-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16754053#comment-16754053
]
Konrad Windszus commented on FELIX-6039:
[~cziegeler] WDYT?
> Check for "webconsole.configurationFactory.nameHint" property for
> configuration factories
> -
>
> Key: FELIX-6039
> URL: https://issues.apache.org/jira/browse/FELIX-6039
> Project: Felix
> Issue Type: Improvement
> Components: Tooling
>Affects Versions: osgicheck-maven-plugin 0.1.0
>Reporter: Konrad Windszus
>Priority: Major
>
> Not only the existence of the property with name
> {{webconsole.configurationFactory.nameHint}} should be enforced
> (http://felix.apache.org/documentation/subprojects/apache-felix-web-console.html#configuration-factories)
> whenever a configuration factory is used, but also the existence of
> referenced properties in the underlying metatype (by checking all
> placeholderrs within that property).
> Compare also with
> https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues/1728
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: [VOTE] Apache Felix Framework 6.0.2 and related subproject releases
+1 Thanks Karl! BTW the changelog states: > Changes from 6.0.1 to 6.0.1 I guess you mean 6.0.1 to 6.0.2 :) Best regards, David On Mon, 28 Jan 2019 at 14:29, Karl Pauls wrote: > I would like to call a vote on the following subproject releases: > > framework 6.0.2 > main 6.0.2 > main.distribution 6.0.2 > > The main changelogs are in jira and at: > > https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.framework-6.0.2/doc/changelog.txt > > Staging repositories: > https://repository.apache.org/content/repositories/orgapachefelix-1280/ > > 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 1280 /tmp/felix-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) >
[VOTE] Apache Felix Framework 6.0.2 and related subproject releases
I would like to call a vote on the following subproject releases: framework 6.0.2 main 6.0.2 main.distribution 6.0.2 The main changelogs are in jira and at: https://svn.apache.org/repos/asf/felix/releases/org.apache.felix.framework-6.0.2/doc/changelog.txt Staging repositories: https://repository.apache.org/content/repositories/orgapachefelix-1280/ 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 1280 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments)
[RESULT][VOTE] Release Apache Felix Gogo JLine 1.1.4
Hi all, this vote passed with the following result: +1 (binding): David Bosschaert, Jean-Baptiste Onofré, Pierre De Rop, Karl Pauls, Raymond Auge +1 (non binding): Christian Schneider, François Papon Thanks all for your vote ! I'm uploading release to dist.apache.org, update Jira and promote artifacts to Central. Thanks again ! Regards JB On 25/01/2019 13:55, Jean-Baptiste Onofré wrote: > Hi all, > > We solved 3 issues in this release (release notes): > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12344851 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-1278/ > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > This vote will be open for 72 hours. > > Thanks, > Regards > JB > -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: [VOTE] Release Apache Felix Gogo JLine 1.1.4
+1 - Ray On Mon, Jan 28, 2019, 04:41 Karl Pauls +1 > > regards, > > Karl > > On Monday, January 28, 2019, Pierre De Rop wrote: > > > +1 > > > > thanks Jean-Batiste > > > > regards > > Pierre > > > > On Mon, Jan 28, 2019 at 9:44 AM Jean-Baptiste Onofré > > wrote: > > > > > +1 (binding) > > > > > > Regards > > > JB > > > > > > On 25/01/2019 13:55, Jean-Baptiste Onofré wrote: > > > > Hi all, > > > > > > > > We solved 3 issues in this release (release notes): > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > projectId=12310100=12344851 > > > > > > > > Staging repository: > > > > https://repository.apache.org/content/repositories/ > > orgapachefelix-1278/ > > > > > > > > Please vote to approve this release: > > > > > > > > [ ] +1 Approve the release > > > > [ ] -1 Veto the release (please provide specific comments) > > > > > > > > This vote will be open for 72 hours. > > > > > > > > Thanks, > > > > Regards > > > > JB > > > > > > > > > > -- > > > Jean-Baptiste Onofré > > > jbono...@apache.org > > > http://blog.nanthrax.net > > > Talend - http://www.talend.com > > > > > > > > -- > Karl Pauls > karlpa...@gmail.com >
[jira] [Updated] (FELIX-5978) Felix framework unable to retrieve custom URL handlers when security is on
[
https://issues.apache.org/jira/browse/FELIX-5978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated FELIX-5978:
--
Component/s: Framework
> Felix framework unable to retrieve custom URL handlers when security is on
> --
>
> Key: FELIX-5978
> URL: https://issues.apache.org/jira/browse/FELIX-5978
> Project: Felix
> Issue Type: Bug
> Components: Framework
>Affects Versions: framework-6.0.0, framework-6.0.1
>Reporter: Timothy Ward
>Assignee: Karl Pauls
>Priority: Critical
> Fix For: framework-6.0.2
>
>
> When running with multiple frameworks in the same VM, custom URL Handlers,
> and OSGi security on there are a couple of problems:
>
> Firstly, this security exception results in the custom URL handler being
> ignored. The framework should really be using a doPriv here.
> {code:java}
> java.security.AccessControlException: access denied
> ("java.lang.RuntimePermission" "getClassLoader")
> at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
> at java.security.AccessController.checkPermission(AccessController.java:884)
> at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> at java.lang.ClassLoader.checkClassLoaderPermission(ClassLoader.java:1528)
> at java.lang.Class.getClassLoader(Class.java:683)
> at
> org.apache.felix.framework.URLHandlers.getFrameworkFromContext(URLHandlers.java:690)
> at
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.getStreamHandlerService(URLHandlersStreamHandlerProxy.java:574)
> at
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.toExternalForm(URLHandlersStreamHandlerProxy.java:474)
> at java.net.URL.toExternalForm(URL.java:929)
> at java.net.URL.toString(URL.java:915)
> at java.lang.ClassLoader.defineClassSourceLocation(ClassLoader.java:678)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:762)
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.defineClass(BundleWiringImpl.java:2344)
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.defineClassParallel(BundleWiringImpl.java:2162)
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.findClass(BundleWiringImpl.java:2096)
> at
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1565)
> at
> org.apache.felix.framework.BundleWiringImpl.access$300(BundleWiringImpl.java:79)
> at
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1982)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at
> org.apache.felix.cm.impl.ConfigurationManager.configure(ConfigurationManager.java:758)
> {code}
> Secondly, the wrong framework is returned some of the time due to the logic
> of URLHandlers.getFrameworkContext() - in this method it assumes that there
> will be a bundle class loader on the stack, which is not true when the
> launcher is starting a bundle (the framework reflectively loads the Activator
> type which requires a URL check to set the security domain).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FELIX-5830) Document changes for Felix Framework
[ https://issues.apache.org/jira/browse/FELIX-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated FELIX-5830: -- Fix Version/s: (was: framework-6.0.2) > Document changes for Felix Framework > > > Key: FELIX-5830 > URL: https://issues.apache.org/jira/browse/FELIX-5830 > Project: Felix > Issue Type: Task > Components: Framework >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: framework-6.0.3 > > > There have been some changes that need documentation. This is the umbrella > issue to keep track of them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FELIX-5878) Implement resolve timeout
[ https://issues.apache.org/jira/browse/FELIX-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated FELIX-5878: -- Fix Version/s: (was: framework-6.0.2) > Implement resolve timeout > - > > Key: FELIX-5878 > URL: https://issues.apache.org/jira/browse/FELIX-5878 > Project: Felix > Issue Type: Improvement > Components: Framework >Affects Versions: framework-5.6.10, framework-6.0.0 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: framework-6.0.3 > > > We should implement a resolve timeout to make sure we don't attempt to > resolve forever. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
RE: [RESULT] [VOTE] Release Apache Felix Bnd SCR Plugin 1.9.2
thanks - i've completed the remaining steps. stefan >-Original Message- >From: Karl Pauls [mailto:karlpa...@gmail.com] >Sent: Monday, January 28, 2019 1:41 PM >To: dev@felix.apache.org >Subject: Re: [RESULT] [VOTE] Release Apache Felix Bnd SCR Plugin 1.9.2 > >Done. > >regards, > >Karl > >On Mon, Jan 28, 2019 at 1:04 PM Stefan Seifert >wrote: >> >> @any PMC member: please copy this release to the Felix dist directory! >> >> stefan >> >> >-Original Message- >> >From: Stefan Seifert [mailto:sseif...@pro-vision.de] >> >Sent: Saturday, January 26, 2019 12:04 PM >> >To: dev@felix.apache.org >> >Subject: [RESULT] [VOTE] Release Apache Felix Bnd SCR Plugin 1.9.2 >> > >> >Hi, >> > >> >The vote has passed with the following result : >> > >> > +1 (binding): Pierre De Rop, Carsten Ziegeler, Raymond Auge, Jean- >> >Baptiste Onofré >> > +1 (non binding): Stefan Seifert, Francois Papon >> > >> > >> >=> @any PMC member: please copy this release to the Felix dist >directory! >> > >> > >> >i will then promote the artifacts to the central Maven repository and >> >update the felix site. >> > >> >stefan >> > >> >> > > >-- >Karl Pauls >karlpa...@gmail.com
[jira] [Updated] (FELIX-5975) URLHandlersStreamHandlerProxy - OPEN_CONNECTION_PROXY null
[
https://issues.apache.org/jira/browse/FELIX-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated FELIX-5975:
--
Fix Version/s: (was: framework-6.0.2)
> URLHandlersStreamHandlerProxy - OPEN_CONNECTION_PROXY null
> --
>
> Key: FELIX-5975
> URL: https://issues.apache.org/jira/browse/FELIX-5975
> Project: Felix
> Issue Type: Bug
> Components: Framework
>Affects Versions: framework-4.6.1
> Environment: AIX server box, Tomcat 8.0.53
>Reporter: Julien Jalageas
>Assignee: Karl Pauls
>Priority: Blocker
> Fix For: framework-6.0.3
>
> Attachments: stacktrace.txt
>
>
> Hi,
> I am running into a blocking issue since I've upgraded from Tomcat 7.0.73 to
> Tomcat 8.0.53, SOAP based web services are failing with the following error:
> java.lang.IllegalStateException: *Stream handler unavailable due to: null*
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.openConnection(URLHandlersStreamHandlerProxy.java:359)
> Using a remote debugger, I was able to find that the real exception is
> actually a Null Pointer Exception thrown from
> *URLHandlersStreamHandlerProxy*.java, line 351:
> return (URLConnection) *OPEN_CONNECTION_PROXY*.invoke(svc, new Object[]\{url,
> proxy});
> where *OPEN_CONNECTION_PROXY* is null (I've attached the full stacktrace).
> Is there a fix available?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Re: [RESULT] [VOTE] Release Apache Felix Bnd SCR Plugin 1.9.2
Done. regards, Karl On Mon, Jan 28, 2019 at 1:04 PM Stefan Seifert wrote: > > @any PMC member: please copy this release to the Felix dist directory! > > stefan > > >-Original Message- > >From: Stefan Seifert [mailto:sseif...@pro-vision.de] > >Sent: Saturday, January 26, 2019 12:04 PM > >To: dev@felix.apache.org > >Subject: [RESULT] [VOTE] Release Apache Felix Bnd SCR Plugin 1.9.2 > > > >Hi, > > > >The vote has passed with the following result : > > > > +1 (binding): Pierre De Rop, Carsten Ziegeler, Raymond Auge, Jean- > >Baptiste Onofré > > +1 (non binding): Stefan Seifert, Francois Papon > > > > > >=> @any PMC member: please copy this release to the Felix dist directory! > > > > > >i will then promote the artifacts to the central Maven repository and > >update the felix site. > > > >stefan > > > > -- Karl Pauls karlpa...@gmail.com
RE: [RESULT] [VOTE] Release Apache Felix Bnd SCR Plugin 1.9.2
@any PMC member: please copy this release to the Felix dist directory! stefan >-Original Message- >From: Stefan Seifert [mailto:sseif...@pro-vision.de] >Sent: Saturday, January 26, 2019 12:04 PM >To: dev@felix.apache.org >Subject: [RESULT] [VOTE] Release Apache Felix Bnd SCR Plugin 1.9.2 > >Hi, > >The vote has passed with the following result : > > +1 (binding): Pierre De Rop, Carsten Ziegeler, Raymond Auge, Jean- >Baptiste Onofré > +1 (non binding): Stefan Seifert, Francois Papon > > >=> @any PMC member: please copy this release to the Felix dist directory! > > >i will then promote the artifacts to the central Maven repository and >update the felix site. > >stefan >
Re: [VOTE] Release Apache Felix Gogo JLine 1.1.4
+1 regards, Karl On Monday, January 28, 2019, Pierre De Rop wrote: > +1 > > thanks Jean-Batiste > > regards > Pierre > > On Mon, Jan 28, 2019 at 9:44 AM Jean-Baptiste Onofré > wrote: > > > +1 (binding) > > > > Regards > > JB > > > > On 25/01/2019 13:55, Jean-Baptiste Onofré wrote: > > > Hi all, > > > > > > We solved 3 issues in this release (release notes): > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12310100=12344851 > > > > > > Staging repository: > > > https://repository.apache.org/content/repositories/ > orgapachefelix-1278/ > > > > > > Please vote to approve this release: > > > > > > [ ] +1 Approve the release > > > [ ] -1 Veto the release (please provide specific comments) > > > > > > This vote will be open for 72 hours. > > > > > > Thanks, > > > Regards > > > JB > > > > > > > -- > > Jean-Baptiste Onofré > > jbono...@apache.org > > http://blog.nanthrax.net > > Talend - http://www.talend.com > > > -- Karl Pauls karlpa...@gmail.com
Re: [VOTE] Release Apache Felix Gogo JLine 1.1.4
+1 thanks Jean-Batiste regards Pierre On Mon, Jan 28, 2019 at 9:44 AM Jean-Baptiste Onofré wrote: > +1 (binding) > > Regards > JB > > On 25/01/2019 13:55, Jean-Baptiste Onofré wrote: > > Hi all, > > > > We solved 3 issues in this release (release notes): > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12344851 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachefelix-1278/ > > > > Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] -1 Veto the release (please provide specific comments) > > > > This vote will be open for 72 hours. > > > > Thanks, > > Regards > > JB > > > > -- > Jean-Baptiste Onofré > jbono...@apache.org > http://blog.nanthrax.net > Talend - http://www.talend.com >
Documentation for Apache Felix Health Checks
Hi all, while creating the first release I found another solution for the problem described in [2] - but when comparing to [1] (that looks like it's the source of it), it does not seem to be consistent (in the wiki [1] there is an Appendix C while the web page [2] does not have that). I'm not sure about the publication process here. Also I would like to move the documentation in the markdown file [3] to the correct location which I believe is a sub page "Apache Felix Health Checks" underneath [4], but there I do not have access rights yet. What's the process for it? Could somebody from the PMC please grant me access to the wiki? Thanks & Best Regards Georg [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115457 [2] http://felix.apache.org/documentation/development/release-management-nexus.html#appendix-b-preparing-releases-on-mac-os-x [3] http://svn.apache.org/viewvc/felix/trunk/healthcheck/docs/felix-health-checks.md?view=log=1849246 [4] https://cwiki.apache.org/confluence/display/FELIX/Subprojects
Re: [VOTE] Release Apache Felix Gogo JLine 1.1.4
+1 (binding) Regards JB On 25/01/2019 13:55, Jean-Baptiste Onofré wrote: > Hi all, > > We solved 3 issues in this release (release notes): > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310100=12344851 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachefelix-1278/ > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] -1 Veto the release (please provide specific comments) > > This vote will be open for 72 hours. > > Thanks, > Regards > JB > -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
[VOTE] Initial release Felix Health Check Annotations 2.0.0, Health Check API 2.0.0, Health Check Core 2.0.0, Health Check General Checks 2.0.0, Health Check Webconsole Plugin 2.0.0
Hi all, We solved 11 issues in this release: https://issues.apache.org/jira/issues/?jql=issuekey%20in%20(FELIX-6024%2CFELIX-6025%2CFELIX-6017%2CFELIX-6018%2CFELIX-6016%2CFELIX-6012%2CFELIX-6011%2CFELIX-6010%2CFELIX-6005%2CFELIX-6004%2CFELIX-5952) (@PMC: Could you please create the versions for this and next release in JIRA for the 5 modules?) Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-1279/ 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 1279 /tmp/felix-staging Please vote to approve this release: [ ] +1 Approve the release [ ] -1 Veto the release (please provide specific comments) This vote will be open for 72 hours. -Georg
Re: [DISCUSS] First release of health check modules annotation, api, core, generalchecks and webconsoleplugin
It's an idea we can add at any time. I don't think it should hold up your first release. ok great - I started the release vote for it... feel free to add this at any time (I'm curious to learn more about this mechanism). -Georg
