Re: [VOTE] Apache Felix SCR Tooling Release
+1 2014-03-13 21:25 GMT+01:00 Pierre De Rop pierre.de...@gmail.com: Hi Carsten; Did some basic tests with the maven scrplugin, as well as with the new bndtools scrplugin. +1 kind regards; /Pierre On Wed, Mar 12, 2014 at 10:53 AM, Carsten Ziegeler cziege...@apache.org wrote: Hi, It's time to cut a new release for our SCR Tooling. This release includes some bug fixes for Maven, Ant and our SCR annotations as well as the first release of our bnd plugin: Updates and Bug Fixes (identical for all three releases): https://issues.apache.org/jira/browse/FELIX/fixforversion/12325061 Apache Felix SCR Generator 1.9.0 Apache Felix Maven SCR Plugin 1.16.0 Apache Felix SCR Ant Task 1.10.0 Updates and Bug Fixes (identical for all three releases): https://issues.apache.org/jira/browse/FELIX/fixforversion/12324798/ Apache Felix SCR Annotations 1.9.8 New Release: Apache Felix SCR Bnd Plugin 1.0.0 Staging repository: https://repository.apache.org/content/repositories/orgapachefelix-1012 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 1012 /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 (at least). Regards, Carsten -- Carsten Ziegeler cziege...@apache.org -- Carsten Ziegeler cziege...@apache.org
[VOTE RESULT] Apache Felix SCR Tooling Release
The vote passes with three binding +1 votes from Pierre De Rop, Clement Escoffier, and Carsten Ziegeler. Thanks everyone for voting Carsten -- Carsten Ziegeler cziege...@apache.org
[jira] [Created] (FELIX-4460) Bad HTTPS settings prevent startup HTTP listener
Dominique Pfister created FELIX-4460: Summary: Bad HTTPS settings prevent startup HTTP listener Key: FELIX-4460 URL: https://issues.apache.org/jira/browse/FELIX-4460 Project: Felix Issue Type: Bug Components: HTTP Service Affects Versions: http-2.2.2 Reporter: Dominique Pfister Entering some bad values for the HTTPS configuration prevents the complete Jetty server startup. This looks like a regression of upgrading Jetty to version 7. The current implementation initializes all enabled connectors, adds them to the server and then starts the server which in turn starts all connectors. If one of them fails to start, the complete server startup fails and the Jetty Bridge is no longer accessible via HTTP. I suggest to initialize an additional HTTPS container only after having the server, so at least HTTP stays available if enabled. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FELIX-4460) Bad HTTPS settings prevent startup HTTP listener
[ https://issues.apache.org/jira/browse/FELIX-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Pfister updated FELIX-4460: - Description: Entering some bad values for the HTTPS configuration prevents the complete Jetty server startup. This looks like a regression of upgrading Jetty to version 7. The current implementation initializes all enabled connectors, adds them to the server and then starts the server which in turn starts all connectors. If one of them fails to start, the complete server startup fails and the Jetty Bridge is no longer accessible via HTTP. I suggest to initialize an additional HTTPS connector only after having started the server, so at least HTTP stays available if enabled. was: Entering some bad values for the HTTPS configuration prevents the complete Jetty server startup. This looks like a regression of upgrading Jetty to version 7. The current implementation initializes all enabled connectors, adds them to the server and then starts the server which in turn starts all connectors. If one of them fails to start, the complete server startup fails and the Jetty Bridge is no longer accessible via HTTP. I suggest to initialize an additional HTTPS container only after having the server, so at least HTTP stays available if enabled. Bad HTTPS settings prevent startup HTTP listener Key: FELIX-4460 URL: https://issues.apache.org/jira/browse/FELIX-4460 Project: Felix Issue Type: Bug Components: HTTP Service Affects Versions: http-2.2.2 Reporter: Dominique Pfister Attachments: patch.txt Entering some bad values for the HTTPS configuration prevents the complete Jetty server startup. This looks like a regression of upgrading Jetty to version 7. The current implementation initializes all enabled connectors, adds them to the server and then starts the server which in turn starts all connectors. If one of them fails to start, the complete server startup fails and the Jetty Bridge is no longer accessible via HTTP. I suggest to initialize an additional HTTPS connector only after having started the server, so at least HTTP stays available if enabled. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FELIX-4460) Bad HTTPS settings prevent startup HTTP listener
[ https://issues.apache.org/jira/browse/FELIX-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Pfister updated FELIX-4460: - Attachment: patch.txt Patch to initialize auxiliary HTTPS connector only after having started the server. Bad HTTPS settings prevent startup HTTP listener Key: FELIX-4460 URL: https://issues.apache.org/jira/browse/FELIX-4460 Project: Felix Issue Type: Bug Components: HTTP Service Affects Versions: http-2.2.2 Reporter: Dominique Pfister Attachments: patch.txt Entering some bad values for the HTTPS configuration prevents the complete Jetty server startup. This looks like a regression of upgrading Jetty to version 7. The current implementation initializes all enabled connectors, adds them to the server and then starts the server which in turn starts all connectors. If one of them fails to start, the complete server startup fails and the Jetty Bridge is no longer accessible via HTTP. I suggest to initialize an additional HTTPS connector only after having started the server, so at least HTTP stays available if enabled. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FELIX-4460) Bad HTTPS settings prevent HTTP connector startup
[ https://issues.apache.org/jira/browse/FELIX-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Pfister updated FELIX-4460: - Summary: Bad HTTPS settings prevent HTTP connector startup (was: Bad HTTPS settings prevent startup HTTP listener) Bad HTTPS settings prevent HTTP connector startup - Key: FELIX-4460 URL: https://issues.apache.org/jira/browse/FELIX-4460 Project: Felix Issue Type: Bug Components: HTTP Service Affects Versions: http-2.2.2 Reporter: Dominique Pfister Attachments: patch.txt Entering some bad values for the HTTPS configuration prevents the complete Jetty server startup. This looks like a regression of upgrading Jetty to version 7. The current implementation initializes all enabled connectors, adds them to the server and then starts the server which in turn starts all connectors. If one of them fails to start, the complete server startup fails and the Jetty Bridge is no longer accessible via HTTP. I suggest to initialize an additional HTTPS connector only after having started the server, so at least HTTP stays available if enabled. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FELIX-4460) Bad HTTPS settings prevent Jetty startup
[ https://issues.apache.org/jira/browse/FELIX-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Pfister updated FELIX-4460: - Summary: Bad HTTPS settings prevent Jetty startup (was: Bad HTTPS settings prevent HTTP connector startup) Bad HTTPS settings prevent Jetty startup Key: FELIX-4460 URL: https://issues.apache.org/jira/browse/FELIX-4460 Project: Felix Issue Type: Bug Components: HTTP Service Affects Versions: http-2.2.2 Reporter: Dominique Pfister Attachments: patch.txt Entering some bad values for the HTTPS configuration prevents the complete Jetty server startup. This looks like a regression of upgrading Jetty to version 7. The current implementation initializes all enabled connectors, adds them to the server and then starts the server which in turn starts all connectors. If one of them fails to start, the complete server startup fails and the Jetty Bridge is no longer accessible via HTTP. I suggest to initialize an additional HTTPS connector only after having started the server, so at least HTTP stays available if enabled. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (FELIX-4460) Bad HTTPS settings render Jetty inaccessible
[ https://issues.apache.org/jira/browse/FELIX-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Pfister updated FELIX-4460: - Summary: Bad HTTPS settings render Jetty inaccessible (was: Bad HTTPS settings prevent Jetty startup) Bad HTTPS settings render Jetty inaccessible Key: FELIX-4460 URL: https://issues.apache.org/jira/browse/FELIX-4460 Project: Felix Issue Type: Bug Components: HTTP Service Affects Versions: http-2.2.2 Reporter: Dominique Pfister Attachments: patch.txt Entering some bad values for the HTTPS configuration prevents the complete Jetty server startup. This looks like a regression of upgrading Jetty to version 7. The current implementation initializes all enabled connectors, adds them to the server and then starts the server which in turn starts all connectors. If one of them fails to start, the complete server startup fails and the Jetty Bridge is no longer accessible via HTTP. I suggest to initialize an additional HTTPS connector only after having started the server, so at least HTTP stays available if enabled. -- This message was sent by Atlassian JIRA (v6.2#6252)
