[jira] [Commented] (KARAF-5622) Upgrade to commons-compress 1.16.1
[ https://issues.apache.org/jira/browse/KARAF-5622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369770#comment-16369770 ] ASF GitHub Bot commented on KARAF-5622: --- jbonofre opened a new pull request #460: [KARAF-5622] Upgrade to commons-compress 1.16.1 URL: https://github.com/apache/karaf/pull/460 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to commons-compress 1.16.1 > -- > > Key: KARAF-5622 > URL: https://issues.apache.org/jira/browse/KARAF-5622 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-5624) Upgrade to jline 3.6.1
[ https://issues.apache.org/jira/browse/KARAF-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-5624. - Resolution: Fixed > Upgrade to jline 3.6.1 > -- > > Key: KARAF-5624 > URL: https://issues.apache.org/jira/browse/KARAF-5624 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5624) Upgrade to jline 3.6.1
[ https://issues.apache.org/jira/browse/KARAF-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369742#comment-16369742 ] ASF GitHub Bot commented on KARAF-5624: --- jbonofre closed pull request #458: [KARAF-5624] Upgrade to jline 3.6.1 URL: https://github.com/apache/karaf/pull/458 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/pom.xml b/pom.xml index 78dab4a2c6..9058947b32 100644 --- a/pom.xml +++ b/pom.xml @@ -258,7 +258,7 @@ 1.17 3.9.0.GA 9.3.21.v20170918 -3.6.0 +3.6.1 3.2.3 1.2.17 3.5.2 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to jline 3.6.1 > -- > > Key: KARAF-5624 > URL: https://issues.apache.org/jira/browse/KARAF-5624 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KARAF-5625) Upgrade to Pax Swissbox 1.8.3
[ https://issues.apache.org/jira/browse/KARAF-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-5625. - Resolution: Fixed > Upgrade to Pax Swissbox 1.8.3 > - > > Key: KARAF-5625 > URL: https://issues.apache.org/jira/browse/KARAF-5625 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-test >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5625) Upgrade to Pax Swissbox 1.8.3
[ https://issues.apache.org/jira/browse/KARAF-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5625: Fix Version/s: (was: 4.1.6) > Upgrade to Pax Swissbox 1.8.3 > - > > Key: KARAF-5625 > URL: https://issues.apache.org/jira/browse/KARAF-5625 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-test >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5625) Upgrade to Pax Swissbox 1.8.3
[ https://issues.apache.org/jira/browse/KARAF-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369737#comment-16369737 ] ASF GitHub Bot commented on KARAF-5625: --- jbonofre closed pull request #457: [KARAF-5625] Upgrade to Pax Swissbox 1.8.3 URL: https://github.com/apache/karaf/pull/457 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/pom.xml b/pom.xml index 78dab4a2c6..7aeca555f2 100644 --- a/pom.xml +++ b/pom.xml @@ -273,7 +273,7 @@ 4.11.0 1.10.1 1.5.0 -1.8.2 +1.8.3 2.5.4 6.1.1 3.0.0 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to Pax Swissbox 1.8.3 > - > > Key: KARAF-5625 > URL: https://issues.apache.org/jira/browse/KARAF-5625 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-test >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5623) Upgrade to maven-bundle-plugin 3.5.0
[ https://issues.apache.org/jira/browse/KARAF-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369080#comment-16369080 ] ASF GitHub Bot commented on KARAF-5623: --- jbonofre opened a new pull request #459: [KARAF-5623] Upgrade to maven-bundle-plugin 3.5.0 URL: https://github.com/apache/karaf/pull/459 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to maven-bundle-plugin 3.5.0 > > > Key: KARAF-5623 > URL: https://issues.apache.org/jira/browse/KARAF-5623 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-build >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5624) Upgrade to jline 3.6.1
[ https://issues.apache.org/jira/browse/KARAF-5624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369077#comment-16369077 ] ASF GitHub Bot commented on KARAF-5624: --- jbonofre opened a new pull request #458: [KARAF-5624] Upgrade to jline 3.6.1 URL: https://github.com/apache/karaf/pull/458 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to jline 3.6.1 > -- > > Key: KARAF-5624 > URL: https://issues.apache.org/jira/browse/KARAF-5624 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5625) Upgrade to Pax Swissbox 1.8.3
[ https://issues.apache.org/jira/browse/KARAF-5625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369072#comment-16369072 ] ASF GitHub Bot commented on KARAF-5625: --- jbonofre opened a new pull request #457: [KARAF-5625] Upgrade to Pax Swissbox 1.8.3 URL: https://github.com/apache/karaf/pull/457 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to Pax Swissbox 1.8.3 > - > > Key: KARAF-5625 > URL: https://issues.apache.org/jira/browse/KARAF-5625 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-test >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0, 4.1.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5628) Corrupt gc.log due to unseparated VM settings
[ https://issues.apache.org/jira/browse/KARAF-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369068#comment-16369068 ] Jean-Baptiste Onofré commented on KARAF-5628: - Fair enough. I will do the improvements. > Corrupt gc.log due to unseparated VM settings > - > > Key: KARAF-5628 > URL: https://issues.apache.org/jira/browse/KARAF-5628 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Reporter: Rico Neubauer >Assignee: Jean-Baptiste Onofré >Priority: Major > > The VM properties used for the start, stop, status and client scripts all use > one common configuration of the VM properties, like Xmx and GC settings. > This has one particular issue when activating the gc.log (-Xloggc:gc.log with > Oracle-VM): Invoking e.g. status while Karaf is running, uses the same > settings, thus points to the same file and corrupts it with NUL values (see > here for details: > [Stackoverflow|[https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl]] > ). > > I would like to request the possibility to configure the VM properties for > starting the instance independently from the maintenance scripts - due to the > issue and also since e.g. running status with lots of heap (if instance is > configured to it) is unneeded. > > Even making it broader, I think it would also make sense to be able to > configure the settings completely, since currently some things are hard-coded > in the scripts, like the _-Xdum_p and _-Xlp_ settings for AIX, where I > personally would like to configure it to _-Xdump:heap:events=gpf,opts=PHD_, > which is currently not possible using the configuration only. Also especially > for AIX, there is _LDR_CNTRL=MAXDATA=0xB000@DSA_, which might not be > desired when running with heaps larger than 3GB. > > If you agree on a separation, I would make a proposal as PR. Please let me > know. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KARAF-5628) Corrupt gc.log due to unseparated VM settings
[ https://issues.apache.org/jira/browse/KARAF-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-5628: --- Assignee: Jean-Baptiste Onofré > Corrupt gc.log due to unseparated VM settings > - > > Key: KARAF-5628 > URL: https://issues.apache.org/jira/browse/KARAF-5628 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Reporter: Rico Neubauer >Assignee: Jean-Baptiste Onofré >Priority: Major > > The VM properties used for the start, stop, status and client scripts all use > one common configuration of the VM properties, like Xmx and GC settings. > This has one particular issue when activating the gc.log (-Xloggc:gc.log with > Oracle-VM): Invoking e.g. status while Karaf is running, uses the same > settings, thus points to the same file and corrupts it with NUL values (see > here for details: > [Stackoverflow|[https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl]] > ). > > I would like to request the possibility to configure the VM properties for > starting the instance independently from the maintenance scripts - due to the > issue and also since e.g. running status with lots of heap (if instance is > configured to it) is unneeded. > > Even making it broader, I think it would also make sense to be able to > configure the settings completely, since currently some things are hard-coded > in the scripts, like the _-Xdum_p and _-Xlp_ settings for AIX, where I > personally would like to configure it to _-Xdump:heap:events=gpf,opts=PHD_, > which is currently not possible using the configuration only. Also especially > for AIX, there is _LDR_CNTRL=MAXDATA=0xB000@DSA_, which might not be > desired when running with heaps larger than 3GB. > > If you agree on a separation, I would make a proposal as PR. Please let me > know. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5613) Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
[
https://issues.apache.org/jira/browse/KARAF-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369054#comment-16369054
]
Saikat Ghosh commented on KARAF-5613:
-
Note we found another change in v4.1.5 against v4.0.9:
*shell:tac* no longer preserves newlines when generating its string output
> Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
> -
>
> Key: KARAF-5613
> URL: https://issues.apache.org/jira/browse/KARAF-5613
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.5
>Reporter: Saikat Ghosh
>Assignee: Guillaume Nodet
>Priority: Major
> Labels: Scripting
>
> Scripting behavior has changed between Karaf v4.0.9 and v4.1.5
> *The following is a shell session for v4.0.10*
> {noformat}
> Apache Karaf (4.0.10)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> a2 = $a1 split " "
> This
> is
> a
> test
> karaf@root()> $a2 2
> a
> karaf@root()> $a2 3
> test
> karaf@root()> each ($a2) {echo $it}
> This
> is
> a
> test
> karaf@root()> each ($a1 split " ") {echo $it}
> This
> is
> a
> test{noformat}
> *The following is a shell session for v4.1.5*
> {noformat}
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> $a1
> This is a test
> karaf@root()> a2 = ($a1 split " ")
> karaf@root()> $a2 0
> This
> karaf@root()> $a2 1
> is
> karaf@root()> $a2 2
> a
> karaf@root()> each ($a1 split " ") {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call
> karaf@root()> $a2
> karaf@root()> each ($a2) {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call{noformat}
> In both versions the split creates an array - but the shell does not seem to
> be automatically coerce $a2 into an array for v4.1.5
> This is breaking several scripts currently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5613) Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
[
https://issues.apache.org/jira/browse/KARAF-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16369051#comment-16369051
]
Saikat Ghosh commented on KARAF-5613:
-
Great to know! This is simple fix for existing scripts and we can implement
easily.
Are there other changes to be aware of that we can read up on?
Many thanks,
Saycat
> Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
> -
>
> Key: KARAF-5613
> URL: https://issues.apache.org/jira/browse/KARAF-5613
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.5
>Reporter: Saikat Ghosh
>Assignee: Guillaume Nodet
>Priority: Major
> Labels: Scripting
>
> Scripting behavior has changed between Karaf v4.0.9 and v4.1.5
> *The following is a shell session for v4.0.10*
> {noformat}
> Apache Karaf (4.0.10)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> a2 = $a1 split " "
> This
> is
> a
> test
> karaf@root()> $a2 2
> a
> karaf@root()> $a2 3
> test
> karaf@root()> each ($a2) {echo $it}
> This
> is
> a
> test
> karaf@root()> each ($a1 split " ") {echo $it}
> This
> is
> a
> test{noformat}
> *The following is a shell session for v4.1.5*
> {noformat}
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> $a1
> This is a test
> karaf@root()> a2 = ($a1 split " ")
> karaf@root()> $a2 0
> This
> karaf@root()> $a2 1
> is
> karaf@root()> $a2 2
> a
> karaf@root()> each ($a1 split " ") {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call
> karaf@root()> $a2
> karaf@root()> each ($a2) {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call{noformat}
> In both versions the split creates an array - but the shell does not seem to
> be automatically coerce $a2 into an array for v4.1.5
> This is breaking several scripts currently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-5629) Add new karaf commands shell:elif and shell:else
[
https://issues.apache.org/jira/browse/KARAF-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-5629:
--
Description:
Take the following example:
{code:java}
if {"$v" equals "a"} {
do something a
} {
if {"$v" equals "b"} {
do something b
} {
if {"$v" equals "c"} {
do something c
} {
do something others
}
}
}
{code}
By introducing the commands shell:elif and shell:else, this can be simplified
as follows:
{code:java}
if {"$v" equals "a"} {
do something a
} elif {"$v" equals "b"} {
do something b
} elif {"$v" equals "c"} {
do something c
} else {
do something others
}
{code}
was:
Take the following example:
{code:java}
if {"$v" equals "a"} {
do something a
} {
if {"$v" equals "b"} {
do something b
} {
if {"$v" equals "c"} {
do something c
} {
do something others
}
}
}
{code}
By introducing the commands shell:elif and shell:else, this can be simplified
as follows:
{code:java}
if {"$v" equals "a"} {
do something a
} elif {"$v" equals "b"} {
do something b
} elif {"$v" equals "c"} {
do something c
} else {
do something others
}
{code}
> Add new karaf commands shell:elif and shell:else
>
>
> Key: KARAF-5629
> URL: https://issues.apache.org/jira/browse/KARAF-5629
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-shell
>Affects Versions: 4.1.5, 4.2.0.M2
>Reporter: Lijun Liao
>Priority: Minor
> Fix For: 4.2.0, 4.1.6
>
>
> Take the following example:
> {code:java}
> if {"$v" equals "a"} {
> do something a
> } {
> if {"$v" equals "b"} {
> do something b
> } {
> if {"$v" equals "c"} {
> do something c
> } {
> do something others
> }
> }
> }
> {code}
> By introducing the commands shell:elif and shell:else, this can be simplified
> as follows:
> {code:java}
> if {"$v" equals "a"} {
> do something a
> } elif {"$v" equals "b"} {
> do something b
> } elif {"$v" equals "c"} {
> do something c
> } else {
> do something others
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-5629) Add new karaf commands shell:elif and shell:else
[
https://issues.apache.org/jira/browse/KARAF-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lijun Liao updated KARAF-5629:
--
Description:
Take the following example:
{code:java}
if {"$v" equals "a"} {
do something a
} {
if {"$v" equals "b"} {
do something b
} {
if {"$v" equals "c"} {
do something c
} {
do something others
}
}
}
{code}
By introducing the commands shell:elif and shell:else, this can be simplified
as follows:
{code:java}
if {"$v" equals "a"} {
do something a
} elif {"$v" equals "b"} {
do something b
} elif {"$v" equals "c"} {
do something c
} else {
do something others
}
{code}
was:
Take the following example:
{code:java}
if {"$v" equals "a"} {
do something a
} {
if {"$v" equals "b"} {
do something b
} {
if {"$v" equals "c"} {
do something c
} {
do something others
}
}
}
{code}
By introducing the commands shell:elif and shell:else, this can be simplified
as follows:
{code:java}
if {"$v" equals "a"} {
do something a
} elif {"$v" equals "b"} {
do something b
} elif {"$v" equals "c"} {
do something c
} else {
do something others
}
{code}
> Add new karaf commands shell:elif and shell:else
>
>
> Key: KARAF-5629
> URL: https://issues.apache.org/jira/browse/KARAF-5629
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-shell
>Affects Versions: 4.1.5, 4.2.0.M2
>Reporter: Lijun Liao
>Priority: Minor
> Fix For: 4.2.0, 4.1.6
>
>
> Take the following example:
> {code:java}
> if {"$v" equals "a"} {
> do something a
> } {
> if {"$v" equals "b"} {
> do something b
> } {
> if {"$v" equals "c"} {
> do something c
> } {
> do something others
> }
> }
> }
> {code}
>
> By introducing the commands shell:elif and shell:else, this can be simplified
> as follows:
> {code:java}
> if {"$v" equals "a"} {
> do something a
> } elif {"$v" equals "b"} {
> do something b
> } elif {"$v" equals "c"} {
> do something c
> } else {
> do something others
> }
> {code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-5629) Add new karaf commands shell:elif and shell:else
Lijun Liao created KARAF-5629:
-
Summary: Add new karaf commands shell:elif and shell:else
Key: KARAF-5629
URL: https://issues.apache.org/jira/browse/KARAF-5629
Project: Karaf
Issue Type: New Feature
Components: karaf-shell
Affects Versions: 4.2.0.M2, 4.1.5
Reporter: Lijun Liao
Fix For: 4.2.0, 4.1.6
Take the following example:
{code:java}
if {"$v" equals "a"} {
do something a
} {
if {"$v" equals "b"} {
do something b
} {
if {"$v" equals "c"} {
do something c
} {
do something others
}
}
}
{code}
By introducing the commands shell:elif and shell:else, this can be simplified
as follows:
{code:java}
if {"$v" equals "a"} {
do something a
} elif {"$v" equals "b"} {
do something b
} elif {"$v" equals "c"} {
do something c
} else {
do something others
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (KARAF-5617) Upgrade to JNA 4.5.1
[ https://issues.apache.org/jira/browse/KARAF-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-5617. - Resolution: Fixed > Upgrade to JNA 4.5.1 > > > Key: KARAF-5617 > URL: https://issues.apache.org/jira/browse/KARAF-5617 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5617) Upgrade to JNA 4.5.1
[ https://issues.apache.org/jira/browse/KARAF-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368970#comment-16368970 ] ASF GitHub Bot commented on KARAF-5617: --- jbonofre closed pull request #455: [KARAF-5617] Upgrade to JNA 4.5.1 URL: https://github.com/apache/karaf/pull/455 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign pull request (from a fork), the diff is supplied below (as it won't show otherwise due to GitHub magic): diff --git a/pom.xml b/pom.xml index 7d3a824b17..78dab4a2c6 100644 --- a/pom.xml +++ b/pom.xml @@ -148,7 +148,7 @@ 3.2.4_1 2.2.0 -4.5.0 +4.5.1 2.2.11 1.9.2 1.10 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to JNA 4.5.1 > > > Key: KARAF-5617 > URL: https://issues.apache.org/jira/browse/KARAF-5617 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5628) Corrupt gc.log due to unseparated VM settings
[ https://issues.apache.org/jira/browse/KARAF-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rico Neubauer updated KARAF-5628: - Description: The VM properties used for the start, stop, status and client scripts all use one common configuration of the VM properties, like Xmx and GC settings. This has one particular issue when activating the gc.log (-Xloggc:gc.log with Oracle-VM): Invoking e.g. status while Karaf is running, uses the same settings, thus points to the same file and corrupts it with NUL values (see here for details: [Stackoverflow|[https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl]] ). I would like to request the possibility to configure the VM properties for starting the instance independently from the maintenance scripts - due to the issue and also since e.g. running status with lots of heap (if instance is configured to it) is unneeded. Even making it broader, I think it would also make sense to be able to configure the settings completely, since currently some things are hard-coded in the scripts, like the _-Xdum_p and _-Xlp_ settings for AIX, where I personally would like to configure it to _-Xdump:heap:events=gpf,opts=PHD_, which is currently not possible using the configuration only. Also especially for AIX, there is _LDR_CNTRL=MAXDATA=0xB000@DSA_, which might not be desired when running with heaps larger than 3GB. If you agree on a separation, I would make a proposal as PR. Please let me know. was: The VM properties used for the start, stop, status and client scripts all use one common configuration of the VM properties, like Xmx and GC settings. This has one particular issue when activating the gc.log (-Xloggc:gc.log with Oracle-VM): Invoking e.g. status while Karaf is running, uses the same settings, thus points to the same file and corrupts it with NUL values (see here for details: [Stackoverflow|[https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl]]). I would like to request the possibility to configure the VM properties for starting the instance independently from the maintenance scripts - due to the issue and also since e.g. running status with lots of heap (if instance is configured to it) is unneeded. Even making it broader, I think it would also make sense to be able to configure the settings completely, since currently some things are hard-coded in the scripts, like the _-Xdum_p and _-Xlp_ settings for AIX, where I personally would like to configure it to _-Xdump:heap:events=gpf,opts=PHD_, which is currently not possible using the configuration only. Also especially for AIX, there is _LDR_CNTRL=MAXDATA=0xB000@DSA_, which might not be desired when running with heaps larger than 3GB. If you agree on a separation, I would make a proposal as PR. Please let me know. > Corrupt gc.log due to unseparated VM settings > - > > Key: KARAF-5628 > URL: https://issues.apache.org/jira/browse/KARAF-5628 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Reporter: Rico Neubauer >Priority: Major > > The VM properties used for the start, stop, status and client scripts all use > one common configuration of the VM properties, like Xmx and GC settings. > This has one particular issue when activating the gc.log (-Xloggc:gc.log with > Oracle-VM): Invoking e.g. status while Karaf is running, uses the same > settings, thus points to the same file and corrupts it with NUL values (see > here for details: > [Stackoverflow|[https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl]] > ). > > I would like to request the possibility to configure the VM properties for > starting the instance independently from the maintenance scripts - due to the > issue and also since e.g. running status with lots of heap (if instance is > configured to it) is unneeded. > > Even making it broader, I think it would also make sense to be able to > configure the settings completely, since currently some things are hard-coded > in the scripts, like the _-Xdum_p and _-Xlp_ settings for AIX, where I > personally would like to configure it to _-Xdump:heap:events=gpf,opts=PHD_, > which is currently not possible using the configuration only. Also especially > for AIX, there is _LDR_CNTRL=MAXDATA=0xB000@DSA_, which might not be > desired when running with heaps larger than 3GB. > > If you agree on a separation, I would make a proposal as PR. Please let me > know. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5628) Corrupt gc.log due to unseparated VM settings
[ https://issues.apache.org/jira/browse/KARAF-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rico Neubauer updated KARAF-5628: - Description: The VM properties used for the start, stop, status and client scripts all use one common configuration of the VM properties, like Xmx and GC settings. This has one particular issue when activating the gc.log (-Xloggc:gc.log with Oracle-VM): Invoking e.g. status while Karaf is running, uses the same settings, thus points to the same file and corrupts it with NUL values (see here for details: [Stackoverflow|[https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl]]). I would like to request the possibility to configure the VM properties for starting the instance independently from the maintenance scripts - due to the issue and also since e.g. running status with lots of heap (if instance is configured to it) is unneeded. Even making it broader, I think it would also make sense to be able to configure the settings completely, since currently some things are hard-coded in the scripts, like the _-Xdum_p and _-Xlp_ settings for AIX, where I personally would like to configure it to _-Xdump:heap:events=gpf,opts=PHD_, which is currently not possible using the configuration only. Also especially for AIX, there is _LDR_CNTRL=MAXDATA=0xB000@DSA_, which might not be desired when running with heaps larger than 3GB. If you agree on a separation, I would make a proposal as PR. Please let me know. was: The VM properties used for the start, stop, status and client scripts all use one common configuration of the VM properties, like Xmx and GC settings. This has one particular issue when activating the gc.log (-Xloggc:gc.log with Oracle-VM): Invoking e.g. status while Karaf is running, uses the same settings, thus points to the same file and corrupts it with NUL values (see here for details: [Stackoverflow|[https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl]).] I would like to request the possibility to configure the VM properties for starting the instance independently from the maintenance scripts - due to the issue and also since e.g. running status with lots of heap (if instance is configured to it) is unneeded. Even making it broader, I think it would also make sense to be able to configure the settings completely, since currently some things are hard-coded in the scripts, like the _-Xdum_p and _-Xlp_ settings for AIX, where I personally would like to configure it to _-Xdump:heap:events=gpf,opts=PHD_, which is currently not possible using the configuration only. Also especially for AIX, there is _LDR_CNTRL=MAXDATA=0xB000@DSA_, which might not be desired when running with heaps larger than 3GB. If you agree on a separation, I would make a proposal as PR. Please let me know. > Corrupt gc.log due to unseparated VM settings > - > > Key: KARAF-5628 > URL: https://issues.apache.org/jira/browse/KARAF-5628 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Reporter: Rico Neubauer >Priority: Major > > The VM properties used for the start, stop, status and client scripts all use > one common configuration of the VM properties, like Xmx and GC settings. > This has one particular issue when activating the gc.log (-Xloggc:gc.log with > Oracle-VM): Invoking e.g. status while Karaf is running, uses the same > settings, thus points to the same file and corrupts it with NUL values (see > here for details: > [Stackoverflow|[https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl]]). > > I would like to request the possibility to configure the VM properties for > starting the instance independently from the maintenance scripts - due to the > issue and also since e.g. running status with lots of heap (if instance is > configured to it) is unneeded. > > Even making it broader, I think it would also make sense to be able to > configure the settings completely, since currently some things are hard-coded > in the scripts, like the _-Xdum_p and _-Xlp_ settings for AIX, where I > personally would like to configure it to _-Xdump:heap:events=gpf,opts=PHD_, > which is currently not possible using the configuration only. Also especially > for AIX, there is _LDR_CNTRL=MAXDATA=0xB000@DSA_, which might not be > desired when running with heaps larger than 3GB. > > If you agree on a separation, I would make a proposal as PR. Please let me > know. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (KARAF-5613) Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
[
https://issues.apache.org/jira/browse/KARAF-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed KARAF-5613.
--
Resolution: Won't Fix
> Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
> -
>
> Key: KARAF-5613
> URL: https://issues.apache.org/jira/browse/KARAF-5613
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.5
>Reporter: Saikat Ghosh
>Assignee: Guillaume Nodet
>Priority: Major
> Labels: Scripting
>
> Scripting behavior has changed between Karaf v4.0.9 and v4.1.5
> *The following is a shell session for v4.0.10*
> {noformat}
> Apache Karaf (4.0.10)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> a2 = $a1 split " "
> This
> is
> a
> test
> karaf@root()> $a2 2
> a
> karaf@root()> $a2 3
> test
> karaf@root()> each ($a2) {echo $it}
> This
> is
> a
> test
> karaf@root()> each ($a1 split " ") {echo $it}
> This
> is
> a
> test{noformat}
> *The following is a shell session for v4.1.5*
> {noformat}
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> $a1
> This is a test
> karaf@root()> a2 = ($a1 split " ")
> karaf@root()> $a2 0
> This
> karaf@root()> $a2 1
> is
> karaf@root()> $a2 2
> a
> karaf@root()> each ($a1 split " ") {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call
> karaf@root()> $a2
> karaf@root()> each ($a2) {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call{noformat}
> In both versions the split creates an array - but the shell does not seem to
> be automatically coerce $a2 into an array for v4.1.5
> This is breaking several scripts currently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5613) Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
[
https://issues.apache.org/jira/browse/KARAF-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368962#comment-16368962
]
Guillaume Nodet commented on KARAF-5613:
This small change has been introduced in gogo in order to support new features
such as:
{code:java}
karaf@root()> echo {1..2}
["1" "2"]
karaf@root()> echo a{1..2}b
["a1b" "a2b"]
{code}
So a closure needs to start with {{"{"}} followed by a space.
> Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
> -
>
> Key: KARAF-5613
> URL: https://issues.apache.org/jira/browse/KARAF-5613
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.5
>Reporter: Saikat Ghosh
>Assignee: Guillaume Nodet
>Priority: Major
> Labels: Scripting
>
> Scripting behavior has changed between Karaf v4.0.9 and v4.1.5
> *The following is a shell session for v4.0.10*
> {noformat}
> Apache Karaf (4.0.10)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> a2 = $a1 split " "
> This
> is
> a
> test
> karaf@root()> $a2 2
> a
> karaf@root()> $a2 3
> test
> karaf@root()> each ($a2) {echo $it}
> This
> is
> a
> test
> karaf@root()> each ($a1 split " ") {echo $it}
> This
> is
> a
> test{noformat}
> *The following is a shell session for v4.1.5*
> {noformat}
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> $a1
> This is a test
> karaf@root()> a2 = ($a1 split " ")
> karaf@root()> $a2 0
> This
> karaf@root()> $a2 1
> is
> karaf@root()> $a2 2
> a
> karaf@root()> each ($a1 split " ") {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call
> karaf@root()> $a2
> karaf@root()> each ($a2) {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call{noformat}
> In both versions the split creates an array - but the shell does not seem to
> be automatically coerce $a2 into an array for v4.1.5
> This is breaking several scripts currently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KARAF-5628) Corrupt gc.log due to unseparated VM settings
Rico Neubauer created KARAF-5628: Summary: Corrupt gc.log due to unseparated VM settings Key: KARAF-5628 URL: https://issues.apache.org/jira/browse/KARAF-5628 Project: Karaf Issue Type: Bug Components: karaf-core Reporter: Rico Neubauer The VM properties used for the start, stop, status and client scripts all use one common configuration of the VM properties, like Xmx and GC settings. This has one particular issue when activating the gc.log (-Xloggc:gc.log with Oracle-VM): Invoking e.g. status while Karaf is running, uses the same settings, thus points to the same file and corrupts it with NUL values (see here for details: [Stackoverflow|[https://stackoverflow.com/questions/8353401/garbage-collector-log-loggc-file-rotation-with-logrotate-does-not-work-properl]).] I would like to request the possibility to configure the VM properties for starting the instance independently from the maintenance scripts - due to the issue and also since e.g. running status with lots of heap (if instance is configured to it) is unneeded. Even making it broader, I think it would also make sense to be able to configure the settings completely, since currently some things are hard-coded in the scripts, like the _-Xdum_p and _-Xlp_ settings for AIX, where I personally would like to configure it to _-Xdump:heap:events=gpf,opts=PHD_, which is currently not possible using the configuration only. Also especially for AIX, there is _LDR_CNTRL=MAXDATA=0xB000@DSA_, which might not be desired when running with heaps larger than 3GB. If you agree on a separation, I would make a proposal as PR. Please let me know. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5627) Upgrade to PAX-JMS 0.2.0
[ https://issues.apache.org/jira/browse/KARAF-5627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368947#comment-16368947 ] ASF GitHub Bot commented on KARAF-5627: --- gnodet opened a new pull request #456: [KARAF-5627] Upgrade to PAX-JMS 0.2.0 URL: https://github.com/apache/karaf/pull/456 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Upgrade to PAX-JMS 0.2.0 > > > Key: KARAF-5627 > URL: https://issues.apache.org/jira/browse/KARAF-5627 > Project: Karaf > Issue Type: Improvement > Components: karaf-jms >Reporter: John Poth >Priority: Major > > Upgrade PAX-JMS to > [0.2.0|https://github.com/ops4j/org.ops4j.pax.jms/releases/tag/jms-0.2.0] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5627) Upgrade to PAX-JMS 0.2.0
John Poth created KARAF-5627: Summary: Upgrade to PAX-JMS 0.2.0 Key: KARAF-5627 URL: https://issues.apache.org/jira/browse/KARAF-5627 Project: Karaf Issue Type: Improvement Components: karaf-jms Reporter: John Poth Upgrade PAX-JMS to [0.2.0|https://github.com/ops4j/org.ops4j.pax.jms/releases/tag/jms-0.2.0] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KARAF-5601) Array values in configurations are printed as pointer addresses when using shell commands
[
https://issues.apache.org/jira/browse/KARAF-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368918#comment-16368918
]
Guillaume Nodet commented on KARAF-5601:
I've added a fix to actually display arrays correctly, but the edition can not
be fixed.
> Array values in configurations are printed as pointer addresses when using
> shell commands
> -
>
> Key: KARAF-5601
> URL: https://issues.apache.org/jira/browse/KARAF-5601
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.4
> Environment: OS X El Capitan 10.11.6
>Reporter: Steven Lombardi
>Assignee: Guillaume Nodet
>Priority: Minor
>
> To reproduce:
> * Start editing any configuration with an array-valued property using
> {{config:edit}}
> * Run {{config:property-list}} and notice that the array does not print
> correctly
> * Run {{config:property-get}} for the name of the array-valued property and
> notice the array does not print correctly
> Example:
> {code:java}
> admin@root()> config:property-list
>customMimeTypes = [Ljava.lang.String;@2b1de817
>felix.fileinstall.filename =
> file:/Users/lambeaux/Connexta/instances/ddf-2.11.5-SNAPSHOT/etc/DDF_Custom_Mime_Type_Resolver-xml.config
>
>name = XML Metacard Content Resolver
>priority = 10
>schema = urn:catalog:metacard
>service.factoryPid = DDF_Custom_Mime_Type_Resolver
>service.pid =
> DDF_Custom_Mime_Type_Resolver.e12a9162-e152-4a2d-bc7e-537d3621eac7
> admin@root()> config:property-get priority
> 10
> admin@root()> config:property-get schema
> urn:catalog:metacard
> admin@root()> config:property-get name
> XML Metacard Content Resolver
> admin@root()> config:property-get customMimeTypes
> [Ljava.lang.String;@2b1de817
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (KARAF-5601) Array values in configurations are printed as pointer addresses when using shell commands
[
https://issues.apache.org/jira/browse/KARAF-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet closed KARAF-5601.
--
Resolution: Won't Fix
> Array values in configurations are printed as pointer addresses when using
> shell commands
> -
>
> Key: KARAF-5601
> URL: https://issues.apache.org/jira/browse/KARAF-5601
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.4
> Environment: OS X El Capitan 10.11.6
>Reporter: Steven Lombardi
>Assignee: Guillaume Nodet
>Priority: Minor
>
> To reproduce:
> * Start editing any configuration with an array-valued property using
> {{config:edit}}
> * Run {{config:property-list}} and notice that the array does not print
> correctly
> * Run {{config:property-get}} for the name of the array-valued property and
> notice the array does not print correctly
> Example:
> {code:java}
> admin@root()> config:property-list
>customMimeTypes = [Ljava.lang.String;@2b1de817
>felix.fileinstall.filename =
> file:/Users/lambeaux/Connexta/instances/ddf-2.11.5-SNAPSHOT/etc/DDF_Custom_Mime_Type_Resolver-xml.config
>
>name = XML Metacard Content Resolver
>priority = 10
>schema = urn:catalog:metacard
>service.factoryPid = DDF_Custom_Mime_Type_Resolver
>service.pid =
> DDF_Custom_Mime_Type_Resolver.e12a9162-e152-4a2d-bc7e-537d3621eac7
> admin@root()> config:property-get priority
> 10
> admin@root()> config:property-get schema
> urn:catalog:metacard
> admin@root()> config:property-get name
> XML Metacard Content Resolver
> admin@root()> config:property-get customMimeTypes
> [Ljava.lang.String;@2b1de817
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5601) Array values in configurations are printed as pointer addresses when using shell commands
[
https://issues.apache.org/jira/browse/KARAF-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368878#comment-16368878
]
Jean-Baptiste Onofré commented on KARAF-5601:
-
Then, I propose to set this Jira as "Fixed" on 4.2.0. Thoughts ?
> Array values in configurations are printed as pointer addresses when using
> shell commands
> -
>
> Key: KARAF-5601
> URL: https://issues.apache.org/jira/browse/KARAF-5601
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.4
> Environment: OS X El Capitan 10.11.6
>Reporter: Steven Lombardi
>Assignee: Guillaume Nodet
>Priority: Minor
>
> To reproduce:
> * Start editing any configuration with an array-valued property using
> {{config:edit}}
> * Run {{config:property-list}} and notice that the array does not print
> correctly
> * Run {{config:property-get}} for the name of the array-valued property and
> notice the array does not print correctly
> Example:
> {code:java}
> admin@root()> config:property-list
>customMimeTypes = [Ljava.lang.String;@2b1de817
>felix.fileinstall.filename =
> file:/Users/lambeaux/Connexta/instances/ddf-2.11.5-SNAPSHOT/etc/DDF_Custom_Mime_Type_Resolver-xml.config
>
>name = XML Metacard Content Resolver
>priority = 10
>schema = urn:catalog:metacard
>service.factoryPid = DDF_Custom_Mime_Type_Resolver
>service.pid =
> DDF_Custom_Mime_Type_Resolver.e12a9162-e152-4a2d-bc7e-537d3621eac7
> admin@root()> config:property-get priority
> 10
> admin@root()> config:property-get schema
> urn:catalog:metacard
> admin@root()> config:property-get name
> XML Metacard Content Resolver
> admin@root()> config:property-get customMimeTypes
> [Ljava.lang.String;@2b1de817
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KARAF-5601) Array values in configurations are printed as pointer addresses when using shell commands
[
https://issues.apache.org/jira/browse/KARAF-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368873#comment-16368873
]
Guillaume Nodet edited comment on KARAF-5601 at 2/19/18 8:47 AM:
-
This has been fixed in 4.2 already and can not easily be backported as the
problem is not in the display of the value, but rather in setting / storing the
typed value.
was (Author: gnt):
This has been fixed in 4.2 already and can not easily be backported.
> Array values in configurations are printed as pointer addresses when using
> shell commands
> -
>
> Key: KARAF-5601
> URL: https://issues.apache.org/jira/browse/KARAF-5601
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.4
> Environment: OS X El Capitan 10.11.6
>Reporter: Steven Lombardi
>Assignee: Guillaume Nodet
>Priority: Minor
>
> To reproduce:
> * Start editing any configuration with an array-valued property using
> {{config:edit}}
> * Run {{config:property-list}} and notice that the array does not print
> correctly
> * Run {{config:property-get}} for the name of the array-valued property and
> notice the array does not print correctly
> Example:
> {code:java}
> admin@root()> config:property-list
>customMimeTypes = [Ljava.lang.String;@2b1de817
>felix.fileinstall.filename =
> file:/Users/lambeaux/Connexta/instances/ddf-2.11.5-SNAPSHOT/etc/DDF_Custom_Mime_Type_Resolver-xml.config
>
>name = XML Metacard Content Resolver
>priority = 10
>schema = urn:catalog:metacard
>service.factoryPid = DDF_Custom_Mime_Type_Resolver
>service.pid =
> DDF_Custom_Mime_Type_Resolver.e12a9162-e152-4a2d-bc7e-537d3621eac7
> admin@root()> config:property-get priority
> 10
> admin@root()> config:property-get schema
> urn:catalog:metacard
> admin@root()> config:property-get name
> XML Metacard Content Resolver
> admin@root()> config:property-get customMimeTypes
> [Ljava.lang.String;@2b1de817
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (KARAF-5601) Array values in configurations are printed as pointer addresses when using shell commands
[
https://issues.apache.org/jira/browse/KARAF-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368873#comment-16368873
]
Guillaume Nodet edited comment on KARAF-5601 at 2/19/18 8:44 AM:
-
This has been fixed in 4.2 already and can not easily be backported.
was (Author: gnt):
This has been fixed in 4.2 already and need to be backported.
> Array values in configurations are printed as pointer addresses when using
> shell commands
> -
>
> Key: KARAF-5601
> URL: https://issues.apache.org/jira/browse/KARAF-5601
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.4
> Environment: OS X El Capitan 10.11.6
>Reporter: Steven Lombardi
>Assignee: Guillaume Nodet
>Priority: Minor
>
> To reproduce:
> * Start editing any configuration with an array-valued property using
> {{config:edit}}
> * Run {{config:property-list}} and notice that the array does not print
> correctly
> * Run {{config:property-get}} for the name of the array-valued property and
> notice the array does not print correctly
> Example:
> {code:java}
> admin@root()> config:property-list
>customMimeTypes = [Ljava.lang.String;@2b1de817
>felix.fileinstall.filename =
> file:/Users/lambeaux/Connexta/instances/ddf-2.11.5-SNAPSHOT/etc/DDF_Custom_Mime_Type_Resolver-xml.config
>
>name = XML Metacard Content Resolver
>priority = 10
>schema = urn:catalog:metacard
>service.factoryPid = DDF_Custom_Mime_Type_Resolver
>service.pid =
> DDF_Custom_Mime_Type_Resolver.e12a9162-e152-4a2d-bc7e-537d3621eac7
> admin@root()> config:property-get priority
> 10
> admin@root()> config:property-get schema
> urn:catalog:metacard
> admin@root()> config:property-get name
> XML Metacard Content Resolver
> admin@root()> config:property-get customMimeTypes
> [Ljava.lang.String;@2b1de817
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KARAF-5601) Array values in configurations are printed as pointer addresses when using shell commands
[
https://issues.apache.org/jira/browse/KARAF-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned KARAF-5601:
--
Assignee: Guillaume Nodet (was: Jean-Baptiste Onofré)
> Array values in configurations are printed as pointer addresses when using
> shell commands
> -
>
> Key: KARAF-5601
> URL: https://issues.apache.org/jira/browse/KARAF-5601
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.4
> Environment: OS X El Capitan 10.11.6
>Reporter: Steven Lombardi
>Assignee: Guillaume Nodet
>Priority: Minor
>
> To reproduce:
> * Start editing any configuration with an array-valued property using
> {{config:edit}}
> * Run {{config:property-list}} and notice that the array does not print
> correctly
> * Run {{config:property-get}} for the name of the array-valued property and
> notice the array does not print correctly
> Example:
> {code:java}
> admin@root()> config:property-list
>customMimeTypes = [Ljava.lang.String;@2b1de817
>felix.fileinstall.filename =
> file:/Users/lambeaux/Connexta/instances/ddf-2.11.5-SNAPSHOT/etc/DDF_Custom_Mime_Type_Resolver-xml.config
>
>name = XML Metacard Content Resolver
>priority = 10
>schema = urn:catalog:metacard
>service.factoryPid = DDF_Custom_Mime_Type_Resolver
>service.pid =
> DDF_Custom_Mime_Type_Resolver.e12a9162-e152-4a2d-bc7e-537d3621eac7
> admin@root()> config:property-get priority
> 10
> admin@root()> config:property-get schema
> urn:catalog:metacard
> admin@root()> config:property-get name
> XML Metacard Content Resolver
> admin@root()> config:property-get customMimeTypes
> [Ljava.lang.String;@2b1de817
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5601) Array values in configurations are printed as pointer addresses when using shell commands
[
https://issues.apache.org/jira/browse/KARAF-5601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368873#comment-16368873
]
Guillaume Nodet commented on KARAF-5601:
This has been fixed in 4.2 already and need to be backported.
> Array values in configurations are printed as pointer addresses when using
> shell commands
> -
>
> Key: KARAF-5601
> URL: https://issues.apache.org/jira/browse/KARAF-5601
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.4
> Environment: OS X El Capitan 10.11.6
>Reporter: Steven Lombardi
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> To reproduce:
> * Start editing any configuration with an array-valued property using
> {{config:edit}}
> * Run {{config:property-list}} and notice that the array does not print
> correctly
> * Run {{config:property-get}} for the name of the array-valued property and
> notice the array does not print correctly
> Example:
> {code:java}
> admin@root()> config:property-list
>customMimeTypes = [Ljava.lang.String;@2b1de817
>felix.fileinstall.filename =
> file:/Users/lambeaux/Connexta/instances/ddf-2.11.5-SNAPSHOT/etc/DDF_Custom_Mime_Type_Resolver-xml.config
>
>name = XML Metacard Content Resolver
>priority = 10
>schema = urn:catalog:metacard
>service.factoryPid = DDF_Custom_Mime_Type_Resolver
>service.pid =
> DDF_Custom_Mime_Type_Resolver.e12a9162-e152-4a2d-bc7e-537d3621eac7
> admin@root()> config:property-get priority
> 10
> admin@root()> config:property-get schema
> urn:catalog:metacard
> admin@root()> config:property-get name
> XML Metacard Content Resolver
> admin@root()> config:property-get customMimeTypes
> [Ljava.lang.String;@2b1de817
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5613) Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
[
https://issues.apache.org/jira/browse/KARAF-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368868#comment-16368868
]
Guillaume Nodet commented on KARAF-5613:
The actual problem is not on the array conversion, but the closure parsing.
Try the following:
{code:java}
karaf@root()> each ($a1 split " ") { echo $it }
This
is
a
test{code}
Note the space after the opening bracket of the closure argument.
> Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
> -
>
> Key: KARAF-5613
> URL: https://issues.apache.org/jira/browse/KARAF-5613
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.5
>Reporter: Saikat Ghosh
>Assignee: Guillaume Nodet
>Priority: Major
> Labels: Scripting
>
> Scripting behavior has changed between Karaf v4.0.9 and v4.1.5
> *The following is a shell session for v4.0.10*
> {noformat}
> Apache Karaf (4.0.10)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> a2 = $a1 split " "
> This
> is
> a
> test
> karaf@root()> $a2 2
> a
> karaf@root()> $a2 3
> test
> karaf@root()> each ($a2) {echo $it}
> This
> is
> a
> test
> karaf@root()> each ($a1 split " ") {echo $it}
> This
> is
> a
> test{noformat}
> *The following is a shell session for v4.1.5*
> {noformat}
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> $a1
> This is a test
> karaf@root()> a2 = ($a1 split " ")
> karaf@root()> $a2 0
> This
> karaf@root()> $a2 1
> is
> karaf@root()> $a2 2
> a
> karaf@root()> each ($a1 split " ") {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call
> karaf@root()> $a2
> karaf@root()> each ($a2) {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call{noformat}
> In both versions the split creates an array - but the shell does not seem to
> be automatically coerce $a2 into an array for v4.1.5
> This is breaking several scripts currently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KARAF-5613) Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
[
https://issues.apache.org/jira/browse/KARAF-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned KARAF-5613:
--
Assignee: Guillaume Nodet (was: Jean-Baptiste Onofré)
> Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
> -
>
> Key: KARAF-5613
> URL: https://issues.apache.org/jira/browse/KARAF-5613
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.5
>Reporter: Saikat Ghosh
>Assignee: Guillaume Nodet
>Priority: Major
> Labels: Scripting
>
> Scripting behavior has changed between Karaf v4.0.9 and v4.1.5
> *The following is a shell session for v4.0.10*
> {noformat}
> Apache Karaf (4.0.10)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> a2 = $a1 split " "
> This
> is
> a
> test
> karaf@root()> $a2 2
> a
> karaf@root()> $a2 3
> test
> karaf@root()> each ($a2) {echo $it}
> This
> is
> a
> test
> karaf@root()> each ($a1 split " ") {echo $it}
> This
> is
> a
> test{noformat}
> *The following is a shell session for v4.1.5*
> {noformat}
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> $a1
> This is a test
> karaf@root()> a2 = ($a1 split " ")
> karaf@root()> $a2 0
> This
> karaf@root()> $a2 1
> is
> karaf@root()> $a2 2
> a
> karaf@root()> each ($a1 split " ") {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call
> karaf@root()> $a2
> karaf@root()> each ($a2) {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call{noformat}
> In both versions the split creates an array - but the shell does not seem to
> be automatically coerce $a2 into an array for v4.1.5
> This is breaking several scripts currently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (KARAF-5613) Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
[
https://issues.apache.org/jira/browse/KARAF-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368856#comment-16368856
]
Guillaume Nodet commented on KARAF-5613:
I'm not sure the change is expected, I rather see it as a regression. I'll
check why the behavior has changed in gogo.
> Scripting Behaviour changed from Karaf 4.0.9 to 4.1.5
> -
>
> Key: KARAF-5613
> URL: https://issues.apache.org/jira/browse/KARAF-5613
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 4.1.5
>Reporter: Saikat Ghosh
>Assignee: Jean-Baptiste Onofré
>Priority: Major
> Labels: Scripting
>
> Scripting behavior has changed between Karaf v4.0.9 and v4.1.5
> *The following is a shell session for v4.0.10*
> {noformat}
> Apache Karaf (4.0.10)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> a2 = $a1 split " "
> This
> is
> a
> test
> karaf@root()> $a2 2
> a
> karaf@root()> $a2 3
> test
> karaf@root()> each ($a2) {echo $it}
> This
> is
> a
> test
> karaf@root()> each ($a1 split " ") {echo $it}
> This
> is
> a
> test{noformat}
> *The following is a shell session for v4.1.5*
> {noformat}
> karaf@root()> a1 = "This is a test"
> This is a test
> karaf@root()> $a1
> This is a test
> karaf@root()> a2 = ($a1 split " ")
> karaf@root()> $a2 0
> This
> karaf@root()> $a2 1
> is
> karaf@root()> $a2 2
> a
> karaf@root()> each ($a1 split " ") {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call
> karaf@root()> $a2
> karaf@root()> each ($a2) {echo $it}
> usage: each elements { closure }
> elements: an array to iterate on
> closure: a function or closure to call{noformat}
> In both versions the split creates an array - but the shell does not seem to
> be automatically coerce $a2 into an array for v4.1.5
> This is breaking several scripts currently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (KARAF-5618) Upgrade to Aries JMX Blueprint 1.2.0
[ https://issues.apache.org/jira/browse/KARAF-5618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5618: Summary: Upgrade to Aries JMX Blueprint 1.2.0 (was: Upgrade to Aries Blueprint 1.2.0) > Upgrade to Aries JMX Blueprint 1.2.0 > > > Key: KARAF-5618 > URL: https://issues.apache.org/jira/browse/KARAF-5618 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5626) Double check Pax JDBC & Pax JMS behavior
[ https://issues.apache.org/jira/browse/KARAF-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5626: Description: Some users reported some slightly different behavior in the shell commands, DataSource & ConnectionFactory since we integrate Pax JDBC & Pax JMS. I would like to double check if all behaves correctly. (was: As we did with Pax JDBC, Karaf should leverage Pax JMS to create and manage ConnectionFactory.) > Double check Pax JDBC & Pax JMS behavior > > > Key: KARAF-5626 > URL: https://issues.apache.org/jira/browse/KARAF-5626 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-jms >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > > Some users reported some slightly different behavior in the shell commands, > DataSource & ConnectionFactory since we integrate Pax JDBC & Pax JMS. I would > like to double check if all behaves correctly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5626) Double check Pax JDBC & Pax JMS behavior
[ https://issues.apache.org/jira/browse/KARAF-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5626: Issue Type: Task (was: Dependency upgrade) > Double check Pax JDBC & Pax JMS behavior > > > Key: KARAF-5626 > URL: https://issues.apache.org/jira/browse/KARAF-5626 > Project: Karaf > Issue Type: Task > Components: karaf-jms >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > > Some users reported some slightly different behavior in the shell commands, > DataSource & ConnectionFactory since we integrate Pax JDBC & Pax JMS. I would > like to double check if all behaves correctly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KARAF-5626) Double check Pax JDBC & Pax JMS behavior
[ https://issues.apache.org/jira/browse/KARAF-5626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5626: Summary: Double check Pax JDBC & Pax JMS behavior (was: Leverage Pax JMS) > Double check Pax JDBC & Pax JMS behavior > > > Key: KARAF-5626 > URL: https://issues.apache.org/jira/browse/KARAF-5626 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-jms >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Major > Fix For: 4.2.0 > > > As we did with Pax JDBC, Karaf should leverage Pax JMS to create and manage > ConnectionFactory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KARAF-5626) Leverage Pax JMS
Jean-Baptiste Onofré created KARAF-5626: --- Summary: Leverage Pax JMS Key: KARAF-5626 URL: https://issues.apache.org/jira/browse/KARAF-5626 Project: Karaf Issue Type: Dependency upgrade Components: karaf-jms Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.2.0 As we did with Pax JDBC, Karaf should leverage Pax JMS to create and manage ConnectionFactory. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
