[jira] [Commented] (KARAF-5425) ArrayIndexOutOfBoundsException running history | grep

2017-10-13 Thread Guillaume Nodet (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204280#comment-16204280
 ] 

Guillaume Nodet commented on KARAF-5425:


I think the problem is a regression caused by 
https://github.com/apache/felix/commit/e1c4bafb9c01e634bdbcdad4b7e0a7d2e84c9222#diff-8298c21ad9b65385ab8671829ca2a817

> ArrayIndexOutOfBoundsException running history | grep
> -
>
> Key: KARAF-5425
> URL: https://issues.apache.org/jira/browse/KARAF-5425
> Project: Karaf
>  Issue Type: Bug
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>
> {code}
> karaf@root()> history | grep cave
> grep: java.lang.ArrayIndexOutOfBoundsException: 29
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5420) Bad console behavior when dealing with the input stream with the exec command

2017-10-13 Thread Guillaume Nodet (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204279#comment-16204279
 ] 

Guillaume Nodet commented on KARAF-5420:


It's not. I've raised KARAF-5425 for this problem.

> Bad console behavior when dealing with the input stream with the exec command
> -
>
> Key: KARAF-5420
> URL: https://issues.apache.org/jira/browse/KARAF-5420
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.2.0
>
>
> The following command behaves correctly:
> {code}
> echo foo | grep o
> {code}
> However, the following one never ends:
> {code}
> echo foo | exec grep o
> {code}
> The following ones also behaves incorrectly (enter does not print a new line, 
> and Ctrl+C / Ctrl+D are not handled correctly) :
> {code}
> grep o
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (KARAF-5425) ArrayIndexOutOfBoundsException running history | grep

2017-10-13 Thread Guillaume Nodet (JIRA) 
Guillaume Nodet created KARAF-5425:
--

 Summary: ArrayIndexOutOfBoundsException running history | grep
 Key: KARAF-5425
 URL: https://issues.apache.org/jira/browse/KARAF-5425
 Project: Karaf
  Issue Type: Bug
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet


{code}
karaf@root()> history | grep cave
grep: java.lang.ArrayIndexOutOfBoundsException: 29
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (KARAF-5063) Karaf shutdowns when '<' or '>' typed in shell

2017-10-13 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet reassigned KARAF-5063:
--

Assignee: Guillaume Nodet

> Karaf shutdowns when '<' or '>' typed in shell
> --
>
> Key: KARAF-5063
> URL: https://issues.apache.org/jira/browse/KARAF-5063
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Dominik Przybysz
>Assignee: Guillaume Nodet
>
> I start karaf and type '<':
> {code}
> bash$ ./bin/karaf 
> __ __    
>/ //_/ __ _/ __/  
>   / ,<  / __ `/ ___/ __ `/ /_
>  / /| |/ /_/ / /  / /_/ / __/
> /_/ |_|\__,_/_/   \__,_/_/ 
>   Apache Karaf (4.1.0)
> 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()> Error executing command: 2  
>   
>   
> bash$
> {code}
> and karaf shutdowns.
> Exception from karaf.log:
> {code}
> 2017-03-25T09:51:28,472 | ERROR | Karaf local console user karaf | ShellUtil  
>   | 43 - org.apache.karaf.shell.core - 4.1.0 | Exception 
> caught while executing command
> java.lang.ArrayIndexOutOfBoundsException: 2
> at org.apache.felix.gogo.runtime.Token.charAt(Token.java:81) 
> [43:org.apache.karaf.shell.core:4.1.0]
> at java.util.regex.Pattern$Slice.match(Pattern.java:3969) [?:?]
> at java.util.regex.Pattern$Branch.match(Pattern.java:4604) [?:?]
> at java.util.regex.Matcher.match(Matcher.java:1270) [?:?]
> at java.util.regex.Matcher.matches(Matcher.java:604) [?:?]
> at org.apache.felix.gogo.runtime.Tokenizer.next(Tokenizer.java:111) 
> [43:org.apache.karaf.shell.core:4.1.0]
> at org.apache.felix.gogo.runtime.Parser.next(Parser.java:284) 
> [43:org.apache.karaf.shell.core:4.1.0]
> at org.apache.felix.gogo.runtime.Parser.program(Parser.java:202) 
> [43:org.apache.karaf.shell.core:4.1.0]
> at 
> org.apache.felix.gogo.jline.Highlighter.highlight(Highlighter.java:58) 
> [43:org.apache.karaf.shell.core:4.1.0]
> at 
> org.jline.reader.impl.LineReaderImpl.getDisplayedBufferWithPrompts(LineReaderImpl.java:3263)
>  [50:org.jline:3.1.3]
> at 
> org.jline.reader.impl.LineReaderImpl.redisplay(LineReaderImpl.java:3203) 
> [50:org.jline:3.1.3]
> at 
> org.jline.reader.impl.LineReaderImpl.cleanup(LineReaderImpl.java:2180) 
> [50:org.jline:3.1.3]
> at 
> org.jline.reader.impl.LineReaderImpl.readLine(LineReaderImpl.java:570) 
> [50:org.jline:3.1.3]
> at 
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:332)
>  [43:org.apache.karaf.shell.core:4.1.0]
> at java.lang.Thread.run(Thread.java:745) [?:?]
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (KARAF-5423) Karaf is flagged as vulnerable to CVE-2015-5262

2017-10-13 Thread Achim Nierbeck (JIRA) 

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

Achim Nierbeck resolved KARAF-5423.
---
Resolution: Fixed

> Karaf is flagged as vulnerable to CVE-2015-5262
> ---
>
> Key: KARAF-5423
> URL: https://issues.apache.org/jira/browse/KARAF-5423
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.2
>Reporter: Fabian Lange
>Assignee: Achim Nierbeck
> Fix For: 4.2.0, 4.1.3
>
>
> Pax Url up to the current 2.5.2 include apache httpclient 4.3.5 which is 
> flagged vulnerable to CVE-2015-5262.
> I already provided a patch upstream 
> https://ops4j1.jira.com/projects/PAXURL/issues/PAXURL-345?filter=allopenissues
> in 
> https://github.com/ops4j/org.ops4j.pax.url/commit/6f938ab159c606c45ec293c116aad41b6cf62510
> but it would require a pax-url release first followed by a dependency upgrade 
> in karaf.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5423) Karaf is flagged as vulnerable to CVE-2015-5262

2017-10-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204206#comment-16204206
 ] 

ASF subversion and git services commented on KARAF-5423:


Commit b7139523b1bad1ebecde77cf65a7381bc40fc157 in karaf's branch 
refs/heads/karaf-4.1.x from [~achim_nierbeck]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=b713952 ]

[KARAF-5423] - Karaf is flagged as vulnerable to CVE-2015-5262


> Karaf is flagged as vulnerable to CVE-2015-5262
> ---
>
> Key: KARAF-5423
> URL: https://issues.apache.org/jira/browse/KARAF-5423
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.2
>Reporter: Fabian Lange
>Assignee: Achim Nierbeck
> Fix For: 4.2.0, 4.1.3
>
>
> Pax Url up to the current 2.5.2 include apache httpclient 4.3.5 which is 
> flagged vulnerable to CVE-2015-5262.
> I already provided a patch upstream 
> https://ops4j1.jira.com/projects/PAXURL/issues/PAXURL-345?filter=allopenissues
> in 
> https://github.com/ops4j/org.ops4j.pax.url/commit/6f938ab159c606c45ec293c116aad41b6cf62510
> but it would require a pax-url release first followed by a dependency upgrade 
> in karaf.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5423) Karaf is flagged as vulnerable to CVE-2015-5262

2017-10-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204207#comment-16204207
 ] 

ASF subversion and git services commented on KARAF-5423:


Commit fc7af0b0ca3cbaa75c01e9e1ff7529586c373b9c in karaf's branch 
refs/heads/master from [~achim_nierbeck]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=fc7af0b ]

[KARAF-5423] - Karaf is flagged as vulnerable to CVE-2015-5262


> Karaf is flagged as vulnerable to CVE-2015-5262
> ---
>
> Key: KARAF-5423
> URL: https://issues.apache.org/jira/browse/KARAF-5423
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.2
>Reporter: Fabian Lange
>Assignee: Achim Nierbeck
> Fix For: 4.2.0, 4.1.3
>
>
> Pax Url up to the current 2.5.2 include apache httpclient 4.3.5 which is 
> flagged vulnerable to CVE-2015-5262.
> I already provided a patch upstream 
> https://ops4j1.jira.com/projects/PAXURL/issues/PAXURL-345?filter=allopenissues
> in 
> https://github.com/ops4j/org.ops4j.pax.url/commit/6f938ab159c606c45ec293c116aad41b6cf62510
> but it would require a pax-url release first followed by a dependency upgrade 
> in karaf.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KARAF-5423) Karaf is flagged as vulnerable to CVE-2015-5262

2017-10-13 Thread Achim Nierbeck (JIRA) 

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

Achim Nierbeck updated KARAF-5423:
--
Fix Version/s: 4.1.3

> Karaf is flagged as vulnerable to CVE-2015-5262
> ---
>
> Key: KARAF-5423
> URL: https://issues.apache.org/jira/browse/KARAF-5423
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.2
>Reporter: Fabian Lange
>Assignee: Achim Nierbeck
> Fix For: 4.2.0, 4.1.3
>
>
> Pax Url up to the current 2.5.2 include apache httpclient 4.3.5 which is 
> flagged vulnerable to CVE-2015-5262.
> I already provided a patch upstream 
> https://ops4j1.jira.com/projects/PAXURL/issues/PAXURL-345?filter=allopenissues
> in 
> https://github.com/ops4j/org.ops4j.pax.url/commit/6f938ab159c606c45ec293c116aad41b6cf62510
> but it would require a pax-url release first followed by a dependency upgrade 
> in karaf.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KARAF-5423) Karaf is flagged as vulnerable to CVE-2015-5262

2017-10-13 Thread Achim Nierbeck (JIRA) 

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

Achim Nierbeck updated KARAF-5423:
--
Fix Version/s: 4.2.0

> Karaf is flagged as vulnerable to CVE-2015-5262
> ---
>
> Key: KARAF-5423
> URL: https://issues.apache.org/jira/browse/KARAF-5423
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.2
>Reporter: Fabian Lange
>Assignee: Achim Nierbeck
> Fix For: 4.2.0
>
>
> Pax Url up to the current 2.5.2 include apache httpclient 4.3.5 which is 
> flagged vulnerable to CVE-2015-5262.
> I already provided a patch upstream 
> https://ops4j1.jira.com/projects/PAXURL/issues/PAXURL-345?filter=allopenissues
> in 
> https://github.com/ops4j/org.ops4j.pax.url/commit/6f938ab159c606c45ec293c116aad41b6cf62510
> but it would require a pax-url release first followed by a dependency upgrade 
> in karaf.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (KARAF-5423) Karaf is flagged as vulnerable to CVE-2015-5262

2017-10-13 Thread Achim Nierbeck (JIRA) 

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

Achim Nierbeck reassigned KARAF-5423:
-

Assignee: Achim Nierbeck

> Karaf is flagged as vulnerable to CVE-2015-5262
> ---
>
> Key: KARAF-5423
> URL: https://issues.apache.org/jira/browse/KARAF-5423
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.2
>Reporter: Fabian Lange
>Assignee: Achim Nierbeck
>
> Pax Url up to the current 2.5.2 include apache httpclient 4.3.5 which is 
> flagged vulnerable to CVE-2015-5262.
> I already provided a patch upstream 
> https://ops4j1.jira.com/projects/PAXURL/issues/PAXURL-345?filter=allopenissues
> in 
> https://github.com/ops4j/org.ops4j.pax.url/commit/6f938ab159c606c45ec293c116aad41b6cf62510
> but it would require a pax-url release first followed by a dependency upgrade 
> in karaf.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (KARAF-5423) Karaf is flagged as vulnerable to CVE-2015-5262

2017-10-13 Thread Achim Nierbeck (JIRA) 

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

Work on KARAF-5423 started by Achim Nierbeck.
-
> Karaf is flagged as vulnerable to CVE-2015-5262
> ---
>
> Key: KARAF-5423
> URL: https://issues.apache.org/jira/browse/KARAF-5423
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.2
>Reporter: Fabian Lange
>Assignee: Achim Nierbeck
>
> Pax Url up to the current 2.5.2 include apache httpclient 4.3.5 which is 
> flagged vulnerable to CVE-2015-5262.
> I already provided a patch upstream 
> https://ops4j1.jira.com/projects/PAXURL/issues/PAXURL-345?filter=allopenissues
> in 
> https://github.com/ops4j/org.ops4j.pax.url/commit/6f938ab159c606c45ec293c116aad41b6cf62510
> but it would require a pax-url release first followed by a dependency upgrade 
> in karaf.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5420) Bad console behavior when dealing with the input stream with the exec command

2017-10-13 Thread Francois Papon (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203876#comment-16203876
 ] 

Francois Papon commented on KARAF-5420:
---

Hi,

This command don't work, I don't know if it's related to this issue :

{code:java}
karaf@root()> history | grep cave
grep: java.lang.ArrayIndexOutOfBoundsException: 29
{code}

But this command work's :

{code:java}
karaf@root()> history | exec grep cave
  1149  feature:repo add cave
  1150  feature:repo-add cave
  1151  feature:install cave-server
  1152  feature:install cave-storage
{code}

*grep* work's only with *exec* after *history* 

However, *grep* work's without exec with *feature:list*

{code:java}
karaf@root()> feature:list | grep -i cave   

  
cave-server │ 4.0.1.SNAPSHOT   │ x│ Started │ 
karaf-cave-4.0.1-SNAPSHOT │
cave-storage│ 4.0.1.SNAPSHOT   │  │ Started │ 
karaf-cave-4.0.1-SNAPSHOT │
{code}

Tested on SNAPSHOT from Jenkins : apache-karaf-4.2.0-20171012.141014-387



> Bad console behavior when dealing with the input stream with the exec command
> -
>
> Key: KARAF-5420
> URL: https://issues.apache.org/jira/browse/KARAF-5420
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.2.0
>
>
> The following command behaves correctly:
> {code}
> echo foo | grep o
> {code}
> However, the following one never ends:
> {code}
> echo foo | exec grep o
> {code}
> The following ones also behaves incorrectly (enter does not print a new line, 
> and Ctrl+C / Ctrl+D are not handled correctly) :
> {code}
> grep o
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (KARAF-5414) Features mentioned in feature.xml stubs aren't taken into account in dependency calculations

2017-10-13 Thread Stephen Kitt (JIRA) 

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

Stephen Kitt resolved KARAF-5414.
-
   Resolution: Fixed
Fix Version/s: 4.0.11
   4.1.3
   4.2.0

> Features mentioned in feature.xml stubs aren't taken into account in 
> dependency calculations
> 
>
> Key: KARAF-5414
> URL: https://issues.apache.org/jira/browse/KARAF-5414
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.2, 4.0.10
>Reporter: Stephen Kitt
>Assignee: Stephen Kitt
> Fix For: 4.2.0, 4.1.3, 4.0.11
>
>
> When features dependencies are defined in a feature.xml stub, the feature 
> isn't taken into account for bundle dependency calculations in the feature 
> generator, even if the corresponding Maven dependency is specified in the 
> POM. This means that bundles defined in the feature that's depended upon are 
> repeated in the generated downstream feature.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5414) Features mentioned in feature.xml stubs aren't taken into account in dependency calculations

2017-10-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203680#comment-16203680
 ] 

ASF subversion and git services commented on KARAF-5414:


Commit d4c9456c5dee06d43e752608de89f6bff230ad50 in karaf's branch 
refs/heads/karaf-4.1.x from [~skitt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=d4c9456 ]

[KARAF-5414] Handle varying feature dependency versions

When a feature stub specifies a feature dependency, and the POM
contains a slight variant of the dependency (e.g., the former
specifies a version range, the latter specifies a single version), we
currently ignore the latter when resolving the former. This patch
changes the behaviour so that feature dependencies are matched more
generously, which allows dependency information to be correctly
analysed.

Signed-off-by: Stephen Kitt 
(cherry picked from commit 226f9e8ed087c57b4ace236cb3fcc578a2720401)


> Features mentioned in feature.xml stubs aren't taken into account in 
> dependency calculations
> 
>
> Key: KARAF-5414
> URL: https://issues.apache.org/jira/browse/KARAF-5414
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.2, 4.0.10
>Reporter: Stephen Kitt
>Assignee: Stephen Kitt
>
> When features dependencies are defined in a feature.xml stub, the feature 
> isn't taken into account for bundle dependency calculations in the feature 
> generator, even if the corresponding Maven dependency is specified in the 
> POM. This means that bundles defined in the feature that's depended upon are 
> repeated in the generated downstream feature.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5414) Features mentioned in feature.xml stubs aren't taken into account in dependency calculations

2017-10-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203681#comment-16203681
 ] 

ASF subversion and git services commented on KARAF-5414:


Commit 4dca9d73400e1ad4e911e9f50e3d927fb3a42fc4 in karaf's branch 
refs/heads/karaf-4.0.x from [~skitt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=4dca9d7 ]

[KARAF-5414] Handle varying feature dependency versions

When a feature stub specifies a feature dependency, and the POM
contains a slight variant of the dependency (e.g., the former
specifies a version range, the latter specifies a single version), we
currently ignore the latter when resolving the former. This patch
changes the behaviour so that feature dependencies are matched more
generously, which allows dependency information to be correctly
analysed.

Signed-off-by: Stephen Kitt 
(cherry picked from commit 226f9e8ed087c57b4ace236cb3fcc578a2720401)


> Features mentioned in feature.xml stubs aren't taken into account in 
> dependency calculations
> 
>
> Key: KARAF-5414
> URL: https://issues.apache.org/jira/browse/KARAF-5414
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.2, 4.0.10
>Reporter: Stephen Kitt
>Assignee: Stephen Kitt
>
> When features dependencies are defined in a feature.xml stub, the feature 
> isn't taken into account for bundle dependency calculations in the feature 
> generator, even if the corresponding Maven dependency is specified in the 
> POM. This means that bundles defined in the feature that's depended upon are 
> repeated in the generated downstream feature.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5414) Features mentioned in feature.xml stubs aren't taken into account in dependency calculations

2017-10-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203672#comment-16203672
 ] 

ASF subversion and git services commented on KARAF-5414:


Commit 226f9e8ed087c57b4ace236cb3fcc578a2720401 in karaf's branch 
refs/heads/master from [~skitt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=226f9e8 ]

[KARAF-5414] Handle varying feature dependency versions

When a feature stub specifies a feature dependency, and the POM
contains a slight variant of the dependency (e.g., the former
specifies a version range, the latter specifies a single version), we
currently ignore the latter when resolving the former. This patch
changes the behaviour so that feature dependencies are matched more
generously, which allows dependency information to be correctly
analysed.

Signed-off-by: Stephen Kitt 


> Features mentioned in feature.xml stubs aren't taken into account in 
> dependency calculations
> 
>
> Key: KARAF-5414
> URL: https://issues.apache.org/jira/browse/KARAF-5414
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.2, 4.0.10
>Reporter: Stephen Kitt
>Assignee: Stephen Kitt
>
> When features dependencies are defined in a feature.xml stub, the feature 
> isn't taken into account for bundle dependency calculations in the feature 
> generator, even if the corresponding Maven dependency is specified in the 
> POM. This means that bundles defined in the feature that's depended upon are 
> repeated in the generated downstream feature.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KARAF-5262) Cellar: Bump to Kubernetes-client 2.5.6

2017-10-13 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet updated KARAF-5262:
---
Fix Version/s: (was: 4.2.0)
   cellar-4.1.1

> Cellar: Bump to Kubernetes-client 2.5.6
> ---
>
> Key: KARAF-5262
> URL: https://issues.apache.org/jira/browse/KARAF-5262
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: cellar-4.1.1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KARAF-5277) Cellar: Bump to Kubernetes-client 2.5.7

2017-10-13 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet updated KARAF-5277:
---
Fix Version/s: (was: 4.2.0)
   cellar-4.1.1

> Cellar: Bump to Kubernetes-client 2.5.7
> ---
>
> Key: KARAF-5277
> URL: https://issues.apache.org/jira/browse/KARAF-5277
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-core
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: cellar-4.1.1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KARAF-5261) Cellar: Upgrade to Hazelcast 3.8.3

2017-10-13 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet updated KARAF-5261:
---
Fix Version/s: (was: 4.2.0)
   cellar-4.1.1

> Cellar: Upgrade to Hazelcast 3.8.3
> --
>
> Key: KARAF-5261
> URL: https://issues.apache.org/jira/browse/KARAF-5261
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: cellar-hazelcast
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: cellar-4.1.1
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (KARAF-5403) Karaf tooling doesn't keep ordering of features given in configuration

2017-10-13 Thread JIRA 

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

Łukasz Dywicki updated KARAF-5403:
--
Fix Version/s: 4.0.11

> Karaf tooling doesn't keep ordering of features given in configuration
> --
>
> Key: KARAF-5403
> URL: https://issues.apache.org/jira/browse/KARAF-5403
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.8
>Reporter: Łukasz Dywicki
>Assignee: Łukasz Dywicki
> Fix For: 4.0.11
>
>
> Even if in properly designed modular system order of start list of bundles 
> should not matter (as start level is sorting factor) for maintainability of 
> configurations and ease of use fature order given in maven plugin 
> configurations should be preserved as much as possible.
> Currently Karaf Assembly Builder does use hashing collections which do not 
> preserve insertion order leading to randomization of boot features and 
> repositories.
> Solving this issue will make potential modification of boot features easier 
> with scripts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5403) Karaf tooling doesn't keep ordering of features given in configuration

2017-10-13 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/KARAF-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203339#comment-16203339
 ] 

Łukasz Dywicki commented on KARAF-5403:
---

Patched 4.0.x branch, still need to rebase commit over latest 4.1.x.

> Karaf tooling doesn't keep ordering of features given in configuration
> --
>
> Key: KARAF-5403
> URL: https://issues.apache.org/jira/browse/KARAF-5403
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.8
>Reporter: Łukasz Dywicki
>Assignee: Łukasz Dywicki
>
> Even if in properly designed modular system order of start list of bundles 
> should not matter (as start level is sorting factor) for maintainability of 
> configurations and ease of use fature order given in maven plugin 
> configurations should be preserved as much as possible.
> Currently Karaf Assembly Builder does use hashing collections which do not 
> preserve insertion order leading to randomization of boot features and 
> repositories.
> Solving this issue will make potential modification of boot features easier 
> with scripts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5403) Karaf tooling doesn't keep ordering of features given in configuration

2017-10-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203325#comment-16203325
 ] 

ASF subversion and git services commented on KARAF-5403:


Commit 51f34067365d72fd853b85ff8b8fd858326871d3 in karaf's branch 
refs/heads/karaf-4.0.x from [~splatch]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=51f3406 ]

KARAF-5403 Fix for loosing order of features given in tooling configuration.


> Karaf tooling doesn't keep ordering of features given in configuration
> --
>
> Key: KARAF-5403
> URL: https://issues.apache.org/jira/browse/KARAF-5403
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.8
>Reporter: Łukasz Dywicki
>Assignee: Łukasz Dywicki
>
> Even if in properly designed modular system order of start list of bundles 
> should not matter (as start level is sorting factor) for maintainability of 
> configurations and ease of use fature order given in maven plugin 
> configurations should be preserved as much as possible.
> Currently Karaf Assembly Builder does use hashing collections which do not 
> preserve insertion order leading to randomization of boot features and 
> repositories.
> Solving this issue will make potential modification of boot features easier 
> with scripts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5403) Karaf tooling doesn't keep ordering of features given in configuration

2017-10-13 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203326#comment-16203326
 ] 

ASF GitHub Bot commented on KARAF-5403:
---

Github user asfgit closed the pull request at:

https://github.com/apache/karaf/pull/380


> Karaf tooling doesn't keep ordering of features given in configuration
> --
>
> Key: KARAF-5403
> URL: https://issues.apache.org/jira/browse/KARAF-5403
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.8
>Reporter: Łukasz Dywicki
>Assignee: Łukasz Dywicki
>
> Even if in properly designed modular system order of start list of bundles 
> should not matter (as start level is sorting factor) for maintainability of 
> configurations and ease of use fature order given in maven plugin 
> configurations should be preserved as much as possible.
> Currently Karaf Assembly Builder does use hashing collections which do not 
> preserve insertion order leading to randomization of boot features and 
> repositories.
> Solving this issue will make potential modification of boot features easier 
> with scripts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Work started] (KARAF-5403) Karaf tooling doesn't keep ordering of features given in configuration

2017-10-13 Thread JIRA 

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

Work on KARAF-5403 started by Łukasz Dywicki.
-
> Karaf tooling doesn't keep ordering of features given in configuration
> --
>
> Key: KARAF-5403
> URL: https://issues.apache.org/jira/browse/KARAF-5403
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-tooling
>Affects Versions: 4.0.8
>Reporter: Łukasz Dywicki
>Assignee: Łukasz Dywicki
>
> Even if in properly designed modular system order of start list of bundles 
> should not matter (as start level is sorting factor) for maintainability of 
> configurations and ease of use fature order given in maven plugin 
> configurations should be preserved as much as possible.
> Currently Karaf Assembly Builder does use hashing collections which do not 
> preserve insertion order leading to randomization of boot features and 
> repositories.
> Solving this issue will make potential modification of boot features easier 
> with scripts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5313) Exception when deleting a .cfg file from hot deploy directory

2017-10-13 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/KARAF-5313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203294#comment-16203294
 ] 

Börcsök József commented on KARAF-5313:
---

I found a similar issue using Felix Fileinstall 3.6.0. I've created a 
declarative service via ConfigAdmin and the above exeption is thrown when tried 
to delete the component.

This is how service is created:
{code}
final Configuration cfg = 
configAdmin.createFactoryConfiguration(factoryPid, "?");
final Dictionary props = new Hashtable<>();
cfg.update(props);
{code}

And how it is removed (filter is an OSGi filter expression of ID based on props 
of creation):
{code}
final Configuration[] cfgsToDelete = configAdmin.listConfigurations(filter);

if (cfgsToDelete != null) {
for (final Configuration c : cfgsToDelete) {
c.delete();
}
} else {
log.warn("No configuration found: " + filter);
}
{code}

NPE is thrown because dictionary (dict = config.getProperties()) is NULL at 
line 179 in org.apache.felix.fileinstall.internal.ConfigInstaller that is not 
handled, setting fileName should check it at the next line.

> Exception when deleting a .cfg file from hot deploy directory 
> --
>
> Key: KARAF-5313
> URL: https://issues.apache.org/jira/browse/KARAF-5313
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.2
> Environment: Windows 7
>Reporter: Scott Leschke
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.3, 4.0.11
>
>
> 2017-08-17T14:03:37,333 | INFO  | CM Event Dispatcher (Fire 
> ConfigurationEvent: 
> pid=bam.provider.query.cae236fc-adc4-437f-9197-0f58eda1d049) | fileinstall
>   | 8 - org.apache.felix.fileinstall - 3.6.0 | Unable to 
> delete configuration file
> java.lang.NullPointerException: null
>   at 
> org.apache.felix.fileinstall.internal.ConfigInstaller.doConfigurationEvent(ConfigInstaller.java:180)
>  [8:org.apache.felix.fileinstall:3.6.0]
>   at 
> org.apache.felix.fileinstall.internal.ConfigInstaller.configurationEvent(ConfigInstaller.java:108)
>  [8:org.apache.felix.fileinstall:3.6.0]
>   at 
> org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.sendEvent(ConfigurationManager.java:2074)
>  [7:org.apache.felix.configadmin:1.8.14]
>   at 
> org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.run(ConfigurationManager.java:2042)
>  [7:org.apache.felix.configadmin:1.8.14]
>   at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:141) 
> [7:org.apache.felix.configadmin:1.8.14]
>   at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:109) 
> [7:org.apache.felix.configadmin:1.8.14]
>   at java.lang.Thread.run(Thread.java:748) [?:?]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5103) Quick start fails at the step "feature:install camel-spring"

2017-10-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203184#comment-16203184
 ] 

ASF subversion and git services commented on KARAF-5103:


Commit 2aeb00bdbdfee3fb316a6ea86f7737a439af13ff in karaf's branch 
refs/heads/master from [~gnt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=2aeb00b ]

[KARAF-5103] Update quickstart for Karaf 4.2.0 and recent camel


> Quick start fails at the step "feature:install camel-spring"
> 
>
> Key: KARAF-5103
> URL: https://issues.apache.org/jira/browse/KARAF-5103
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Ubuntu 14.04
>Reporter: Mike Fogg
> Fix For: 4.2.0, 4.1.3
>
>
> The quick start results in an error when entering the command to install 
> camel-spring.
> karaf@root()> feature:install camel-spring
> Error executing command: Unable to resolve root: missing requirement [root] 
> osgi.identity; osgi.identity=camel-spring; type=karaf.feature; 
> version="[2.15.2,2.15.2]"; 
> filter:="(&(osgi.identity=camel-spring)(type=karaf.feature)(version>=2.15.2)(version<=2.15.2))"
>  [caused by: Unable to resolve camel-spring/2.15.2: missing requirement 
> [camel-spring/2.15.2] osgi.identity; osgi.identity=spring; 
> type=karaf.feature; version="[3.2.0,4.0.0)"]
> It sounds like this is related to KARAF-4730, however since this is the first 
> thing I have tried after installing and is my introduction to Karaf (as it 
> would be presumably for anyone going through the Quick Start), I don't know 
> how I would go about removing the filter from the camel-spring dependency in 
> order to install it.  Considering this is a quick start, I probably shouldn't 
> have to do anything that isn't spelled out in the instructions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (KARAF-5103) Quick start fails at the step "feature:install camel-spring"

2017-10-13 Thread Guillaume Nodet (JIRA) 

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

Guillaume Nodet resolved KARAF-5103.

   Resolution: Fixed
 Assignee: Guillaume Nodet
Fix Version/s: (was: 4.1.2)
   4.1.3

> Quick start fails at the step "feature:install camel-spring"
> 
>
> Key: KARAF-5103
> URL: https://issues.apache.org/jira/browse/KARAF-5103
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Ubuntu 14.04
>Reporter: Mike Fogg
>Assignee: Guillaume Nodet
> Fix For: 4.2.0, 4.1.3
>
>
> The quick start results in an error when entering the command to install 
> camel-spring.
> karaf@root()> feature:install camel-spring
> Error executing command: Unable to resolve root: missing requirement [root] 
> osgi.identity; osgi.identity=camel-spring; type=karaf.feature; 
> version="[2.15.2,2.15.2]"; 
> filter:="(&(osgi.identity=camel-spring)(type=karaf.feature)(version>=2.15.2)(version<=2.15.2))"
>  [caused by: Unable to resolve camel-spring/2.15.2: missing requirement 
> [camel-spring/2.15.2] osgi.identity; osgi.identity=spring; 
> type=karaf.feature; version="[3.2.0,4.0.0)"]
> It sounds like this is related to KARAF-4730, however since this is the first 
> thing I have tried after installing and is my introduction to Karaf (as it 
> would be presumably for anyone going through the Quick Start), I don't know 
> how I would go about removing the filter from the camel-spring dependency in 
> order to install it.  Considering this is a quick start, I probably shouldn't 
> have to do anything that isn't spelled out in the instructions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5103) Quick start fails at the step "feature:install camel-spring"

2017-10-13 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203183#comment-16203183
 ] 

ASF subversion and git services commented on KARAF-5103:


Commit cefe274d7936e0c93815eca830e8c94e3217660c in karaf's branch 
refs/heads/karaf-4.1.x from [~gnt]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=cefe274 ]

[KARAF-5103] Update quickstart for Karaf 4.1.0 and recent camel


> Quick start fails at the step "feature:install camel-spring"
> 
>
> Key: KARAF-5103
> URL: https://issues.apache.org/jira/browse/KARAF-5103
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Ubuntu 14.04
>Reporter: Mike Fogg
> Fix For: 4.2.0, 4.1.3
>
>
> The quick start results in an error when entering the command to install 
> camel-spring.
> karaf@root()> feature:install camel-spring
> Error executing command: Unable to resolve root: missing requirement [root] 
> osgi.identity; osgi.identity=camel-spring; type=karaf.feature; 
> version="[2.15.2,2.15.2]"; 
> filter:="(&(osgi.identity=camel-spring)(type=karaf.feature)(version>=2.15.2)(version<=2.15.2))"
>  [caused by: Unable to resolve camel-spring/2.15.2: missing requirement 
> [camel-spring/2.15.2] osgi.identity; osgi.identity=spring; 
> type=karaf.feature; version="[3.2.0,4.0.0)"]
> It sounds like this is related to KARAF-4730, however since this is the first 
> thing I have tried after installing and is my introduction to Karaf (as it 
> would be presumably for anyone going through the Quick Start), I don't know 
> how I would go about removing the filter from the camel-spring dependency in 
> order to install it.  Considering this is a quick start, I probably shouldn't 
> have to do anything that isn't spelled out in the instructions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (KARAF-5103) Quick start fails at the step "feature:install camel-spring"

2017-10-13 Thread Guillaume Nodet (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203120#comment-16203120
 ] 

Guillaume Nodet edited comment on KARAF-5103 at 10/13/17 7:38 AM:
--

The doc still points to 2.15.2, we need to fix it.
The camel-example-osgi does not exist in 2.18.x of camel.
And since camel 2.20.0, examples are only provided as sources, not binaries.


was (Author: gnt):
The doc still points to 2.15.2, we need to fix it.

> Quick start fails at the step "feature:install camel-spring"
> 
>
> Key: KARAF-5103
> URL: https://issues.apache.org/jira/browse/KARAF-5103
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Ubuntu 14.04
>Reporter: Mike Fogg
> Fix For: 4.2.0, 4.1.2
>
>
> The quick start results in an error when entering the command to install 
> camel-spring.
> karaf@root()> feature:install camel-spring
> Error executing command: Unable to resolve root: missing requirement [root] 
> osgi.identity; osgi.identity=camel-spring; type=karaf.feature; 
> version="[2.15.2,2.15.2]"; 
> filter:="(&(osgi.identity=camel-spring)(type=karaf.feature)(version>=2.15.2)(version<=2.15.2))"
>  [caused by: Unable to resolve camel-spring/2.15.2: missing requirement 
> [camel-spring/2.15.2] osgi.identity; osgi.identity=spring; 
> type=karaf.feature; version="[3.2.0,4.0.0)"]
> It sounds like this is related to KARAF-4730, however since this is the first 
> thing I have tried after installing and is my introduction to Karaf (as it 
> would be presumably for anyone going through the Quick Start), I don't know 
> how I would go about removing the filter from the camel-spring dependency in 
> order to install it.  Considering this is a quick start, I probably shouldn't 
> have to do anything that isn't spelled out in the instructions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (KARAF-5416) Remove support for ext and endorsed libraries for Java 9 compatibility

2017-10-13 Thread Grzegorz Grzybek (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-5416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16203133#comment-16203133
 ] 

Grzegorz Grzybek commented on KARAF-5416:
-

[~gnt] so no more "enhanced" {{java.lang.Throwable}} for pax-logging?

> Remove support for ext and endorsed libraries for Java 9 compatibility
> --
>
> Key: KARAF-5416
> URL: https://issues.apache.org/jira/browse/KARAF-5416
> Project: Karaf
>  Issue Type: New Feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (KARAF-5424) Bad input stream behavior when using grep command

2017-10-13 Thread Guillaume Nodet (JIRA) 
Guillaume Nodet created KARAF-5424:
--

 Summary: Bad input stream behavior when using grep command
 Key: KARAF-5424
 URL: https://issues.apache.org/jira/browse/KARAF-5424
 Project: Karaf
  Issue Type: Bug
Reporter: Guillaume Nodet


The following command does not handle the input stream correctly (, 
Ctrl+C, Ctrl+D, etc...)
{code}
grep o
{code}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)