[jira] [Commented] (KARAF-4612) Downgrade Felix FileInstall to keep Java6 support
[ https://issues.apache.org/jira/browse/KARAF-4612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411310#comment-15411310 ] Jean-Baptiste Onofré commented on KARAF-4612: - Actually, I just tested and other projects have broken Java 6 support: Pax URL, blueprint, etc. If I downgrade those dependencies, it means that bunch of other issues won't be fixed. So, I would say, Karaf 3.0.5 is the latest release to still fully support Java 6. I'm updating the website accordingly. > Downgrade Felix FileInstall to keep Java6 support > - > > Key: KARAF-4612 > URL: https://issues.apache.org/jira/browse/KARAF-4612 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.6, 3.0.7 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4612) Downgrade Felix FileInstall to keep Java6 support
[ https://issues.apache.org/jira/browse/KARAF-4612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4612. - Resolution: Won't Fix > Downgrade Felix FileInstall to keep Java6 support > - > > Key: KARAF-4612 > URL: https://issues.apache.org/jira/browse/KARAF-4612 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.6, 3.0.7 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4612) Downgrade Felix FileInstall to keep Java6 support
[ https://issues.apache.org/jira/browse/KARAF-4612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4612: Fix Version/s: (was: 3.0.8) > Downgrade Felix FileInstall to keep Java6 support > - > > Key: KARAF-4612 > URL: https://issues.apache.org/jira/browse/KARAF-4612 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.6, 3.0.7 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-4612) Downgrade Felix FileInstall to keep Java6 support
[ https://issues.apache.org/jira/browse/KARAF-4612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4612 started by Jean-Baptiste Onofré. --- > Downgrade Felix FileInstall to keep Java6 support > - > > Key: KARAF-4612 > URL: https://issues.apache.org/jira/browse/KARAF-4612 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.6, 3.0.7 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.8 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4539) Do not default to Xalan as the TransformerFactory implementation
[ https://issues.apache.org/jira/browse/KARAF-4539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4539: Fix Version/s: (was: 3.0.8) 3.0.9 > Do not default to Xalan as the TransformerFactory implementation > > > Key: KARAF-4539 > URL: https://issues.apache.org/jira/browse/KARAF-4539 > Project: Karaf > Issue Type: Bug >Affects Versions: 3.0.5, 3.0.6 >Reporter: Robert Varga >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.9 > > > The switch to Xalan-J as the default transformer factory in KARAF-3956 has > broken OpenDaylight XML processing code in multiple places. > The first issue is that Xalan's TransformerImpl does not support StAXResult, > which is a regression from JVM defaults and requires clear hacks to > workaround: > https://github.com/opendaylight/yangtools/commit/dd5487e20c8a9b2191516b230ccd4e16896652dd. > The other issue seems to be correctness of transformation from DOM to SAX. > The effect is that code in > https://github.com/opendaylight/netconf/blob/3062d9b5a6704075b4b10a8e1ad481738ca370c7/netconf/netconf-netty-util/src/main/java/org/opendaylight/netconf/nettyutil/handler/NetconfEXIToMessageDecoder.java > fails to emit proper namespaces. This looks related to > https://issues.apache.org/jira/browse/XALANJ-2382 and/or > https://bugs.openjdk.java.net/browse/JDK-6305029. > In both cases code which runs just fine with multiple JVMs and worked with > karaf-3.0.3 fails with 3.0.6 unless non-trivial surgery is performed: > https://git.opendaylight.org/gerrit/39368. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4283) List command reporting incorrect bundle state after service recovery
[ https://issues.apache.org/jira/browse/KARAF-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4283: Fix Version/s: (was: 3.0.8) 3.0.9 > List command reporting incorrect bundle state after service recovery > > > Key: KARAF-4283 > URL: https://issues.apache.org/jira/browse/KARAF-4283 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 2.4.3, 3.0.5, 4.0.4 > Environment: Oracle Java 1.7.0_79 > Camel 2.16.1 >Reporter: Quinn Stevenson >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6, 3.0.9 > > > When an OSGi service used by a Camel route disappears, the list command > report bundle containing the Camel route is in the "Waiting" state, which is > expected. > However, when the required OSGi service is restored, the list command > continues to report the bundle containing the Camel route is in the "Waiting" > state, even though the Camel route recovers and is processing exchanges. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2511) Review and update documentation
[ https://issues.apache.org/jira/browse/KARAF-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2511: Fix Version/s: (was: 3.0.8) 3.0.9 > Review and update documentation > --- > > Key: KARAF-2511 > URL: https://issues.apache.org/jira/browse/KARAF-2511 > Project: Karaf > Issue Type: Task > Components: karaf-documentation >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6, 3.0.9 > > > The documentation (manual) should be reviewed: > - The subshell part should be described (usage and configuration). > - The "code samples"/screenshots have to be updated with Karaf 3.0.0 use cases > - a global polishing, double read -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3825) Add ability to shutdown Karaf with a disabled shutdown port
[ https://issues.apache.org/jira/browse/KARAF-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3825: Fix Version/s: (was: 3.0.8) 3.0.9 > Add ability to shutdown Karaf with a disabled shutdown port > --- > > Key: KARAF-3825 > URL: https://issues.apache.org/jira/browse/KARAF-3825 > Project: Karaf > Issue Type: Improvement > Components: karaf-core >Affects Versions: 3.0.3, 4.0.0 >Reporter: Dmitry Konstantinov >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6, 3.0.9 > > > Sometimes by security reasons listen ports are asked to disable. It would be > nice to provide an alternative way to trigger Karaf shutdown by touching a > special file. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4092) feature.xml to support SystemProperties
[ https://issues.apache.org/jira/browse/KARAF-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4092: Fix Version/s: (was: 3.0.8) 3.0.9 > feature.xml to support SystemProperties > --- > > Key: KARAF-4092 > URL: https://issues.apache.org/jira/browse/KARAF-4092 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Amit Patel >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6, 3.0.9 > > > We need feature.xml file to have access to systemProperty. For example we are > using feature in below format and it has and > define in SystemProperty file. so we can externalized the jar file location > and it can be specified at runtime though SystemProperties > > start="true">file:/ajsc-jars/osgiservice1//-.jar > - > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-4623) Upgrade to Spring 4.1.8
[ https://issues.apache.org/jira/browse/KARAF-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-4623: Fix Version/s: (was: 3.0.8) 3.0.9 > Upgrade to Spring 4.1.8 > --- > > Key: KARAF-4623 > URL: https://issues.apache.org/jira/browse/KARAF-4623 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Affects Versions: 4.1.0, 4.0.5, 3.0.7 >Reporter: Krzysztof Sobkowiak >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6, 3.0.9 > > > We are currently using Spring 4.1.7.RELEASE, but one user has pointed to a > vulerability in this version http://pivotal.io/security/cve-2015-5211. We > should upgrade to 4.1.8.RELEASE (not available yet as bundle) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (KARAF-4622) Upgrade to Spring 3.2.17
[ https://issues.apache.org/jira/browse/KARAF-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-4622. - Resolution: Fixed > Upgrade to Spring 3.2.17 > > > Key: KARAF-4622 > URL: https://issues.apache.org/jira/browse/KARAF-4622 > Project: Karaf > Issue Type: Dependency upgrade >Affects Versions: 4.1.0, 4.0.5, 3.0.7 >Reporter: Krzysztof Sobkowiak >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6, 3.0.8 > > > We are currently using Spring 3.2.14.RELEASE, but one user has pointed to a > vulerability in this version http://pivotal.io/security/cve-2015-5211. We > should upgrade to 3.2.17.RELEASE (available in ServiceMix bundles). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-4622) Upgrade to Spring 3.2.17
[ https://issues.apache.org/jira/browse/KARAF-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411000#comment-15411000 ] ASF subversion and git services commented on KARAF-4622: Commit 65d100a206937163aef656035303796a0ce1352f in karaf's branch refs/heads/karaf-3.0.x from [~jbonofre] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=65d100a ] [KARAF-4622] Upgrade to Spring 3.2.17.RELEASE_1 > Upgrade to Spring 3.2.17 > > > Key: KARAF-4622 > URL: https://issues.apache.org/jira/browse/KARAF-4622 > Project: Karaf > Issue Type: Dependency upgrade >Affects Versions: 4.1.0, 4.0.5, 3.0.7 >Reporter: Krzysztof Sobkowiak >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6, 3.0.8 > > > We are currently using Spring 3.2.14.RELEASE, but one user has pointed to a > vulerability in this version http://pivotal.io/security/cve-2015-5211. We > should upgrade to 3.2.17.RELEASE (available in ServiceMix bundles). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-4622) Upgrade to Spring 3.2.17
[ https://issues.apache.org/jira/browse/KARAF-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-4622 started by Jean-Baptiste Onofré. --- > Upgrade to Spring 3.2.17 > > > Key: KARAF-4622 > URL: https://issues.apache.org/jira/browse/KARAF-4622 > Project: Karaf > Issue Type: Dependency upgrade >Affects Versions: 4.1.0, 4.0.5, 3.0.7 >Reporter: Krzysztof Sobkowiak >Assignee: Jean-Baptiste Onofré > Fix For: 4.1.0, 4.0.6, 3.0.8 > > > We are currently using Spring 3.2.14.RELEASE, but one user has pointed to a > vulerability in this version http://pivotal.io/security/cve-2015-5211. We > should upgrade to 3.2.17.RELEASE (available in ServiceMix bundles). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
