[jira] [Commented] (KARAF-5281) Upgrade to Spring 4.3.10.RELEASE

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5281:


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

[KARAF-5281] Upgrade to Spring 4.3.10.RELEASE


> Upgrade to Spring 4.3.10.RELEASE
> 
>
> Key: KARAF-5281
> URL: https://issues.apache.org/jira/browse/KARAF-5281
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-feature
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>




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


[jira] [Resolved] (KARAF-5281) Upgrade to Spring 4.3.10.RELEASE

2017-07-31 Thread JIRA

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

Jean-Baptiste Onofré resolved KARAF-5281.
-
Resolution: Fixed

> Upgrade to Spring 4.3.10.RELEASE
> 
>
> Key: KARAF-5281
> URL: https://issues.apache.org/jira/browse/KARAF-5281
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-feature
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>




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


[jira] [Commented] (KARAF-5281) Upgrade to Spring 4.3.10.RELEASE

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5281:


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

[KARAF-5281] Upgrade to Spring 4.3.10.RELEASE


> Upgrade to Spring 4.3.10.RELEASE
> 
>
> Key: KARAF-5281
> URL: https://issues.apache.org/jira/browse/KARAF-5281
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-feature
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>




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


[jira] [Created] (KARAF-5281) Upgrade to Spring 4.3.10.RELEASE

2017-07-31 Thread JIRA
Jean-Baptiste Onofré created KARAF-5281:
---

 Summary: Upgrade to Spring 4.3.10.RELEASE
 Key: KARAF-5281
 URL: https://issues.apache.org/jira/browse/KARAF-5281
 Project: Karaf
  Issue Type: Dependency upgrade
  Components: karaf-feature
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
 Fix For: 4.2.0, 4.1.2






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


[jira] [Work started] (KARAF-5281) Upgrade to Spring 4.3.10.RELEASE

2017-07-31 Thread JIRA

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

Work on KARAF-5281 started by Jean-Baptiste Onofré.
---
> Upgrade to Spring 4.3.10.RELEASE
> 
>
> Key: KARAF-5281
> URL: https://issues.apache.org/jira/browse/KARAF-5281
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-feature
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>




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


[jira] [Updated] (KARAF-4537) Karaf Maven Plugin should respect scope when building a feature

2017-07-31 Thread JIRA

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

Jean-Baptiste Onofré updated KARAF-4537:

Fix Version/s: (was: 4.1.2)
   4.1.3

> Karaf Maven Plugin should respect scope when building a feature
> ---
>
> Key: KARAF-4537
> URL: https://issues.apache.org/jira/browse/KARAF-4537
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-tooling
>Affects Versions: 4.0.5
>Reporter: Viktor Kozlov
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.3
>
>
> I am building a feature without a feature template file. I list my feature 
> content via pom dependencies.
> For example:
> 
> 
> org.apache.geronimo.specs
> geronimo-validation_1.1_spec
> compile
> 
> 
> org.apache.geronimo.specs
> geronimo-el_2.2_spec
> compile
> 
> 
> commons-collections
> commons-collections
> compile
> 
> 
> commons-beanutils
> commons-beanutils
> compile
> 
> 
> org.apache.bval
> org.apache.bval.bundle
> compile
> 
> 
> The target file is OK except I need to mark somehow whether bundle is 
> dependency or not.
> dependency="true">mvn:org.apache.geronimo.specs/geronimo-validation_1.1_spec
> I think maven runtime scope would be nice.



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


[jira] [Updated] (KARAF-4424) referenced features/bundles not installed when dropped in deploy folder

2017-07-31 Thread JIRA

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

Jean-Baptiste Onofré updated KARAF-4424:

Fix Version/s: (was: 4.1.2)
   4.1.3

> referenced features/bundles not installed when dropped in deploy folder
> ---
>
> Key: KARAF-4424
> URL: https://issues.apache.org/jira/browse/KARAF-4424
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.4
>Reporter: Robert von Burg
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.0.10, 4.1.3
>
>
> I have the following features:
> {code:xml}
> 
> http://karaf.apache.org/xmlns/features/v1.3.0"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://karaf.apache.org/xmlns/features/v1.3.0 
> karaf-features-1.3.0.xsd " name="All-features">
>   
> mvn:my.group/MyBundle1/0.3.0-SNAPSHOT/xml/features
>   
> mvn:my.group/MyBundle2/0.3.0-SNAPSHOT/xml/features
>   
> mvn:my.group/MyBundle3/0.3.0-SNAPSHOT/xml/features
>   
>version="0.3.0-SNAPSHOT">MyBundle1
>   
>   
>version="0.3.0-SNAPSHOT">MyBundle2
>   
>   
>version="0.3.0-SNAPSHOT">MyBundle3
>   
> 
> 
> http://karaf.apache.org/xmlns/features/v1.3.0"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://karaf.apache.org/xmlns/features/v1.3.0 
> karaf-features-1.3.0.xsd " name="MyBundle1-features">
>   
>start="true">mvn:my.group/MyBundle1/0.3.0-SNAPSHOT
>   
> 
> 
> http://karaf.apache.org/xmlns/features/v1.3.0"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://karaf.apache.org/xmlns/features/v1.3.0 
> karaf-features-1.3.0.xsd " name="MyBundle2-features">
>   
>start="true">mvn:my.group/MyBundle2/0.3.0-SNAPSHOT
>   
> 
> 
> http://karaf.apache.org/xmlns/features/v1.3.0"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>   xsi:schemaLocation="http://karaf.apache.org/xmlns/features/v1.3.0 
> karaf-features-1.3.0.xsd " name="MyBundle3-features">
>   
>start="true">mvn:my.group/MyBundle3/0.3.0-SNAPSHOT
>   
> 
> {code}
> On my local machine when i drop the "all-features", then it installs al the 
> referenced bundles. On my local machine, the bundles were installed using mvn 
> clean install.
> On another machine, where the features are pulled in through a remote archiva 
> repository, it doesn't auto install. It says:
> {noformat}
> Adding features: MyBundle1/[0.3.0.SNAPSHOT,0.3.0.SNAPSHOT]
> No deployment change.
> {noformat}
> When i then do everything by hand:
> {noformat}
> feature:repo-add mvn:my.group/MyBundle1/0.3.0-SNAPSHOT/xml/features
> feature:repo-add mvn:my.group/MyBundle2/0.3.0-SNAPSHOT/xml/features
> feature:repo-add mvn:my.group/MyBundle3/0.3.0-SNAPSHOT/xml/features
> feature:install MyBundle1/0.3.0-SNAPSHOT
> feature:install MyBundle2/0.3.0-SNAPSHOT
> feature:install MyBundle3/0.3.0-SNAPSHOT
> {noformat}
> the features are installed and everything.



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


[jira] [Resolved] (KARAF-5120) etc/org.apache.karaf.shell.cfg is "raw", all comments are lost in the distribution

2017-07-31 Thread JIRA

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

Jean-Baptiste Onofré resolved KARAF-5120.
-
Resolution: Fixed

> etc/org.apache.karaf.shell.cfg is "raw", all comments are lost in the 
> distribution
> --
>
> Key: KARAF-5120
> URL: https://issues.apache.org/jira/browse/KARAF-5120
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core, karaf-tooling
>Affects Versions: 4.1.1
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>
> In the "final" distributions, the {{etc/org.apache.karaf.shell.cfg}} just 
> contains:
> {code}
> sshPort=8201
> sshHost=0.0.0.0
> sshRealm=karaf
> hostKey=${karaf.etc}/host.key
> {code}
> All original comments, including additional properties examples, are lost.



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


[jira] [Resolved] (KARAF-5111) Error executing command: java.lang.InterruptedException when installing feature

2017-07-31 Thread JIRA

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

Jean-Baptiste Onofré resolved KARAF-5111.
-
   Resolution: Cannot Reproduce
Fix Version/s: (was: 4.1.2)
   (was: 4.2.0)

Tested on 4.1.2-SNAPSHOT and 4.2.0-SNAPSHOT without problem.

I created the ipojo features XML locally and installed the ipojo feature from 
this file.

> Error executing command: java.lang.InterruptedException when installing 
> feature
> ---
>
> Key: KARAF-5111
> URL: https://issues.apache.org/jira/browse/KARAF-5111
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.1.1
> Environment: JDK 8, MacOS
>Reporter: Andy Phillips
>Assignee: Jean-Baptiste Onofré
> Attachments: karaf.log
>
>
> I am trying to install a feature i wrote to install iPojo.  I can manually 
> install the two bundles, but when i install the "feature" that does the same 
> thing it give me the following error:
> {code}
> Error executing command: java.lang.InterruptedException
> {code}
> I've attached the karaf.log as well. ipojo version == 1.12.1
> The feature is simple:
> {code}
> 
> mvn:org.apache.felix/org.apache.felix.ipojo/1.12.1
> 
> mvn:org.apache.felix/org.apache.felix.ipojo.api/1.12.1
> 
> {code}



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


[jira] [Updated] (KARAF-5110) Karaf 4.1.x / httplite incompatibility

2017-07-31 Thread JIRA

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

Jean-Baptiste Onofré updated KARAF-5110:

Fix Version/s: (was: 4.1.2)
   4.1.3

> Karaf 4.1.x / httplite incompatibility
> --
>
> Key: KARAF-5110
> URL: https://issues.apache.org/jira/browse/KARAF-5110
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Maven 3.3.9 / MacOS 10.12.4
>Reporter: Stephen Winnall
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.3
>
> Attachments: karaf-4.1.x-httplite.tbz
>
>
> I am trying to build a Karaf assembly using Karaf 4.1.1, Java 
> 1.8.0_76-ea-b04, Maven 3.3.9, Netbeans 8.2 and macOS 10.12.4. I am getting an 
> error message, even if I omit all my own features from the build (i.e. I 
> build an empty Karaf): 
> java.lang.ClassCastException: 
> org.apache.felix.httplite.osgi.HttpServiceImpl cannot be cast to 
> org.osgi.service.http.HttpService 
> The problem seems to be that the latest version of 
> org.apache.felix.httplite.complete, which provides 
> org.apache.felix.httplite.osgi.HttpServiceImpl, i.e. 0.1.5, requires a 
> version of java.servlet that is incompatible with the rest of Karaf 4.1.1, 
> which - I think - expects 3.1.0. The following comes from the MANIFEST.MF of 
> org.apache.felix.httplite.complete-0.1.5.jar: 
> Import-Package: javax.servlet;version="[2.4,3)" 



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


[jira] [Updated] (KARAF-5111) Error executing command: java.lang.InterruptedException when installing feature

2017-07-31 Thread JIRA

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

Jean-Baptiste Onofré updated KARAF-5111:

Description: 
I am trying to install a feature i wrote to install iPojo.  I can manually 
install the two bundles, but when i install the "feature" that does the same 
thing it give me the following error:

{code}
Error executing command: java.lang.InterruptedException
{code}

I've attached the karaf.log as well.  ${version.ipojo} = 1.12.1

The feature is simple:

{code}

mvn:org.apache.felix/org.apache.felix.ipojo/1.12.1
mvn:org.apache.felix/org.apache.felix.ipojo.api/1.12.1

{code}

  was:
I am trying to install a feature i wrote to install iPojo.  I can manually 
install the two bundles, but when i install the "feature" that does the same 
thing it give me the following error:

{code}
Error executing command: java.lang.InterruptedException
{code}

I've attached the karaf.log as well.  ${version.ipojo} = 1.12.1

The feature is simple:

{code}


mvn:org.apache.felix/org.apache.felix.ipojo/${version.ipojo}

mvn:org.apache.felix/org.apache.felix.ipojo.api/${version.ipojo}

{code}


> Error executing command: java.lang.InterruptedException when installing 
> feature
> ---
>
> Key: KARAF-5111
> URL: https://issues.apache.org/jira/browse/KARAF-5111
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.1.1
> Environment: JDK 8, MacOS
>Reporter: Andy Phillips
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log
>
>
> I am trying to install a feature i wrote to install iPojo.  I can manually 
> install the two bundles, but when i install the "feature" that does the same 
> thing it give me the following error:
> {code}
> Error executing command: java.lang.InterruptedException
> {code}
> I've attached the karaf.log as well.  ${version.ipojo} = 1.12.1
> The feature is simple:
> {code}
> 
> mvn:org.apache.felix/org.apache.felix.ipojo/1.12.1
> 
> mvn:org.apache.felix/org.apache.felix.ipojo.api/1.12.1
> 
> {code}



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


[jira] [Updated] (KARAF-5111) Error executing command: java.lang.InterruptedException when installing feature

2017-07-31 Thread JIRA

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

Jean-Baptiste Onofré updated KARAF-5111:

Description: 
I am trying to install a feature i wrote to install iPojo.  I can manually 
install the two bundles, but when i install the "feature" that does the same 
thing it give me the following error:

{code}
Error executing command: java.lang.InterruptedException
{code}

I've attached the karaf.log as well. ipojo version == 1.12.1

The feature is simple:

{code}

mvn:org.apache.felix/org.apache.felix.ipojo/1.12.1
mvn:org.apache.felix/org.apache.felix.ipojo.api/1.12.1

{code}

  was:
I am trying to install a feature i wrote to install iPojo.  I can manually 
install the two bundles, but when i install the "feature" that does the same 
thing it give me the following error:

{code}
Error executing command: java.lang.InterruptedException
{code}

I've attached the karaf.log as well.  ${version.ipojo} = 1.12.1

The feature is simple:

{code}

mvn:org.apache.felix/org.apache.felix.ipojo/1.12.1
mvn:org.apache.felix/org.apache.felix.ipojo.api/1.12.1

{code}


> Error executing command: java.lang.InterruptedException when installing 
> feature
> ---
>
> Key: KARAF-5111
> URL: https://issues.apache.org/jira/browse/KARAF-5111
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.1.1
> Environment: JDK 8, MacOS
>Reporter: Andy Phillips
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log
>
>
> I am trying to install a feature i wrote to install iPojo.  I can manually 
> install the two bundles, but when i install the "feature" that does the same 
> thing it give me the following error:
> {code}
> Error executing command: java.lang.InterruptedException
> {code}
> I've attached the karaf.log as well. ipojo version == 1.12.1
> The feature is simple:
> {code}
> 
> mvn:org.apache.felix/org.apache.felix.ipojo/1.12.1
> 
> mvn:org.apache.felix/org.apache.felix.ipojo.api/1.12.1
> 
> {code}



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


[jira] [Updated] (KARAF-5111) Error executing command: java.lang.InterruptedException when installing feature

2017-07-31 Thread JIRA

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

Jean-Baptiste Onofré updated KARAF-5111:

Description: 
I am trying to install a feature i wrote to install iPojo.  I can manually 
install the two bundles, but when i install the "feature" that does the same 
thing it give me the following error:

{code}
Error executing command: java.lang.InterruptedException
{code}

I've attached the karaf.log as well.  ${version.ipojo} = 1.12.1

The feature is simple:

{code}


mvn:org.apache.felix/org.apache.felix.ipojo/${version.ipojo}

mvn:org.apache.felix/org.apache.felix.ipojo.api/${version.ipojo}

{code}

  was:
I am trying to install a feature i wrote to install iPojo.  I can manually 
install the two bundles, but when i install the "feature" that does the same 
thing it give me the following error:

{code}
Error executing command: java.lang.InterruptedException
{code}

I've attached the karaf.log as well.  ${version.ipojo} = 1.12.1

The feature is simple:



mvn:org.apache.felix/org.apache.felix.ipojo/${version.ipojo}

mvn:org.apache.felix/org.apache.felix.ipojo.api/${version.ipojo}



> Error executing command: java.lang.InterruptedException when installing 
> feature
> ---
>
> Key: KARAF-5111
> URL: https://issues.apache.org/jira/browse/KARAF-5111
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.1.1
> Environment: JDK 8, MacOS
>Reporter: Andy Phillips
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log
>
>
> I am trying to install a feature i wrote to install iPojo.  I can manually 
> install the two bundles, but when i install the "feature" that does the same 
> thing it give me the following error:
> {code}
> Error executing command: java.lang.InterruptedException
> {code}
> I've attached the karaf.log as well.  ${version.ipojo} = 1.12.1
> The feature is simple:
> {code}
> 
> 
> mvn:org.apache.felix/org.apache.felix.ipojo/${version.ipojo}
> 
> mvn:org.apache.felix/org.apache.felix.ipojo.api/${version.ipojo}
> 
> {code}



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


[jira] [Resolved] (KARAF-5134) Instance org.apache.karaf.features.cfg refers to 4.1.1-SNAPSHOT

2017-07-31 Thread JIRA

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

Jean-Baptiste Onofré resolved KARAF-5134.
-
Resolution: Fixed

> Instance org.apache.karaf.features.cfg refers to 4.1.1-SNAPSHOT
> ---
>
> Key: KARAF-5134
> URL: https://issues.apache.org/jira/browse/KARAF-5134
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-instance
>Affects Versions: 4.1.1
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>




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


[jira] [Updated] (KARAF-5228) Add documentation about staged featuresBoot

2017-07-31 Thread JIRA

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

Jean-Baptiste Onofré updated KARAF-5228:

Fix Version/s: (was: 4.1.2)
   4.1.3

> Add documentation about staged featuresBoot
> ---
>
> Key: KARAF-5228
> URL: https://issues.apache.org/jira/browse/KARAF-5228
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.1.1
>Reporter: Emily Berk
> Fix For: 4.2.0, 4.1.3
>
>
> Documentation should be added to clarify the relationship between features 
> included in parentheses and features not wrapped in parentheses.



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


[jira] [Updated] (KARAF-5273) karaf-maven-plugin assembly should take feature wildcards

2017-07-31 Thread JIRA

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

Jean-Baptiste Onofré updated KARAF-5273:

Fix Version/s: (was: 4.1.2)
   4.1.3

> karaf-maven-plugin assembly should take feature wildcards
> -
>
> Key: KARAF-5273
> URL: https://issues.apache.org/jira/browse/KARAF-5273
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-tooling
>Reporter: Fabian Lange
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.3
>
>
> As per discussion in:
> http://karaf.922171.n3.nabble.com/Building-custom-dist-including-all-features-of-a-repository-td4051100.html
> it would be great if the assembly part of the karaf-maven-plugin would 
> respect wildcards for startup/boot/installed feature names. currently it only 
> performs an equals check, requiring dist builders to explicitly list all the 
> features they want.



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


[jira] [Updated] (KARAF-5198) KAR:Create update feature file based on list of features provided

2017-07-31 Thread George McCone (JIRA)

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

George McCone updated KARAF-5198:
-
Description: 
When you create a KAR file using the kar:create command, you can give it a list 
of features of the specified repo to include in the KAR file.

It appears that the feature file that is included in the KAR is copied straight 
out of the repo and includes all the features regardless of the those specified.

When the KAR is deployed, it is starting all the features in the feature file. 
In many cases this is resulting in the starting of numerous other features.

One good example of this is the cxf-dosgi repo's feature "cxf-dosgi-base" which 
has a feature defined for libs needed when running outside Karaf (or at least 
that is what the description says for the feature). It references a bunch of 
bundles that come with core Karaf and when this feature tries to install, it 
hangs the KAR deployer and Karaf won't shutdown correctly.

It would be nice if the feature file either removed those features that were 
not exported, or mark the feature with install="manual", assuming KARAF-5197 
adds this capability.

  was:
When you create a KAR file using the kar:create command, you can give it a list 
of features of the specified repo to include int the KAR file.

It appears that the feature file that is included in the KAR is copied straight 
out of the repo and includes all the features regardless of the those specified.

When the KAR is deployed, it is starting all the features in the feature file. 
In many cases this is resulting in the starting of numerous other features.

One good example of this is the cxf-dosgi repo's feature "cxf-dosgi-base" which 
has a feature defined for libs needed when running outside Karaf (or at least 
that is what the description says for the feature). It references a bunch of 
bundles that come with core Karaf and when this feature tries to install, it 
hangs the KAR deployer and Karaf won't shutdown correctly.

It would be nice if the feature file either removed those features that were 
not exported, or mark the feature with install="manual", assuming KARAF-5197 
adds this capability.


> KAR:Create update feature file based on list of features provided
> -
>
> Key: KARAF-5198
> URL: https://issues.apache.org/jira/browse/KARAF-5198
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-kar
> Environment: N/A
>Reporter: George McCone
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
>
> When you create a KAR file using the kar:create command, you can give it a 
> list of features of the specified repo to include in the KAR file.
> It appears that the feature file that is included in the KAR is copied 
> straight out of the repo and includes all the features regardless of the 
> those specified.
> When the KAR is deployed, it is starting all the features in the feature 
> file. In many cases this is resulting in the starting of numerous other 
> features.
> One good example of this is the cxf-dosgi repo's feature "cxf-dosgi-base" 
> which has a feature defined for libs needed when running outside Karaf (or at 
> least that is what the description says for the feature). It references a 
> bunch of bundles that come with core Karaf and when this feature tries to 
> install, it hangs the KAR deployer and Karaf won't shutdown correctly.
> It would be nice if the feature file either removed those features that were 
> not exported, or mark the feature with install="manual", assuming KARAF-5197 
> adds this capability.



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


[jira] [Reopened] (KARAF-5280) Shell should not display the welcome message again when it is restarted

2017-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider reopened KARAF-5280:


The current solution also suppresses the welcome on ssh which is not desired.
Need to fix that.

> Shell should not display the welcome message again when it is restarted
> ---
>
> Key: KARAF-5280
> URL: https://issues.apache.org/jira/browse/KARAF-5280
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.2.0, 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> When updating the shell explicitly or during a feature install or uninstall 
> we see this welcome message:
> {{__ __    
>/ //_/ __ _/ __/  
>   / ,<  / __ `/ ___/ __ `/ /_
>  / /| |/ /_/ / /  / /_/ / __/
> /_/ |_|\__,_/_/   \__,_/_/ 
>   Apache Karaf (4.2.0-SNAPSHOT)
> 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.
> }}
> To reproduce do:
> update org.apache.karaf.shell.core 
> While the welcome message makes sense when karaf starts it is confusing when 
> installing or uninstalling a feature. So I propose we store that we already 
> displayed the welcome message and then do not display it again.



--
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-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider edited comment on KARAF-5103 at 7/31/17 4:21 PM:
-

This issue is fixed in later camel versions.
Try:
feature:repo-add camel 2.18.4
feature:install camel-spring



was (Author: ch...@die-schneider.net):
This issue is fixed in later camel versions.
Try:
{{feature:repo-add camel 2.18.4
feature:install camel-spring}}


> 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: Christian Schneider
> 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] [Resolved] (KARAF-5103) Quick start fails at the step "feature:install camel-spring"

2017-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider resolved KARAF-5103.

Resolution: Fixed

This issue is fixed in later camel versions.
Try:
{{feature:repo-add camel 2.18.4
feature:install camel-spring}}


> 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: Christian Schneider
> 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] [Resolved] (KARAF-5280) Shell should not display the welcome message again when it is restarted

2017-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider resolved KARAF-5280.

Resolution: Fixed

> Shell should not display the welcome message again when it is restarted
> ---
>
> Key: KARAF-5280
> URL: https://issues.apache.org/jira/browse/KARAF-5280
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.2.0, 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> When updating the shell explicitly or during a feature install or uninstall 
> we see this welcome message:
> {{__ __    
>/ //_/ __ _/ __/  
>   / ,<  / __ `/ ___/ __ `/ /_
>  / /| |/ /_/ / /  / /_/ / __/
> /_/ |_|\__,_/_/   \__,_/_/ 
>   Apache Karaf (4.2.0-SNAPSHOT)
> 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.
> }}
> To reproduce do:
> update org.apache.karaf.shell.core 
> While the welcome message makes sense when karaf starts it is confusing when 
> installing or uninstalling a feature. So I propose we store that we already 
> displayed the welcome message and then do not display it again.



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


[jira] [Commented] (KARAF-5280) Shell should not display the welcome message again when it is restarted

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5280:


Commit 8298925b1e748c220d8c7ba41e74e4c4eecd0c4f in karaf's branch 
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=8298925 ]

[KARAF-5280] Suppress welcome message on restarts of shell core


> Shell should not display the welcome message again when it is restarted
> ---
>
> Key: KARAF-5280
> URL: https://issues.apache.org/jira/browse/KARAF-5280
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.2.0, 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> When updating the shell explicitly or during a feature install or uninstall 
> we see this welcome message:
> {{__ __    
>/ //_/ __ _/ __/  
>   / ,<  / __ `/ ___/ __ `/ /_
>  / /| |/ /_/ / /  / /_/ / __/
> /_/ |_|\__,_/_/   \__,_/_/ 
>   Apache Karaf (4.2.0-SNAPSHOT)
> 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.
> }}
> To reproduce do:
> update org.apache.karaf.shell.core 
> While the welcome message makes sense when karaf starts it is confusing when 
> installing or uninstalling a feature. So I propose we store that we already 
> displayed the welcome message and then do not display it again.



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


[jira] [Commented] (KARAF-5280) Shell should not display the welcome message again when it is restarted

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5280:


Commit 9ff986db5fcefa9e2e40ed93267f7a5213db25e1 in karaf's branch 
refs/heads/karaf-4.1.x from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=9ff986d ]

[KARAF-5280] Suppress welcome message on restarts of shell core


> Shell should not display the welcome message again when it is restarted
> ---
>
> Key: KARAF-5280
> URL: https://issues.apache.org/jira/browse/KARAF-5280
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.2.0, 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> When updating the shell explicitly or during a feature install or uninstall 
> we see this welcome message:
> {{__ __    
>/ //_/ __ _/ __/  
>   / ,<  / __ `/ ___/ __ `/ /_
>  / /| |/ /_/ / /  / /_/ / __/
> /_/ |_|\__,_/_/   \__,_/_/ 
>   Apache Karaf (4.2.0-SNAPSHOT)
> 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.
> }}
> To reproduce do:
> update org.apache.karaf.shell.core 
> While the welcome message makes sense when karaf starts it is confusing when 
> installing or uninstalling a feature. So I propose we store that we already 
> displayed the welcome message and then do not display it again.



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


[jira] [Commented] (KARAF-5078) Shell crash

2017-07-31 Thread Scott Leschke (JIRA)

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

Scott Leschke commented on KARAF-5078:
--

Just built the latest version of 4.2.0-SNAPSHOT and tried this.  I entered 
'help' at the command prompt 4 times and was able to recreate the error

2017-07-31T11:01:14,796 | ERROR | Karaf local console user karaf | ShellUtil
| 42 - org.apache.karaf.shell.core - 4.2.0.SNAPSHOT | 
Exception caught while executing command
java.lang.NumberFormatException: For input string: "1B"
at 
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) 
~[?:?]
at java.lang.Integer.parseInt(Integer.java:580) ~[?:?]
at java.lang.Integer.(Integer.java:867) ~[?:?]
at 
org.jline.terminal.impl.jna.win.AnsiOutputStream.write(AnsiOutputStream.java:124)
 ~[?:?]
at java.io.FilterOutputStream.write(FilterOutputStream.java:125) ~[?:?]
at 
java.nio.channels.Channels$WritableByteChannelImpl.write(Channels.java:458) 
~[?:?]
at org.apache.felix.gogo.runtime.Pipe$MultiChannel.write(Pipe.java:644) 
~[42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
...

> Shell crash
> ---
>
> Key: KARAF-5078
> URL: https://issues.apache.org/jira/browse/KARAF-5078
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Windows 7
>Reporter: Scott Leschke
>Assignee: Christian Schneider
>Priority: Critical
> Fix For: 4.1.2
>
>
> Karaf shell behaves badly in Windows console. It appears better than 4.1.0 
> but still a problem. Command string start out red and turns dark blue while 
> typing become virtually unreadable.
> Most problematic though is that the shell crashed and brought down Karaf as a 
> result of entering the word "bundle" at the console prompt. After the 
> following tracebacks, the Felix shutdown sequence is displayed in the log.
> 2017-03-31T09:56:38,363 | ERROR | Karaf local console user karaf | ShellUtil  
>   | 42 - org.apache.karaf.shell.core - 4.1.1 | Exception 
> caught while executing command
> java.lang.NumberFormatException: For input string: "1B"
>   at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) 
> ~[?:?]
>   at java.lang.Integer.parseInt(Integer.java:580) ~[?:?]
>   at java.lang.Integer.parseInt(Integer.java:615) ~[?:?]
>   at 
> org.jline.terminal.impl.jna.win.WindowsAnsiOutputStream.write(WindowsAnsiOutputStream.java:189)
>  ~[?:?]
>   at java.io.FilterOutputStream.write(FilterOutputStream.java:125) ~[?:?]
>   at 
> java.nio.channels.Channels$WritableByteChannelImpl.write(Channels.java:458) 
> ~[?:?]
>   at org.apache.felix.gogo.runtime.Pipe$MultiChannel.write(Pipe.java:644) 
> ~[42:org.apache.karaf.shell.core:4.1.1]
>   at java.nio.channels.Channels.writeFullyImpl(Channels.java:78) ~[?:?]
>   at java.nio.channels.Channels.writeFully(Channels.java:101) ~[?:?]
>   at java.nio.channels.Channels.access$000(Channels.java:61) ~[?:?]
>   at java.nio.channels.Channels$1.write(Channels.java:174) ~[?:?]
>   at java.io.PrintStream.write(PrintStream.java:480) ~[?:?]
>   at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) ~[?:?]
>   at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) 
> ~[?:?]
>   at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104) ~[?:?]
>   at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185) 
> ~[?:?]
>   at java.io.PrintStream.write(PrintStream.java:527) ~[?:?]
>   at java.io.PrintStream.print(PrintStream.java:669) ~[?:?]
>   at java.io.PrintStream.println(PrintStream.java:806) ~[?:?]
>   at org.apache.felix.gogo.jline.Posix._main(Posix.java:134) 
> ~[42:org.apache.karaf.shell.core:4.1.1]
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
> ~[?:?]
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  ~[?:?]
>   at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?]
>   at org.apache.felix.gogo.runtime.Reflective.invoke(Reflective.java:136) 
> ~[42:org.apache.karaf.shell.core:4.1.1]
>   at 
> org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.lambda$wrap$0(SessionFactoryImpl.java:195)
>  ~[42:org.apache.karaf.shell.core:4.1.1]
>   at 
> org.apache.karaf.shell.impl.console.SessionFactoryImpl$ShellCommand.execute(SessionFactoryImpl.java:241)
>  [42:org.apache.karaf.shell.core:4.1.1]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
>  [42:org.apache.karaf.shell.core:4.1.1]
>   at 
> org.

[jira] [Created] (KARAF-5280) Shell should not display the welcome message again when it is restarted

2017-07-31 Thread Christian Schneider (JIRA)
Christian Schneider created KARAF-5280:
--

 Summary: Shell should not display the welcome message again when 
it is restarted
 Key: KARAF-5280
 URL: https://issues.apache.org/jira/browse/KARAF-5280
 Project: Karaf
  Issue Type: Improvement
  Components: karaf-shell
Affects Versions: 4.1.1, 4.2.0
Reporter: Christian Schneider
Assignee: Christian Schneider
 Fix For: 4.2.0, 4.1.2


When updating the shell explicitly or during a feature install or uninstall we 
see this welcome message:
{{__ __    
   / //_/ __ _/ __/  
  / ,<  / __ `/ ___/ __ `/ /_
 / /| |/ /_/ / /  / /_/ / __/
/_/ |_|\__,_/_/   \__,_/_/ 

  Apache Karaf (4.2.0-SNAPSHOT)

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.
}}

To reproduce do:
update org.apache.karaf.shell.core 

While the welcome message makes sense when karaf starts it is confusing when 
installing or uninstalling a feature. So I propose we store that we already 
displayed the welcome message and then do not display it again.




--
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-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider commented on KARAF-5103:


What quick start are you talking about? Can you point to a URL?

> 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: Christian Schneider
> 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-5279) InterruptedException when updating the shell.core bundle

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5279:


Commit ab47af2baf9a9e7ce9a23f86351960df3da59d02 in karaf's branch 
refs/heads/karaf-4.1.x from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=ab47af2 ]

[KARAF-5279] Only log InterruptedException on debug level


> InterruptedException when updating the shell.core bundle
> 
>
> Key: KARAF-5279
> URL: https://issues.apache.org/jira/browse/KARAF-5279
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> update org.apache.karaf.shell.core
> There are two InterruptedExceptions. This issue is mainly about the second 
> one.
> It seems to hint that the start of a bundles extensions did not finish which 
> is not true.
> I found that started.await() always throws InterruptedException if the thread 
> was interrupted even if the countdown latch for started already finished.
> 2017-07-31T15:33:53,571 | ERROR | Karaf local console user karaf | ShellUtil  
>   | 42 - org.apache.karaf.shell.core - 4.2.0.SNAPSHOT | 
> Exception caught while executing command
> java.lang.InterruptedException: null
>   at java.lang.Object.wait(Native Method) ~[?:?]
>   at java.lang.Object.wait(Object.java:502) [?:?]
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.start(CommandSessionImpl.java:772)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:295) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:168) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:148) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:168)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:363)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at java.lang.Thread.run(Thread.java:748) [?:?]
> 2017-07-31T15:34:20,192 | WARN  | pipe-update 42   | CommandExtension 
> | 42 - org.apache.karaf.shell.core - 4.2.0.SNAPSHOT | The wait for 
> bundle org.apache.karaf.service.core being started before destruction has 
> been interrupted.
> java.lang.InterruptedException: null
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
>  [?:?]
>   at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) 
> [?:?]
>   at 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension.destroy(CommandExtension.java:125)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.utils.extender.AbstractExtender$2.run(AbstractExtender.java:285)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   at 
> org.apache.felix.utils.extender.AbstractExtender.destroyExtension(AbstractExtender.java:307)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.utils.extender.AbstractExtender.stop(AbstractExtender.java:125)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.stop(Activator.java:128) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:719)
>  [?:?]
>   at org.apache.felix.framework.Felix.stopBundle(Felix.java:2632) [?:?]
>   at org.apache.felix.framework.Felix.updateBundle(Felix.java:2366) [?:?]
>   at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:1018) 
> [?:?]
>   at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:1004) 
> [?:?]
>   at org.apache.karaf.bundle.command.Update.doExecute(Update.java:57) 
> [21:org.apache.karaf.bundle.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.bundle.command.BundleCommand.execute(BundleCommand.java:46) 
> [21:org.apache.karaf.bundle.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCo

[jira] [Commented] (KARAF-5279) InterruptedException when updating the shell.core bundle

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5279:


Commit f9e5308f3cfe50453bdab321f405b253da330990 in karaf's branch 
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=f9e5308 ]

[KARAF-5279] Only log InterruptedException on debug level


> InterruptedException when updating the shell.core bundle
> 
>
> Key: KARAF-5279
> URL: https://issues.apache.org/jira/browse/KARAF-5279
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> update org.apache.karaf.shell.core
> There are two InterruptedExceptions. This issue is mainly about the second 
> one.
> It seems to hint that the start of a bundles extensions did not finish which 
> is not true.
> I found that started.await() always throws InterruptedException if the thread 
> was interrupted even if the countdown latch for started already finished.
> 2017-07-31T15:33:53,571 | ERROR | Karaf local console user karaf | ShellUtil  
>   | 42 - org.apache.karaf.shell.core - 4.2.0.SNAPSHOT | 
> Exception caught while executing command
> java.lang.InterruptedException: null
>   at java.lang.Object.wait(Native Method) ~[?:?]
>   at java.lang.Object.wait(Object.java:502) [?:?]
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.start(CommandSessionImpl.java:772)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:295) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:168) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:148) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:168)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:363)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at java.lang.Thread.run(Thread.java:748) [?:?]
> 2017-07-31T15:34:20,192 | WARN  | pipe-update 42   | CommandExtension 
> | 42 - org.apache.karaf.shell.core - 4.2.0.SNAPSHOT | The wait for 
> bundle org.apache.karaf.service.core being started before destruction has 
> been interrupted.
> java.lang.InterruptedException: null
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
>  [?:?]
>   at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) 
> [?:?]
>   at 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension.destroy(CommandExtension.java:125)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.utils.extender.AbstractExtender$2.run(AbstractExtender.java:285)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   at 
> org.apache.felix.utils.extender.AbstractExtender.destroyExtension(AbstractExtender.java:307)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.utils.extender.AbstractExtender.stop(AbstractExtender.java:125)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.stop(Activator.java:128) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:719)
>  [?:?]
>   at org.apache.felix.framework.Felix.stopBundle(Felix.java:2632) [?:?]
>   at org.apache.felix.framework.Felix.updateBundle(Felix.java:2366) [?:?]
>   at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:1018) 
> [?:?]
>   at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:1004) 
> [?:?]
>   at org.apache.karaf.bundle.command.Update.doExecute(Update.java:57) 
> [21:org.apache.karaf.bundle.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.bundle.command.BundleCommand.execute(BundleCommand.java:46) 
> [21:org.apache.karaf.bundle.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand

[jira] [Commented] (KARAF-5279) InterruptedException when updating the shell.core bundle

2017-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider commented on KARAF-5279:


I did the commit with the wrong jra id 5072

> InterruptedException when updating the shell.core bundle
> 
>
> Key: KARAF-5279
> URL: https://issues.apache.org/jira/browse/KARAF-5279
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> update org.apache.karaf.shell.core
> There are two InterruptedExceptions. This issue is mainly about the second 
> one.
> It seems to hint that the start of a bundles extensions did not finish which 
> is not true.
> I found that started.await() always throws InterruptedException if the thread 
> was interrupted even if the countdown latch for started already finished.
> 2017-07-31T15:33:53,571 | ERROR | Karaf local console user karaf | ShellUtil  
>   | 42 - org.apache.karaf.shell.core - 4.2.0.SNAPSHOT | 
> Exception caught while executing command
> java.lang.InterruptedException: null
>   at java.lang.Object.wait(Native Method) ~[?:?]
>   at java.lang.Object.wait(Object.java:502) [?:?]
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.start(CommandSessionImpl.java:772)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:295) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:168) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:148) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:168)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:363)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at java.lang.Thread.run(Thread.java:748) [?:?]
> 2017-07-31T15:34:20,192 | WARN  | pipe-update 42   | CommandExtension 
> | 42 - org.apache.karaf.shell.core - 4.2.0.SNAPSHOT | The wait for 
> bundle org.apache.karaf.service.core being started before destruction has 
> been interrupted.
> java.lang.InterruptedException: null
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
>  [?:?]
>   at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) 
> [?:?]
>   at 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension.destroy(CommandExtension.java:125)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.utils.extender.AbstractExtender$2.run(AbstractExtender.java:285)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   at 
> org.apache.felix.utils.extender.AbstractExtender.destroyExtension(AbstractExtender.java:307)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.utils.extender.AbstractExtender.stop(AbstractExtender.java:125)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.stop(Activator.java:128) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:719)
>  [?:?]
>   at org.apache.felix.framework.Felix.stopBundle(Felix.java:2632) [?:?]
>   at org.apache.felix.framework.Felix.updateBundle(Felix.java:2366) [?:?]
>   at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:1018) 
> [?:?]
>   at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:1004) 
> [?:?]
>   at org.apache.karaf.bundle.command.Update.doExecute(Update.java:57) 
> [21:org.apache.karaf.bundle.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.bundle.command.BundleCommand.execute(BundleCommand.java:46) 
> [21:org.apache.karaf.bundle.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
>  [42:org.apache.karaf.shell

[jira] [Resolved] (KARAF-5279) InterruptedException when updating the shell.core bundle

2017-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider resolved KARAF-5279.

   Resolution: Fixed
Fix Version/s: 4.1.2

> InterruptedException when updating the shell.core bundle
> 
>
> Key: KARAF-5279
> URL: https://issues.apache.org/jira/browse/KARAF-5279
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> update org.apache.karaf.shell.core
> There are two InterruptedExceptions. This issue is mainly about the second 
> one.
> It seems to hint that the start of a bundles extensions did not finish which 
> is not true.
> I found that started.await() always throws InterruptedException if the thread 
> was interrupted even if the countdown latch for started already finished.
> 2017-07-31T15:33:53,571 | ERROR | Karaf local console user karaf | ShellUtil  
>   | 42 - org.apache.karaf.shell.core - 4.2.0.SNAPSHOT | 
> Exception caught while executing command
> java.lang.InterruptedException: null
>   at java.lang.Object.wait(Native Method) ~[?:?]
>   at java.lang.Object.wait(Object.java:502) [?:?]
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.start(CommandSessionImpl.java:772)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:295) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:168) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:148) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:168)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:363)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at java.lang.Thread.run(Thread.java:748) [?:?]
> 2017-07-31T15:34:20,192 | WARN  | pipe-update 42   | CommandExtension 
> | 42 - org.apache.karaf.shell.core - 4.2.0.SNAPSHOT | The wait for 
> bundle org.apache.karaf.service.core being started before destruction has 
> been interrupted.
> java.lang.InterruptedException: null
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
>  [?:?]
>   at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) 
> [?:?]
>   at 
> org.apache.karaf.shell.impl.action.osgi.CommandExtension.destroy(CommandExtension.java:125)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.utils.extender.AbstractExtender$2.run(AbstractExtender.java:285)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   at 
> org.apache.felix.utils.extender.AbstractExtender.destroyExtension(AbstractExtender.java:307)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.utils.extender.AbstractExtender.stop(AbstractExtender.java:125)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.Activator.stop(Activator.java:128) 
> [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:719)
>  [?:?]
>   at org.apache.felix.framework.Felix.stopBundle(Felix.java:2632) [?:?]
>   at org.apache.felix.framework.Felix.updateBundle(Felix.java:2366) [?:?]
>   at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:1018) 
> [?:?]
>   at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:1004) 
> [?:?]
>   at org.apache.karaf.bundle.command.Update.doExecute(Update.java:57) 
> [21:org.apache.karaf.bundle.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.bundle.command.BundleCommand.execute(BundleCommand.java:46) 
> [21:org.apache.karaf.bundle.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at 
> org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
>  [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
>   at org.apache.felix.

[jira] [Commented] (KARAF-5072) Add setting to ssh server for forcing a provided key

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5072:


Commit 90d3fa1641eea375220614886d2a0df494ae6d9a in karaf's branch 
refs/heads/karaf-4.1.x from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=90d3fa1 ]

[KARAF-5072] Avoid InterruptedException in case we do not have to wait for 
started


> Add setting to ssh server for forcing a provided key
> 
>
> Key: KARAF-5072
> URL: https://issues.apache.org/jira/browse/KARAF-5072
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> If karaf does not find a server key in etc/hosts.key it will create one and 
> save it. 
> If the key is present but invalid it will be overwritten by default.
> If overwrite=false in the settings and the provided key is invalid then karaf 
> will create a key on every first ssh connect after a restart. 
> I think it would be better to have a setting to force the provided key to be 
> used and throw an exception if it is invalid.



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


[jira] [Updated] (KARAF-5072) Add setting to ssh server for forcing a provided key

2017-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider updated KARAF-5072:
---
Fix Version/s: 4.2.0

> Add setting to ssh server for forcing a provided key
> 
>
> Key: KARAF-5072
> URL: https://issues.apache.org/jira/browse/KARAF-5072
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> If karaf does not find a server key in etc/hosts.key it will create one and 
> save it. 
> If the key is present but invalid it will be overwritten by default.
> If overwrite=false in the settings and the provided key is invalid then karaf 
> will create a key on every first ssh connect after a restart. 
> I think it would be better to have a setting to force the provided key to be 
> used and throw an exception if it is invalid.



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


[jira] [Commented] (KARAF-5072) Add setting to ssh server for forcing a provided key

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5072:


Commit 09d4d1e680524ce6f7dd672287f6aa87c2b60928 in karaf's branch 
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=09d4d1e ]

[KARAF-5072] Avoid InterruptedException in case we do not have to wait for 
started


> Add setting to ssh server for forcing a provided key
> 
>
> Key: KARAF-5072
> URL: https://issues.apache.org/jira/browse/KARAF-5072
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> If karaf does not find a server key in etc/hosts.key it will create one and 
> save it. 
> If the key is present but invalid it will be overwritten by default.
> If overwrite=false in the settings and the provided key is invalid then karaf 
> will create a key on every first ssh connect after a restart. 
> I think it would be better to have a setting to force the provided key to be 
> used and throw an exception if it is invalid.



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


[jira] [Created] (KARAF-5279) InterruptedException when updating the shell.core bundle

2017-07-31 Thread Christian Schneider (JIRA)
Christian Schneider created KARAF-5279:
--

 Summary: InterruptedException when updating the shell.core bundle
 Key: KARAF-5279
 URL: https://issues.apache.org/jira/browse/KARAF-5279
 Project: Karaf
  Issue Type: Bug
  Components: karaf-shell
Affects Versions: 4.1.1
Reporter: Christian Schneider
Assignee: Christian Schneider
 Fix For: 4.2.0


update org.apache.karaf.shell.core

There are two InterruptedExceptions. This issue is mainly about the second one.
It seems to hint that the start of a bundles extensions did not finish which is 
not true.
I found that started.await() always throws InterruptedException if the thread 
was interrupted even if the countdown latch for started already finished.

2017-07-31T15:33:53,571 | ERROR | Karaf local console user karaf | ShellUtil
| 42 - org.apache.karaf.shell.core - 4.2.0.SNAPSHOT | 
Exception caught while executing command
java.lang.InterruptedException: null
at java.lang.Object.wait(Native Method) ~[?:?]
at java.lang.Object.wait(Object.java:502) [?:?]
at 
org.apache.felix.gogo.runtime.CommandSessionImpl$JobImpl.start(CommandSessionImpl.java:772)
 [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:295) 
[42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:168) 
[42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:148) 
[42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at 
org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:168)
 [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at 
org.apache.karaf.shell.impl.console.ConsoleSessionImpl.run(ConsoleSessionImpl.java:363)
 [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at java.lang.Thread.run(Thread.java:748) [?:?]

2017-07-31T15:34:20,192 | WARN  | pipe-update 42   | CommandExtension   
  | 42 - org.apache.karaf.shell.core - 4.2.0.SNAPSHOT | The wait for bundle 
org.apache.karaf.service.core being started before destruction has been 
interrupted.
java.lang.InterruptedException: null
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1326)
 [?:?]
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:277) 
[?:?]
at 
org.apache.karaf.shell.impl.action.osgi.CommandExtension.destroy(CommandExtension.java:125)
 [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at 
org.apache.felix.utils.extender.AbstractExtender$2.run(AbstractExtender.java:285)
 [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
at 
org.apache.felix.utils.extender.AbstractExtender.destroyExtension(AbstractExtender.java:307)
 [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at 
org.apache.felix.utils.extender.AbstractExtender.stop(AbstractExtender.java:125)
 [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at 
org.apache.karaf.shell.impl.console.osgi.Activator.stop(Activator.java:128) 
[42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at 
org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:719)
 [?:?]
at org.apache.felix.framework.Felix.stopBundle(Felix.java:2632) [?:?]
at org.apache.felix.framework.Felix.updateBundle(Felix.java:2366) [?:?]
at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:1018) 
[?:?]
at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:1004) 
[?:?]
at org.apache.karaf.bundle.command.Update.doExecute(Update.java:57) 
[21:org.apache.karaf.bundle.core:4.2.0.SNAPSHOT]
at 
org.apache.karaf.bundle.command.BundleCommand.execute(BundleCommand.java:46) 
[21:org.apache.karaf.bundle.core:4.2.0.SNAPSHOT]
at 
org.apache.karaf.shell.impl.action.command.ActionCommand.execute(ActionCommand.java:84)
 [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at 
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:68)
 [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at 
org.apache.karaf.shell.impl.console.osgi.secured.SecuredCommand.execute(SecuredCommand.java:86)
 [42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:571) 
[42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at 
org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:497) 
[42:org.apache.karaf.shell.core:4.2.0.SNAPSHOT]
at org.apache.felix.gogo.runtime.Closure.execute(Closure.java:386) 
[42:org.apache.karaf.shell.co

[jira] [Resolved] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf

2017-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider resolved KARAF-5174.

Resolution: Fixed

This is resolved after updating to felix 5.6.6.

> Uninstalling feature using liquibase-slf4j crashes karaf
> 
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie" 
> GNU/linux 64bit
>Reporter: Steinar Bang
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log.gz, karaf.zip
>
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add 
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will now output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at 
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at 
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core 
> feature, the crash on uninstall doesn't happen.



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


[jira] [Resolved] (KARAF-5278) Update to felix framework 5.6.6

2017-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider resolved KARAF-5278.

Resolution: Fixed

> Update to felix framework 5.6.6
> ---
>
> Key: KARAF-5278
> URL: https://issues.apache.org/jira/browse/KARAF-5278
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Affects Versions: 4.2.0, 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> There is an issue about update of fragments in felix 5.6.4. This is fixed in 
> 5.6.6 so we should update to it.



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


[jira] [Commented] (KARAF-5278) Update to felix framework 5.6.6

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5278:


Commit fbb840a9adbbc3d0dd870669dc162f48eddc896a in karaf's branch 
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=fbb840a ]

[KARAF-5278] Upadate to felix framework 5.6.6


> Update to felix framework 5.6.6
> ---
>
> Key: KARAF-5278
> URL: https://issues.apache.org/jira/browse/KARAF-5278
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Affects Versions: 4.2.0, 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> There is an issue about update of fragments in felix 5.6.4. This is fixed in 
> 5.6.6 so we should update to it.



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


[jira] [Commented] (KARAF-5278) Update to felix framework 5.6.6

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5278:


Commit 5116ae91de754d656b6199929584e93db9026187 in karaf's branch 
refs/heads/karaf-4.1.x from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=5116ae9 ]

[KARAF-5278] Upadate to felix framework 5.6.6


> Update to felix framework 5.6.6
> ---
>
> Key: KARAF-5278
> URL: https://issues.apache.org/jira/browse/KARAF-5278
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Affects Versions: 4.2.0, 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> There is an issue about update of fragments in felix 5.6.4. This is fixed in 
> 5.6.6 so we should update to it.



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


[jira] [Created] (KARAF-5278) Update to felix framework 5.6.6

2017-07-31 Thread Christian Schneider (JIRA)
Christian Schneider created KARAF-5278:
--

 Summary: Update to felix framework 5.6.6
 Key: KARAF-5278
 URL: https://issues.apache.org/jira/browse/KARAF-5278
 Project: Karaf
  Issue Type: Dependency upgrade
  Components: karaf-core
Affects Versions: 4.1.1, 4.2.0
Reporter: Christian Schneider
Assignee: Christian Schneider
 Fix For: 4.2.0, 4.1.2


There is an issue about update of fragments in felix 5.6.4. This is fixed in 
5.6.6 so we should update to it.



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


[jira] [Commented] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf

2017-07-31 Thread Guillaume Nodet (JIRA)

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

Guillaume Nodet commented on KARAF-5174:


The restart is caused by https://issues.apache.org/jira/browse/FELIX-5649
A workaround is to remove the {{Require-Capability = 
osgi.ee;filter:=(&(osgi.ee=JavaSE)(version=1.6))}} header from the fragment.

> Uninstalling feature using liquibase-slf4j crashes karaf
> 
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie" 
> GNU/linux 64bit
>Reporter: Steinar Bang
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log.gz, karaf.zip
>
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add 
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will now output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at 
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at 
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core 
> feature, the crash on uninstall doesn't happen.



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


[jira] [Assigned] (KARAF-5174) Uninstalling feature using liquibase-slf4j crashes karaf

2017-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider reassigned KARAF-5174:
--

Assignee: Christian Schneider

> Uninstalling feature using liquibase-slf4j crashes karaf
> 
>
> Key: KARAF-5174
> URL: https://issues.apache.org/jira/browse/KARAF-5174
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.1.1
> Environment: Java 1.8 64 bit, windows 7 64bit, debian "jessie" 
> GNU/linux 64bit
>Reporter: Steinar Bang
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
> Attachments: karaf.log.gz, karaf.zip
>
>
> To reproduce:
> # clone this project and build it with maven:
> {noformat}
> mkdir -p ~/git
> cd ~/git
> git clone https://github.com/steinarb/liquibase-karaf-feature/
> cd liquibase-karaf-feature
> mvn clean install
> {noformat}
> # start karaf and give the following commands to the karaf console:
> {noformat}
> feature:repo-add 
> mvn:no.priv.bang.karaf/liquibase-core-karaf/LATEST/xml/features
> feature:install liquibase-core
> {noformat}
> # uninstall the feature
> {noformat}
> feature:uninstall liquibase-core
> {noformat}
> Karaf will now output the following and hang:
> {noformat}
> karaf@root()> feature:install liquibase-core
> karaf@root()> feature:uninstall liquibase-core
> karaf@root()>
> java.lang.IllegalStateException: No inital startlevel yet
> at 
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at 
> org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {noformat}
> On karaf 4.0.7 the crash on uninstall doesn't happen.
> If the liquibase-slf4j fragment bundle is removed from the liquibase-core 
> feature, the crash on uninstall doesn't happen.



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


[jira] [Resolved] (KARAF-5266) log commands should limit number of lines printed instead of number of log entries

2017-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider resolved KARAF-5266.

Resolution: Fixed

> log commands should limit number of lines printed instead of number of log 
> entries
> --
>
> Key: KARAF-5266
> URL: https://issues.apache.org/jira/browse/KARAF-5266
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> log:tail only shows the n last log entries. Still sometimes it looks like it 
> shows masses of log data. This is when you have stack traces in the log. A 
> full stack trace only counts as one line currently. I think a good 
> enhancement would be to change the logic to really only show n lines instead 
> of n log records.



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


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

2017-07-31 Thread Andrea Cosentino (JIRA)

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

Andrea Cosentino resolved KARAF-5277.
-
Resolution: Fixed

> 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: 4.2.0
>
>




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


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

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5277:


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

[KARAF-5277] Cellar: Bump to Kubernetes-client 2.5.7


> 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: 4.2.0
>
>




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


[jira] [Commented] (KARAF-5276) Do not use right prompt by default

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5276:


Commit 8b06470e6827d984a0c1f23ec92e66c722c802df in karaf's branch 
refs/heads/karaf-4.1.x from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=8b06470 ]

[KARAF-5276] Do not use right prompt by default


> Do not use right prompt by default
> --
>
> Key: KARAF-5276
> URL: https://issues.apache.org/jira/browse/KARAF-5276
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> Currently karaf displays the data on the right side of the prompt. This often 
> causes problems when changing the window size for me. 
> Besides I do not see any added value by seeing the time there.
> So I propose to switch off setting the right prompt by default.



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


[jira] [Commented] (KARAF-5276) Do not use right prompt by default

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5276:


Commit 160a835ac39ea284a171ed9c8d33037050ee635f in karaf's branch 
refs/heads/master from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=160a835 ]

[KARAF-5276] Do not use right prompt by default


> Do not use right prompt by default
> --
>
> Key: KARAF-5276
> URL: https://issues.apache.org/jira/browse/KARAF-5276
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> Currently karaf displays the data on the right side of the prompt. This often 
> causes problems when changing the window size for me. 
> Besides I do not see any added value by seeing the time there.
> So I propose to switch off setting the right prompt by default.



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


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

2017-07-31 Thread Andrea Cosentino (JIRA)
Andrea Cosentino created KARAF-5277:
---

 Summary: 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: 4.2.0






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


[jira] [Resolved] (KARAF-5276) Do not use right prompt by default

2017-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider resolved KARAF-5276.

Resolution: Fixed

> Do not use right prompt by default
> --
>
> Key: KARAF-5276
> URL: https://issues.apache.org/jira/browse/KARAF-5276
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.1
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> Currently karaf displays the data on the right side of the prompt. This often 
> causes problems when changing the window size for me. 
> Besides I do not see any added value by seeing the time there.
> So I propose to switch off setting the right prompt by default.



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


[jira] [Created] (KARAF-5276) Do not use right prompt by default

2017-07-31 Thread Christian Schneider (JIRA)
Christian Schneider created KARAF-5276:
--

 Summary: Do not use right prompt by default
 Key: KARAF-5276
 URL: https://issues.apache.org/jira/browse/KARAF-5276
 Project: Karaf
  Issue Type: Bug
  Components: karaf-shell
Affects Versions: 4.1.1
Reporter: Christian Schneider
Assignee: Christian Schneider
 Fix For: 4.2.0, 4.1.2


Currently karaf displays the data on the right side of the prompt. This often 
causes problems when changing the window size for me. 
Besides I do not see any added value by seeing the time there.

So I propose to switch off setting the right prompt by default.




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


[jira] [Updated] (KARAF-5266) log commands should limit number of lines printed instead of number of log entries

2017-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider updated KARAF-5266:
---
Fix Version/s: 4.1.2

> log commands should limit number of lines printed instead of number of log 
> entries
> --
>
> Key: KARAF-5266
> URL: https://issues.apache.org/jira/browse/KARAF-5266
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> log:tail only shows the n last log entries. Still sometimes it looks like it 
> shows masses of log data. This is when you have stack traces in the log. A 
> full stack trace only counts as one line currently. I think a good 
> enhancement would be to change the logic to really only show n lines instead 
> of n log records.



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


[jira] [Commented] (KARAF-5267) Karaf does not work correctly after log:tail

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5267:


Commit fd4f64006a0efe2a461af225124d25ad33b22a25 in karaf's branch 
refs/heads/karaf-4.1.x from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=fd4f640 ]

[KARAF-5267] Documentation and move flush to correct position


> Karaf does not work correctly after log:tail
> 
>
> Key: KARAF-5267
> URL: https://issues.apache.org/jira/browse/KARAF-5267
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> To reproduce:
> Start karaf
> log:tail
> Ctrl-C
> Hit the up key
> The shell will display OC and not go up the history.
> I think this is because the threads are not stopped correctly.



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


[jira] [Commented] (KARAF-5267) Karaf does not work correctly after log:tail

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5267:


Commit 5c0800e4b7717f2a476ecb3552eaa41f6b3c7fed in karaf's branch 
refs/heads/karaf-4.1.x from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=5c0800e ]

[KARAF-5267] Redesigned log:tail to not start threads


> Karaf does not work correctly after log:tail
> 
>
> Key: KARAF-5267
> URL: https://issues.apache.org/jira/browse/KARAF-5267
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> To reproduce:
> Start karaf
> log:tail
> Ctrl-C
> Hit the up key
> The shell will display OC and not go up the history.
> I think this is because the threads are not stopped correctly.



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


[jira] [Commented] (KARAF-5266) log commands should limit number of lines printed instead of number of log entries

2017-07-31 Thread ASF subversion and git services (JIRA)

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

ASF subversion and git services commented on KARAF-5266:


Commit 5e2f07e442939e667a2653cc10ce3d6834899360 in karaf's branch 
refs/heads/karaf-4.1.x from [~ch...@die-schneider.net]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=5e2f07e ]

[KARAF-5266] Limit log entries displayed on tail to 50 by default


> log commands should limit number of lines printed instead of number of log 
> entries
> --
>
> Key: KARAF-5266
> URL: https://issues.apache.org/jira/browse/KARAF-5266
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0
>
>
> log:tail only shows the n last log entries. Still sometimes it looks like it 
> shows masses of log data. This is when you have stack traces in the log. A 
> full stack trace only counts as one line currently. I think a good 
> enhancement would be to change the logic to really only show n lines instead 
> of n log records.



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


[jira] [Updated] (KARAF-5267) Karaf does not work correctly after log:tail

2017-07-31 Thread Christian Schneider (JIRA)

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

Christian Schneider updated KARAF-5267:
---
Fix Version/s: 4.1.2

> Karaf does not work correctly after log:tail
> 
>
> Key: KARAF-5267
> URL: https://issues.apache.org/jira/browse/KARAF-5267
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.2.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.2.0, 4.1.2
>
>
> To reproduce:
> Start karaf
> log:tail
> Ctrl-C
> Hit the up key
> The shell will display OC and not go up the history.
> I think this is because the threads are not stopped correctly.



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