[jira] [Commented] (KARAF-4220) Upgrade to eclipselink 2.6.1

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4220:


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

KARAF-4220 - Upgrade to eclipselink 2.6.1


> Upgrade to eclipselink 2.6.1
> 
>
> Key: KARAF-4220
> URL: https://issues.apache.org/jira/browse/KARAF-4220
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-feature
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4218) JAAS boot classes are not marked serializable

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4218:


Commit fa5f3a6e5ff2e68574890aa46b46f50d97db524f in karaf's branch 
refs/heads/master from [~kurt.westerf...@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=fa5f3a6 ]

[KARAF-4218] Mark Principal classes as Serializable


> JAAS boot classes are not marked serializable
> -
>
> Key: KARAF-4218
> URL: https://issues.apache.org/jira/browse/KARAF-4218
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-osgi, karaf-security
>Affects Versions: 4.0.3
>Reporter: Kurt Westerfeld
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> The principal classes in the jaas/boot module 
> (org.apache.karaf.jaas.boot.principal package) are not marked serializable.  
> I am trying to setup clustering for a hawtio-based console, and the app 
> stores javax.security.Subject in session data, which is not serializable 
> because org.apache.karaf.jaas.boot.principal.UserPrincipal/etc are not marked 
> serializable. 
> Setting up a configuration for this is easy.  Simply create a WAB project 
> that has WEB-INF/jetty-web.xml as follows.  The session manager in this case 
> simply causes the sessions to serialize to disk.  Most clustering solutions 
> rely on serializable session data.
> {noformat}
> 
>  "http://www.eclipse.org/jetty/configure.dtd;>
> 
>   
> 
>   
> 
>   ${karaf.data}/sessions
>   10
> 
>   
> 
>   
> 
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4132) assembly archetype should remove runtime scope to the standard features XML

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4132:


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

KARAF-4132 - Don't define runtime scope for standard feature in the assembly 
archetype


> assembly archetype should remove runtime scope to the standard features XML
> ---
>
> Key: KARAF-4132
> URL: https://issues.apache.org/jira/browse/KARAF-4132
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-archetypes
>Affects Versions: 4.0.2, 4.0.3
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> The assembly archetype should not define the standard features XML with 
> runtime scope, as it can produce error with the user define startupFeatures.
> More over, the documentation about how to create custom distribution should 
> be improve as it's not really clear to the users.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4240) Provide Asciidoc command help printer

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4240:


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

KARAF-4240 - Add asciidoc command help printer


> Provide Asciidoc command help printer
> -
>
> Key: KARAF-4240
> URL: https://issues.apache.org/jira/browse/KARAF-4240
> Project: Karaf
>  Issue Type: New Feature
>  Components: karaf-documentation, karaf-tooling
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>
> In preparation for the switch to asciidoc for the documentation, we need a 
> command help printer that generate asciidoc format.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4031) Unresolved repository inside the feature causes Karaf freezing during startup

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4031:


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

KARAF-4031 - Fix repo loading

KARAF-4083 - Fix repo loading


> Unresolved repository inside the feature causes Karaf freezing during startup
> -
>
> Key: KARAF-4031
> URL: https://issues.apache.org/jira/browse/KARAF-4031
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.1
> Environment: Windows
>Reporter: Andrei Shakirin
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> I have observed following behavior: there is a feature containing a 
> repository URL inside the feature.xml:
> {code:xml}
> 
>  name="${project.artifactId}-${project.version}"
> xmlns="http://karaf.apache.org/xmlns/features/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
> xsi:schemaLocation="http://karaf.apache.org/xmlns/features/v1.0.0 
> http://karaf.apache.org/xmlns/features/v1.0.0 ">
> mvn:org.mycompany/thirdparty-features/9.9.9/xml
> 
> thirdparty-commons
> 
> 
> {code}
> The repository URL mvn:org.mycompany/thirdparty-features/9.9.9/xml is not 
> exist and cannot be resolved.
> I specify the feature URL in org.apache.karaf.features.cfg 
> featuresRepositories, but NOT mention the feature in featuresBoot:
> {code:xml}
> featuresRepositories = \
> mvn:org.apache.karaf.features/enterprise/4.0.1/xml/features, \
> mvn:org.apache.karaf.features/framework/4.0.1/xml/features, \
> mvn:org.apache.karaf.features/spring/4.0.1/xml/features, \
> mvn:org.apache.karaf.features/standard/4.0.1/xml/features,\
> mvn:org.mycompany/test-bad/1.0.0-SNAPSHOT/xml
> #
> # Comma separated list of features to install at startup
> #
> featuresBoot = \
> aries-blueprint, \
> bundle, \
> config, \
> deployer, \
> diagnostic, \
> feature, \
> instance, \
> jaas, \
> kar, \
> log, \
> management, \
> package, \
> service, \
> shell, \
> shell-compat, \
> ssh, \
> system, \
> wrap
> {code}
> Current behavior:
> 1) Karaf writes error message in the log file:
> java.io.IOException: Error resolving artifact 
> org.mycompany:thirdparty-features:xml:9.9.9: Could not find artifact 
> org.mycompany:thirdparty-features:xml:9.9.9 in central 
> (http://repo1.maven.org/maven2/) : 
> mvn:org.mycompany/thirdparty-features/9.9.9/xml
> (absolutely correct)
> 2) further startup process is completely blocked (problem)
> Expected behavior: write error message and continue startup process: feature 
> is not specified in featuresBoot and must not be installed.
> Interesting, if unresolved feature URL is specified directly in 
> featuresRepositories, Karaf proceed it correctly: writes error message, but 
> continues startup. Blocking appears only if unresolved URL is specified 
> inside the feature.xml.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4083) Reference to the invalid repository in feature file breaks commands

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4083:


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

KARAF-4031 - Fix repo loading

KARAF-4083 - Fix repo loading


> Reference to the invalid repository in feature file breaks commands
> ---
>
> Key: KARAF-4083
> URL: https://issues.apache.org/jira/browse/KARAF-4083
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.2
>Reporter: Alexander Osadchiy
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.0.4
>
>
> Feature commands don't work after registering feature repository with 
> reference to the invalid repository.
> There is a feature repository "parent-1.0-features.xml" with reference to the 
> invalid repository "child-1.0-features.xml" (e.g. with broken xml structure).
> When I add parent repo via command:
> karaf@root()> feature:repo-add mvn:parent/1.0/xml/features
> Command will add parent repo and child repo, but after this feature:* 
> commands will not work at all, with exception like this:
> karaf@root()> feature:repo-list 
> Error executing command: Unable to load mvn:child/1.0/xml/features : 
> mvn:child/1.0/xml/features
> This child repository can't be removed using feature:repo-remove and that 
> leads to unusable container.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4083) Reference to the invalid repository in feature file breaks commands

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4083:


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

KARAF-4031 - Avoid to block boot features when a repository can't be loaded

KARAF-4083 - Avoid to break features service when a repository can't be loaded


> Reference to the invalid repository in feature file breaks commands
> ---
>
> Key: KARAF-4083
> URL: https://issues.apache.org/jira/browse/KARAF-4083
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.2
>Reporter: Alexander Osadchiy
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.0.4
>
>
> Feature commands don't work after registering feature repository with 
> reference to the invalid repository.
> There is a feature repository "parent-1.0-features.xml" with reference to the 
> invalid repository "child-1.0-features.xml" (e.g. with broken xml structure).
> When I add parent repo via command:
> karaf@root()> feature:repo-add mvn:parent/1.0/xml/features
> Command will add parent repo and child repo, but after this feature:* 
> commands will not work at all, with exception like this:
> karaf@root()> feature:repo-list 
> Error executing command: Unable to load mvn:child/1.0/xml/features : 
> mvn:child/1.0/xml/features
> This child repository can't be removed using feature:repo-remove and that 
> leads to unusable container.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4246) sshd 0.14.0 breaks client timeout

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4246:


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

KARAF-4246 - Add support of idle timeout to the client


> sshd 0.14.0 breaks client timeout
> -
>
> Key: KARAF-4246
> URL: https://issues.apache.org/jira/browse/KARAF-4246
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 3.0.5, 4.0.3
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>
> karaf-client.jar in Karaf version 3.0.5 has a new client idle timeout added
> as a result of ugprading to MINA SSHD 0.14.0.
> This causes the client to time out after 10 minutes even though the server
> idle timeout setting is different.
> Here's a patch:
> {code}
> Index: src/main/java/org/apache/karaf/client/ClientConfig.java
> ===
> --- src/main/java/org/apache/karaf/client/ClientConfig.java   (revision 33766)
> +++ src/main/java/org/apache/karaf/client/ClientConfig.java   (revision 33767)
> @@ -38,6 +38,7 @@
>  private int level;
>  private int retryAttempts;
>  private int retryDelay;
> +private long idleTimeout;
>  private boolean batch;
>  private String file = null;
>  private String keyFile = null;
> @@ -64,6 +65,7 @@
>  level = Integer.parseInt(shellCfg.getProperty("logLevel", "1"));
>  retryAttempts = 0;
>  retryDelay = 2;
> +idleTimeout =
> Long.parseLong(shellCfg.getProperty("sshIdleTimeout"));
>  batch = false;
>  file = null;
>  user = null;
> @@ -293,4 +295,8 @@
>  public String getKeyFile() {
>  return keyFile;
>  }
> +
> +public long getIdleTimeout() {
> +  return idleTimeout;
> +}
>  }
> Index: src/main/java/org/apache/karaf/client/Main.java
> ===
> --- src/main/java/org/apache/karaf/client/Main.java   (revision 33766)
> +++ src/main/java/org/apache/karaf/client/Main.java   (revision 33767)
> @@ -37,6 +37,7 @@
>  import org.apache.sshd.client.UserInteraction;
>  import org.apache.sshd.client.channel.ChannelShell;
>  import org.apache.sshd.client.future.ConnectFuture;
> +import org.apache.sshd.common.FactoryManager;
>  import org.apache.sshd.common.RuntimeSshException;
>  import org.apache.sshd.common.keyprovider.FileKeyPairProvider;
>  import org.fusesource.jansi.AnsiConsole;
> @@ -78,6 +79,7 @@
>  int exitStatus = 0;
>  try {
>  client = SshClient.setUpDefaultClient();
> +client.getProperties().put(FactoryManager.IDLE_TIMEOUT,
> String.valueOf(config.getIdleTimeout()));
>  setupAgent(config.getUser(), config.getKeyFile(), client);
>  final Console console = System.console();
>  if (console != null) {
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4031) Unresolved repository inside the feature causes Karaf freezing during startup

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4031:


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

KARAF-4031 - Avoid to block boot features when a repository can't be loaded

KARAF-4083 - Avoid to break features service when a repository can't be loaded


> Unresolved repository inside the feature causes Karaf freezing during startup
> -
>
> Key: KARAF-4031
> URL: https://issues.apache.org/jira/browse/KARAF-4031
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.1
> Environment: Windows
>Reporter: Andrei Shakirin
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> I have observed following behavior: there is a feature containing a 
> repository URL inside the feature.xml:
> {code:xml}
> 
>  name="${project.artifactId}-${project.version}"
> xmlns="http://karaf.apache.org/xmlns/features/v1.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; 
> xsi:schemaLocation="http://karaf.apache.org/xmlns/features/v1.0.0 
> http://karaf.apache.org/xmlns/features/v1.0.0 ">
> mvn:org.mycompany/thirdparty-features/9.9.9/xml
> 
> thirdparty-commons
> 
> 
> {code}
> The repository URL mvn:org.mycompany/thirdparty-features/9.9.9/xml is not 
> exist and cannot be resolved.
> I specify the feature URL in org.apache.karaf.features.cfg 
> featuresRepositories, but NOT mention the feature in featuresBoot:
> {code:xml}
> featuresRepositories = \
> mvn:org.apache.karaf.features/enterprise/4.0.1/xml/features, \
> mvn:org.apache.karaf.features/framework/4.0.1/xml/features, \
> mvn:org.apache.karaf.features/spring/4.0.1/xml/features, \
> mvn:org.apache.karaf.features/standard/4.0.1/xml/features,\
> mvn:org.mycompany/test-bad/1.0.0-SNAPSHOT/xml
> #
> # Comma separated list of features to install at startup
> #
> featuresBoot = \
> aries-blueprint, \
> bundle, \
> config, \
> deployer, \
> diagnostic, \
> feature, \
> instance, \
> jaas, \
> kar, \
> log, \
> management, \
> package, \
> service, \
> shell, \
> shell-compat, \
> ssh, \
> system, \
> wrap
> {code}
> Current behavior:
> 1) Karaf writes error message in the log file:
> java.io.IOException: Error resolving artifact 
> org.mycompany:thirdparty-features:xml:9.9.9: Could not find artifact 
> org.mycompany:thirdparty-features:xml:9.9.9 in central 
> (http://repo1.maven.org/maven2/) : 
> mvn:org.mycompany/thirdparty-features/9.9.9/xml
> (absolutely correct)
> 2) further startup process is completely blocked (problem)
> Expected behavior: write error message and continue startup process: feature 
> is not specified in featuresBoot and must not be installed.
> Interesting, if unresolved feature URL is specified directly in 
> featuresRepositories, Karaf proceed it correctly: writes error message, but 
> continues startup. Blocking appears only if unresolved URL is specified 
> inside the feature.xml.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-3679) Change current documentation from Scalate to Asciidoc

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-3679:


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

KARAF-3679 - Switch user guide to asciidoc


> Change current documentation from Scalate to Asciidoc
> -
>
> Key: KARAF-3679
> URL: https://issues.apache.org/jira/browse/KARAF-3679
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-documentation
>Reporter: Morgan hautman
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-3100) Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-3100:


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

KARAF-3100 -  in a feature are now store in a cfg file as we do with 
config:* commands. close #43


> Add Option To Create Config Files For Feature Configs Instead Of Importing 
> Directly Into Config Admin
> -
>
> Key: KARAF-3100
> URL: https://issues.apache.org/jira/browse/KARAF-3100
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Affects Versions: 3.0.1
>Reporter: Gareth Collins
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>
> I have created a pull request for this here:
> https://github.com/apache/karaf/pull/43
> As the title says, this allows karaf to be configured to output feature 
> configurations to config file...which I believe are easier to manage. Let me 
> know what you think. If it looks OK, would it be possible to merge soon (e.g. 
> karaf 3.0.2 :))? The changes are very localized.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-3100) Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-3100:


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

KARAF-3100 - Fix property key in feature config installer


> Add Option To Create Config Files For Feature Configs Instead Of Importing 
> Directly Into Config Admin
> -
>
> Key: KARAF-3100
> URL: https://issues.apache.org/jira/browse/KARAF-3100
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Affects Versions: 3.0.1
>Reporter: Gareth Collins
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>
> I have created a pull request for this here:
> https://github.com/apache/karaf/pull/43
> As the title says, this allows karaf to be configured to output feature 
> configurations to config file...which I believe are easier to manage. Let me 
> know what you think. If it looks OK, would it be possible to merge soon (e.g. 
> karaf 3.0.2 :))? The changes are very localized.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-3100) Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-3100:


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

KARAF-3100 -  in a feature are now store in a cfg file as we do with 
config:* commands


> Add Option To Create Config Files For Feature Configs Instead Of Importing 
> Directly Into Config Admin
> -
>
> Key: KARAF-3100
> URL: https://issues.apache.org/jira/browse/KARAF-3100
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Affects Versions: 3.0.1
>Reporter: Gareth Collins
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>
> I have created a pull request for this here:
> https://github.com/apache/karaf/pull/43
> As the title says, this allows karaf to be configured to output feature 
> configurations to config file...which I believe are easier to manage. Let me 
> know what you think. If it looks OK, would it be possible to merge soon (e.g. 
> karaf 3.0.2 :))? The changes are very localized.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4246) sshd 0.14.0 breaks client timeout

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4246:


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

KARAF-4246 - Add support of idle timeout to the client


> sshd 0.14.0 breaks client timeout
> -
>
> Key: KARAF-4246
> URL: https://issues.apache.org/jira/browse/KARAF-4246
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 3.0.5, 4.0.3
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>
> karaf-client.jar in Karaf version 3.0.5 has a new client idle timeout added
> as a result of ugprading to MINA SSHD 0.14.0.
> This causes the client to time out after 10 minutes even though the server
> idle timeout setting is different.
> Here's a patch:
> {code}
> Index: src/main/java/org/apache/karaf/client/ClientConfig.java
> ===
> --- src/main/java/org/apache/karaf/client/ClientConfig.java   (revision 33766)
> +++ src/main/java/org/apache/karaf/client/ClientConfig.java   (revision 33767)
> @@ -38,6 +38,7 @@
>  private int level;
>  private int retryAttempts;
>  private int retryDelay;
> +private long idleTimeout;
>  private boolean batch;
>  private String file = null;
>  private String keyFile = null;
> @@ -64,6 +65,7 @@
>  level = Integer.parseInt(shellCfg.getProperty("logLevel", "1"));
>  retryAttempts = 0;
>  retryDelay = 2;
> +idleTimeout =
> Long.parseLong(shellCfg.getProperty("sshIdleTimeout"));
>  batch = false;
>  file = null;
>  user = null;
> @@ -293,4 +295,8 @@
>  public String getKeyFile() {
>  return keyFile;
>  }
> +
> +public long getIdleTimeout() {
> +  return idleTimeout;
> +}
>  }
> Index: src/main/java/org/apache/karaf/client/Main.java
> ===
> --- src/main/java/org/apache/karaf/client/Main.java   (revision 33766)
> +++ src/main/java/org/apache/karaf/client/Main.java   (revision 33767)
> @@ -37,6 +37,7 @@
>  import org.apache.sshd.client.UserInteraction;
>  import org.apache.sshd.client.channel.ChannelShell;
>  import org.apache.sshd.client.future.ConnectFuture;
> +import org.apache.sshd.common.FactoryManager;
>  import org.apache.sshd.common.RuntimeSshException;
>  import org.apache.sshd.common.keyprovider.FileKeyPairProvider;
>  import org.fusesource.jansi.AnsiConsole;
> @@ -78,6 +79,7 @@
>  int exitStatus = 0;
>  try {
>  client = SshClient.setUpDefaultClient();
> +client.getProperties().put(FactoryManager.IDLE_TIMEOUT,
> String.valueOf(config.getIdleTimeout()));
>  setupAgent(config.getUser(), config.getKeyFile(), client);
>  final Console console = System.console();
>  if (console != null) {
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4247) Issues with LDAP caching

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4247:


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

[KARAF-4247] Issues with LDAP caching


> Issues with LDAP caching
> 
>
> Key: KARAF-4247
> URL: https://issues.apache.org/jira/browse/KARAF-4247
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-security
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
>
> There are several known issues with the LDAPCache code.
> 1) The cache is not cleared when the LDAPLoginModule configuration is 
> changed, leaving stale data in the cache.
> 2) No way to disable the cache. Setting the cache time to live to zero has no 
> effect. (I may just be setting the time to live incorrectly).
> 3) The cache does not listen to change events from the LDAP server. This 
> leaves stale entries in the cache when the ldap server is updated. The 
> SimpleCachedLDAPAuthorizationMap used in active-mq registers these listeners.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4197) Upgrade to blueprint.core-1.5.0, jpa-2.3.0, transaction.blueprint-2.1.0

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4197:


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

[KARAF-4197] Upgrade to blueprint.core-1.5.0, jpa-2.3.0, 
transaction.blueprint-2.1.0


> Upgrade to blueprint.core-1.5.0, jpa-2.3.0, transaction.blueprint-2.1.0
> ---
>
> Key: KARAF-4197
> URL: https://issues.apache.org/jira/browse/KARAF-4197
> Project: Karaf
>  Issue Type: Dependency upgrade
>Affects Versions: 4.0.3
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4166) Add karaf.lock.exclusive property to prevent a slave instance to start

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4166:


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

KARAF-4166 - Introduce karaf.lock.exclusive property to prevent slave instance 
to start


> Add karaf.lock.exclusive property to prevent a slave instance to start
> --
>
> Key: KARAF-4166
> URL: https://issues.apache.org/jira/browse/KARAF-4166
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>
> By default, a Karaf slave instance starts to be able to "pre-install" bundle 
> there.
> We can enhance the SimpleLockFile (controled a karaf.lock.exclusive property) 
> like this:
> {code}
> boolean lock() throws Exception {
>  boolean locked = super.lock();
>  if (!locked) throw new RuntimeException("startup aborted");
>  return true;
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4166) Add karaf.lock.exclusive property to prevent a slave instance to start

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4166:


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

KARAF-4166 - Introduce karaf.lock.exclusive property to prevent slave instance 
to start


> Add karaf.lock.exclusive property to prevent a slave instance to start
> --
>
> Key: KARAF-4166
> URL: https://issues.apache.org/jira/browse/KARAF-4166
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>
> By default, a Karaf slave instance starts to be able to "pre-install" bundle 
> there.
> We can enhance the SimpleLockFile (controled a karaf.lock.exclusive property) 
> like this:
> {code}
> boolean lock() throws Exception {
>  boolean locked = super.lock();
>  if (!locked) throw new RuntimeException("startup aborted");
>  return true;
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4166) Add karaf.lock.slave.block property to prevent a slave instance to start

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4166:


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

KARAF-4166 - Rename karaf.lock.exclusive property to karaf.lock.slave.block


> Add karaf.lock.slave.block property to prevent a slave instance to start
> 
>
> Key: KARAF-4166
> URL: https://issues.apache.org/jira/browse/KARAF-4166
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>
> By default, a Karaf slave instance starts to be able to "pre-install" bundle 
> there.
> In some use case, we want to block the startup of the slave instances.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4252) scr feature doesn't install the WebConsole DS plugin

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4252:


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

KARAF-4252 - Add felix inventory bundle in scr feature, required by DS 
WebConsole plugin


> scr feature doesn't install the WebConsole DS plugin
> 
>
> Key: KARAF-4252
> URL: https://issues.apache.org/jira/browse/KARAF-4252
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature, karaf-webconsole
>Affects Versions: 4.0.3
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> Even if the webconsole feature is installed, and so the condition satisfied, 
> the scr feature doesn't install the DS WebConsole plugin.
> The issue is this plugin requires Felix Inventory dependency.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4197) Upgrade to blueprint.core-1.5.0, jpa-2.3.0, transaction.blueprint-2.1.0

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4197:


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

KARAF-4197 - Upgrade to Aries Transaction Blueprint 2.1.0


> Upgrade to blueprint.core-1.5.0, jpa-2.3.0, transaction.blueprint-2.1.0
> ---
>
> Key: KARAF-4197
> URL: https://issues.apache.org/jira/browse/KARAF-4197
> Project: Karaf
>  Issue Type: Dependency upgrade
>Affects Versions: 4.0.3
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4166) Add karaf.lock.slave.block property to prevent a slave instance to start

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4166:


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

KARAF-4166 - Rename karaf.lock.exclusive property to karaf.lock.slave.block


> Add karaf.lock.slave.block property to prevent a slave instance to start
> 
>
> Key: KARAF-4166
> URL: https://issues.apache.org/jira/browse/KARAF-4166
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>
> By default, a Karaf slave instance starts to be able to "pre-install" bundle 
> there.
> In some use case, we want to block the startup of the slave instances.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4230) Upgrade to Aries Blueprint Core 1.5.0

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4230:


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

KARAF-4230 - Upgrade to Aries Blueprint Core 1.5.0


> Upgrade to Aries Blueprint Core 1.5.0
> -
>
> Key: KARAF-4230
> URL: https://issues.apache.org/jira/browse/KARAF-4230
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-222) Provide karaf:run, karaf:deploy, karaf:client Maven goals

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-222:
---

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

KARAF-222 - Provide karaf:run, karaf:deploy, karaf:client Maven goals


> Provide karaf:run, karaf:deploy, karaf:client Maven goals
> -
>
> Key: KARAF-222
> URL: https://issues.apache.org/jira/browse/KARAF-222
> Project: Karaf
>  Issue Type: New Feature
>  Components: karaf-tooling
>Reporter: james strachan
>Assignee: Jean-Baptiste Onofré
> Attachments: KARAF-222-run-mojo-1.diff
>
>
> Did a quick google & couldn't see one yet - please close if there is one 
> already :)
> The really nice thing about jetty:run is it watches the source code & 
> target/classes dir & auto redeploys on change, so there's no deploy step - 
> you just hack & compile (which your IDE or incremental compile can do - e.g. 
> "mvn scala:cc").
> For added bonus would be being able to add some extra bundles, so it can be a 
> RAD way to hack bundles. Maybe folks could have some integration junit tests 
> automatically rerun whenever the bundle is redeployed?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4226) Web Console is missing package exports for bundleinfo and i18n

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4226:


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

KARAF-4226 Web Console is missing package exports for bundleinfo and i18n

add missing package exports


> Web Console is missing package exports for bundleinfo and i18n
> --
>
> Key: KARAF-4226
> URL: https://issues.apache.org/jira/browse/KARAF-4226
> Project: Karaf
>  Issue Type: Bug
>  Components: webconsole
>Affects Versions: 4.0.3
>Reporter: Oliver Lietz
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> Felix:
> {noformat}
> org.apache.felix.webconsole,version=3.2.0
> org.apache.felix.webconsole.bundleinfo,version=1.0.0
> org.apache.felix.webconsole.i18n,version=1.0.0
> {noformat}
> Karaf:
> {noformat}
> org.apache.felix.webconsole,version=3.1.2
> org.json,version=0.0.0.20140107
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4239) Upgrade to Pax-Logging 1.8.5

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4239:


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

[KARAF-4239] - Upgrade to Pax-Logging 1.8.5


> Upgrade to Pax-Logging 1.8.5
> 
>
> Key: KARAF-4239
> URL: https://issues.apache.org/jira/browse/KARAF-4239
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Affects Versions: 4.0.3
>Reporter: Achim Nierbeck
>Assignee: Achim Nierbeck
> Fix For: 4.0.4
>
>
> Pax-Logging 1.8.5 does also export the log4j 2 apis, therefore an upgrade to 
> this version is needed. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4238) Upgrade to Pax URL 2.4.5

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4238:


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

KARAF-4238 - Upgrade to Pax URL 2.4.5


> Upgrade to Pax URL 2.4.5
> 
>
> Key: KARAF-4238
> URL: https://issues.apache.org/jira/browse/KARAF-4238
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.6, 4.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4238) Upgrade to Pax URL 2.4.5

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4238:


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

KARAF-4238 - Upgrade to Pax URL 2.4.5


> Upgrade to Pax URL 2.4.5
> 
>
> Key: KARAF-4238
> URL: https://issues.apache.org/jira/browse/KARAF-4238
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4228) Upgrade to Aries Subsystem 2.0.8

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4228:


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

KARAF-4228 - Upgrade to Aries Subsystem 2.0.8


> Upgrade to Aries Subsystem 2.0.8
> 
>
> Key: KARAF-4228
> URL: https://issues.apache.org/jira/browse/KARAF-4228
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-3679) Change current documentation from Scalate to Asciidoc

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-3679:


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

KARAF-3679 - Fix typo in Cave documentation


> Change current documentation from Scalate to Asciidoc
> -
>
> Key: KARAF-3679
> URL: https://issues.apache.org/jira/browse/KARAF-3679
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-documentation
>Reporter: Morgan hautman
>Assignee: Jean-Baptiste Onofré
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-3679) Change current documentation from Scalate to Asciidoc

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-3679:


Commit 122506889de9a5998d9b78a4e856dd4169f332b8 in karaf-cave's branch 
refs/heads/cave-3.x from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf-cave.git;h=1225068 ]

KARAF-3679 - Use asciidoc for Cave documentation


> Change current documentation from Scalate to Asciidoc
> -
>
> Key: KARAF-3679
> URL: https://issues.apache.org/jira/browse/KARAF-3679
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-documentation
>Reporter: Morgan hautman
>Assignee: Jean-Baptiste Onofré
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4233) Upgrade to Aries JPA Container 1.0.3

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4233:


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

KARAF-4233 - Upgrade to Aries JPA Container 1.0.3


> Upgrade to Aries JPA Container 1.0.3
> 
>
> Key: KARAF-4233
> URL: https://issues.apache.org/jira/browse/KARAF-4233
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4227) Upgrade to Pax-exam 4.8.0

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4227:


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

[KARAF-4227] Upgrade to Pax-exam 4.8.0


> Upgrade to Pax-exam 4.8.0
> -
>
> Key: KARAF-4227
> URL: https://issues.apache.org/jira/browse/KARAF-4227
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Andrea Cosentino
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4228) Upgrade to Aries Subsystem 2.0.8

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4228:


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

KARAF-4228 - Upgrade to Aries Subsystem 2.0.8


> Upgrade to Aries Subsystem 2.0.8
> 
>
> Key: KARAF-4228
> URL: https://issues.apache.org/jira/browse/KARAF-4228
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4243) Add apache ignite to feature repo:add shorthand

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4243:


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

KARAF-4243 - Add Apache Ignite features repository


> Add apache ignite to feature repo:add shorthand
> ---
>
> Key: KARAF-4243
> URL: https://issues.apache.org/jira/browse/KARAF-4243
> Project: Karaf
>  Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> See
> https://apacheignite.readme.io/docs/osgi-installation-in-karaf
> We should add a shorthand so you can do
> feature:repo-add ignite 1.5.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4239) Upgrade to Pax-Logging 1.8.5

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4239:


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

KARAF-4239 - Upgrade to Pax Logging 1.8.5


> Upgrade to Pax-Logging 1.8.5
> 
>
> Key: KARAF-4239
> URL: https://issues.apache.org/jira/browse/KARAF-4239
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Affects Versions: 4.0.3
>Reporter: Achim Nierbeck
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> Pax-Logging 1.8.5 does also export the log4j 2 apis, therefore an upgrade to 
> this version is needed. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4240) Provide Asciidoc command help printer

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4240:


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

KARAF-4240 - Add asciidoc command help printer


> Provide Asciidoc command help printer
> -
>
> Key: KARAF-4240
> URL: https://issues.apache.org/jira/browse/KARAF-4240
> Project: Karaf
>  Issue Type: New Feature
>  Components: karaf-documentation, karaf-tooling
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> In preparation for the switch to asciidoc for the documentation, we need a 
> command help printer that generate asciidoc format.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4242) Add apache artemis to repo-add shorthand list

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4242:


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

KARAF-4242 - Add Apache Artemis features repository


> Add apache artemis to repo-add shorthand list
> -
>
> Key: KARAF-4242
> URL: https://issues.apache.org/jira/browse/KARAF-4242
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.4
>
>
> Today you can add cxf, camel, activemq, etc using
> feature:repo-add camel 2.16.1
> We should add artemis to that list too, so you can do
> feature:repo-add artemis 1.2.0
> Today you have to use
> feature:repo-add mvn:org.apache.activemq/artemis-features/1.2.1-SNAPSHOT/xml



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4258) Cleanup deprecated and unused properties

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4258:


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

KARAF-4258 - Cleanup unused properties


> Cleanup deprecated and unused properties
> 
>
> Key: KARAF-4258
> URL: https://issues.apache.org/jira/browse/KARAF-4258
> Project: Karaf
>  Issue Type: Task
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.5
>
>
> Some cfg files shipped by default contain deprecated and unused properties.
> For instance, etc/org.apache.karaf.features.cfg file contains 
> respectStartLvlDuringFeatureStartup or respectStartLvlDuringFeatureUninstall 
> properties not used anymore.
> I will cleanup those unused properties to avoid to confuse users.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-2971) there is no MBean operation for easily get bundle status

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-2971:


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

KARAF-2971 - Add bundle:status command and getStatus() MBean operation. This 
closes #126


> there is no MBean operation for easily get bundle status
> 
>
> Key: KARAF-2971
> URL: https://issues.apache.org/jira/browse/KARAF-2971
> Project: Karaf
>  Issue Type: Improvement
>Affects Versions: 2.3.3
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> Now if user want to get a specific bundle's status (Active, Resolved, ...), 
> the only MBean operation can be used is list(), but it return TabularData for 
> all of the installed bundles, user has to process the TabularData. 
> Maybe a new operation --- getStatus(bundle name/bundle id) should be provided 
> in the Bundle MBean for user easily get one specific bundle's status.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-2971) there is no MBean operation for easily get bundle status

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-2971:


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

KARAF-2971 - Add bundle:status command and getStatus() MBean operation. This 
closes #126


> there is no MBean operation for easily get bundle status
> 
>
> Key: KARAF-2971
> URL: https://issues.apache.org/jira/browse/KARAF-2971
> Project: Karaf
>  Issue Type: Improvement
>Affects Versions: 2.3.3
>Reporter: Xilai Dai
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> Now if user want to get a specific bundle's status (Active, Resolved, ...), 
> the only MBean operation can be used is list(), but it return TabularData for 
> all of the installed bundles, user has to process the TabularData. 
> Maybe a new operation --- getStatus(bundle name/bundle id) should be provided 
> in the Bundle MBean for user easily get one specific bundle's status.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4263) Require JDK 1.8

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4263:


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

KARAF-4263 - Upgrade to JDK 1.8
KARAF-4264 - Upgrade to json 20150729, This closes #92


> Require JDK 1.8
> ---
>
> Key: KARAF-4263
> URL: https://issues.apache.org/jira/browse/KARAF-4263
> Project: Karaf
>  Issue Type: New Feature
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4190) Upgrade to pax-logging 1.9

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4190:


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

[KARAF-4189] [KARAF-4190] Switch to log4j v2


> Upgrade to pax-logging 1.9
> --
>
> Key: KARAF-4190
> URL: https://issues.apache.org/jira/browse/KARAF-4190
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4264) Upgrade to pax-web 6

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4264:


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

[KARAF-4264] Upgrade to pax-web 6 (snapshot)

> Upgrade to pax-web 6
> 
>
> Key: KARAF-4264
> URL: https://issues.apache.org/jira/browse/KARAF-4264
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-webcontainer
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4255) karaf-maven-plugin does include unused feature conditional dependencies in assembly

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4255:


Commit 84b90910d955dbbf1d4752acb06ee126e341c669 in karaf's branch 
refs/heads/karaf-4.0.x from [~fabianlange]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=84b9091 ]

[KARAF-4255] Only include conditional dependencies in assembly if condition is 
met


> karaf-maven-plugin does include unused feature conditional dependencies in 
> assembly
> ---
>
> Key: KARAF-4255
> URL: https://issues.apache.org/jira/browse/KARAF-4255
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Fabian Lange
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> I am using karaf-maven-plugin to make a custom assembly.
> I do include SCR, but I do not include webconsole.
> When I look into the system folder of my generated assembly, I can see:
> {code}
> target/assembly/system/org/apache/felix/org.apache.felix.webconsole.plugins.ds/2.0.2/org.apache.felix.webconsole.plugins.ds-2.0.2.jar
> {code}
> this correlates to the maven output:
> {code}
> [INFO] Feature scr is defined as a boot feature
> [INFO] == Installing artifact 
> mvn:org.apache.karaf.scr/org.apache.karaf.scr.command/4.0.3
> [INFO] == Installing artifact mvn:org.apache.felix/org.apache.felix.scr/2.0.2
> [INFO] == Installing artifact 
> mvn:org.apache.felix/org.apache.felix.scr.compat/1.0.2
> [INFO] == Installing artifact 
> mvn:org.apache.felix/org.apache.felix.webconsole.plugins.ds/2.0.2
> [INFO] == Installing artifact 
> mvn:org.apache.felix/org.apache.felix.metatype/1.1.2
> [INFO] == Installing artifact 
> mvn:org.apache.karaf.scr/org.apache.karaf.scr.management/4.0.3
> {code}
> however looking at: 
> https://github.com/apache/karaf/blob/master/assemblies/features/standard/src/main/feature/feature.xml#L524
> you can see that this is an conditional dependency only.
> This is caused by the fact that assembly does not check if the conditional 
> had been met:
> https://github.com/apache/karaf/blob/master/profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java#L822
> I believe we need a check for the conditionals wether the condition is 
> actually met.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4255) karaf-maven-plugin does include unused feature conditional dependencies in assembly

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4255:


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

Merge branch 'KARAF-4255' of https://github.com/CodingFabian/karaf


> karaf-maven-plugin does include unused feature conditional dependencies in 
> assembly
> ---
>
> Key: KARAF-4255
> URL: https://issues.apache.org/jira/browse/KARAF-4255
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Fabian Lange
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> I am using karaf-maven-plugin to make a custom assembly.
> I do include SCR, but I do not include webconsole.
> When I look into the system folder of my generated assembly, I can see:
> {code}
> target/assembly/system/org/apache/felix/org.apache.felix.webconsole.plugins.ds/2.0.2/org.apache.felix.webconsole.plugins.ds-2.0.2.jar
> {code}
> this correlates to the maven output:
> {code}
> [INFO] Feature scr is defined as a boot feature
> [INFO] == Installing artifact 
> mvn:org.apache.karaf.scr/org.apache.karaf.scr.command/4.0.3
> [INFO] == Installing artifact mvn:org.apache.felix/org.apache.felix.scr/2.0.2
> [INFO] == Installing artifact 
> mvn:org.apache.felix/org.apache.felix.scr.compat/1.0.2
> [INFO] == Installing artifact 
> mvn:org.apache.felix/org.apache.felix.webconsole.plugins.ds/2.0.2
> [INFO] == Installing artifact 
> mvn:org.apache.felix/org.apache.felix.metatype/1.1.2
> [INFO] == Installing artifact 
> mvn:org.apache.karaf.scr/org.apache.karaf.scr.management/4.0.3
> {code}
> however looking at: 
> https://github.com/apache/karaf/blob/master/assemblies/features/standard/src/main/feature/feature.xml#L524
> you can see that this is an conditional dependency only.
> This is caused by the fact that assembly does not check if the conditional 
> had been met:
> https://github.com/apache/karaf/blob/master/profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java#L822
> I believe we need a check for the conditionals wether the condition is 
> actually met.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4255) karaf-maven-plugin does include unused feature conditional dependencies in assembly

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4255:


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

[KARAF-4255] Only include conditional dependencies in assembly if condition is 
met


> karaf-maven-plugin does include unused feature conditional dependencies in 
> assembly
> ---
>
> Key: KARAF-4255
> URL: https://issues.apache.org/jira/browse/KARAF-4255
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3
>Reporter: Fabian Lange
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.5
>
>
> I am using karaf-maven-plugin to make a custom assembly.
> I do include SCR, but I do not include webconsole.
> When I look into the system folder of my generated assembly, I can see:
> {code}
> target/assembly/system/org/apache/felix/org.apache.felix.webconsole.plugins.ds/2.0.2/org.apache.felix.webconsole.plugins.ds-2.0.2.jar
> {code}
> this correlates to the maven output:
> {code}
> [INFO] Feature scr is defined as a boot feature
> [INFO] == Installing artifact 
> mvn:org.apache.karaf.scr/org.apache.karaf.scr.command/4.0.3
> [INFO] == Installing artifact mvn:org.apache.felix/org.apache.felix.scr/2.0.2
> [INFO] == Installing artifact 
> mvn:org.apache.felix/org.apache.felix.scr.compat/1.0.2
> [INFO] == Installing artifact 
> mvn:org.apache.felix/org.apache.felix.webconsole.plugins.ds/2.0.2
> [INFO] == Installing artifact 
> mvn:org.apache.felix/org.apache.felix.metatype/1.1.2
> [INFO] == Installing artifact 
> mvn:org.apache.karaf.scr/org.apache.karaf.scr.management/4.0.3
> {code}
> however looking at: 
> https://github.com/apache/karaf/blob/master/assemblies/features/standard/src/main/feature/feature.xml#L524
> you can see that this is an conditional dependency only.
> This is caused by the fact that assembly does not check if the conditional 
> had been met:
> https://github.com/apache/karaf/blob/master/profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java#L822
> I believe we need a check for the conditionals wether the condition is 
> actually met.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4566) "karaf" script invokes /bin/sh but requires /bin/bash functions

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4566:


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

[KARAF-4566] bin/karaf script invokes /bin/sh but requires /bin/bash 
functions\n\nThis close #197


>  "karaf" script invokes /bin/sh but requires /bin/bash functions
> 
>
> Key: KARAF-4566
> URL: https://issues.apache.org/jira/browse/KARAF-4566
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 3.0.6
> Environment: Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc)
>Reporter: Alexis de Talhouët
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> The bin/karaf script uses the "local" command which is a shell builtin of 
> bash and similar shells, but is not required for POSIX-compliance in sh. When 
> I attempt to run karaf on a Solaris system, I see the following output:
> root@solaris:/opendaylight/bin# ./karaf
> ./karaf[172]: local: not found [No such file or directory]
> ./karaf[182]: local: not found [No such file or directory]
> ./karaf[183]: local: not found [No such file or directory]
> Lines 172, 182 and 183 invoke "local" to make local variables to the 
> function. According to "man bash", this is a shell builtin. However, 
> bin/karaf is invoked as:
> #!/bin/sh
> On most flavors of linux, this resolves to bash or dash which probably runs 
> in a restricted environment after checking to see that its $0 is sh. But on 
> Solaris's /bin/sh is actually ksh93 for backwards compatibility.
> Since "local" is not part of a POSIX-compliant /bin/sh, depending on it in a 
> script that is invoked with /bin/sh is a bug.
> (this explaination is borrowed from 
> https://issues.apache.org/jira/browse/MNG-5852)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4566) "karaf" script invokes /bin/sh but requires /bin/bash functions

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4566:


Commit 8b087d159476f0f5f04dbb5f09f2792da2b56bf5 in karaf's branch 
refs/heads/karaf-3.0.x from [~adetalhouet]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=8b087d1 ]

KARAF-4566 "karaf" script invokes /bin/sh but requires /bin/bash functions

Signed-off-by: Alexis de Talhouët 


>  "karaf" script invokes /bin/sh but requires /bin/bash functions
> 
>
> Key: KARAF-4566
> URL: https://issues.apache.org/jira/browse/KARAF-4566
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 3.0.6
> Environment: Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc)
>Reporter: Alexis de Talhouët
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> The bin/karaf script uses the "local" command which is a shell builtin of 
> bash and similar shells, but is not required for POSIX-compliance in sh. When 
> I attempt to run karaf on a Solaris system, I see the following output:
> root@solaris:/opendaylight/bin# ./karaf
> ./karaf[172]: local: not found [No such file or directory]
> ./karaf[182]: local: not found [No such file or directory]
> ./karaf[183]: local: not found [No such file or directory]
> Lines 172, 182 and 183 invoke "local" to make local variables to the 
> function. According to "man bash", this is a shell builtin. However, 
> bin/karaf is invoked as:
> #!/bin/sh
> On most flavors of linux, this resolves to bash or dash which probably runs 
> in a restricted environment after checking to see that its $0 is sh. But on 
> Solaris's /bin/sh is actually ksh93 for backwards compatibility.
> Since "local" is not part of a POSIX-compliant /bin/sh, depending on it in a 
> script that is invoked with /bin/sh is a bug.
> (this explaination is borrowed from 
> https://issues.apache.org/jira/browse/MNG-5852)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4566) "karaf" script invokes /bin/sh but requires /bin/bash functions

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4566:


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

[KARAF-4566] Cleanup in script. This closes #197


>  "karaf" script invokes /bin/sh but requires /bin/bash functions
> 
>
> Key: KARAF-4566
> URL: https://issues.apache.org/jira/browse/KARAF-4566
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 3.0.6
> Environment: Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc)
>Reporter: Alexis de Talhouët
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> The bin/karaf script uses the "local" command which is a shell builtin of 
> bash and similar shells, but is not required for POSIX-compliance in sh. When 
> I attempt to run karaf on a Solaris system, I see the following output:
> root@solaris:/opendaylight/bin# ./karaf
> ./karaf[172]: local: not found [No such file or directory]
> ./karaf[182]: local: not found [No such file or directory]
> ./karaf[183]: local: not found [No such file or directory]
> Lines 172, 182 and 183 invoke "local" to make local variables to the 
> function. According to "man bash", this is a shell builtin. However, 
> bin/karaf is invoked as:
> #!/bin/sh
> On most flavors of linux, this resolves to bash or dash which probably runs 
> in a restricted environment after checking to see that its $0 is sh. But on 
> Solaris's /bin/sh is actually ksh93 for backwards compatibility.
> Since "local" is not part of a POSIX-compliant /bin/sh, depending on it in a 
> script that is invoked with /bin/sh is a bug.
> (this explaination is borrowed from 
> https://issues.apache.org/jira/browse/MNG-5852)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4566) "karaf" script invokes /bin/sh but requires /bin/bash functions

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4566:


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

[KARAF-4566] Cleanup in script. This closes #197


>  "karaf" script invokes /bin/sh but requires /bin/bash functions
> 
>
> Key: KARAF-4566
> URL: https://issues.apache.org/jira/browse/KARAF-4566
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 3.0.6
> Environment: Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc)
>Reporter: Alexis de Talhouët
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> The bin/karaf script uses the "local" command which is a shell builtin of 
> bash and similar shells, but is not required for POSIX-compliance in sh. When 
> I attempt to run karaf on a Solaris system, I see the following output:
> root@solaris:/opendaylight/bin# ./karaf
> ./karaf[172]: local: not found [No such file or directory]
> ./karaf[182]: local: not found [No such file or directory]
> ./karaf[183]: local: not found [No such file or directory]
> Lines 172, 182 and 183 invoke "local" to make local variables to the 
> function. According to "man bash", this is a shell builtin. However, 
> bin/karaf is invoked as:
> #!/bin/sh
> On most flavors of linux, this resolves to bash or dash which probably runs 
> in a restricted environment after checking to see that its $0 is sh. But on 
> Solaris's /bin/sh is actually ksh93 for backwards compatibility.
> Since "local" is not part of a POSIX-compliant /bin/sh, depending on it in a 
> script that is invoked with /bin/sh is a bug.
> (this explaination is borrowed from 
> https://issues.apache.org/jira/browse/MNG-5852)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4556) Upgrade to Aries Blueprint CM 1.0.9

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4556:


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

Revert "[KARAF-4556] Upgrade to Aries Blueprint CM 1.0.9"

This reverts commit 7cf848268c0e77f1f7421c2e518f4bdd891d579b.


> Upgrade to Aries Blueprint CM 1.0.9
> ---
>
> Key: KARAF-4556
> URL: https://issues.apache.org/jira/browse/KARAF-4556
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4556) Upgrade to Aries Blueprint CM 1.0.9

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4556:


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

Revert "[KARAF-4556] Upgrade to Aries Blueprint CM 1.0.9"

This reverts commit e9a0c8966d0bb24f58d221919e1fd8aa6be98462.


> Upgrade to Aries Blueprint CM 1.0.9
> ---
>
> Key: KARAF-4556
> URL: https://issues.apache.org/jira/browse/KARAF-4556
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4556) Upgrade to Aries Blueprint CM 1.0.9

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4556:


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

Revert "[KARAF-4556] Upgrade to Aries Blueprint CM 1.0.9"

This reverts commit 243ed0b2391d5df9825bb33f9b2ab8007af6c604.


> Upgrade to Aries Blueprint CM 1.0.9
> ---
>
> Key: KARAF-4556
> URL: https://issues.apache.org/jira/browse/KARAF-4556
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4563) Upgrade Cglib to version 3.2.2

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4563:


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

[KARAF-4563] Upgrade Cglib to version 3.2.2


> Upgrade Cglib to version 3.2.2
> --
>
> Key: KARAF-4563
> URL: https://issues.apache.org/jira/browse/KARAF-4563
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4563) Upgrade Cglib to version 3.2.2

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4563:


Commit 954f7d48479b09ee92af2d927675ed278a3750c0 in karaf's branch 
refs/heads/karaf-4.0.x from [~ancosen]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=954f7d4 ]

[KARAF-4563] Upgrade Cglib to version 3.2.2


> Upgrade Cglib to version 3.2.2
> --
>
> Key: KARAF-4563
> URL: https://issues.apache.org/jira/browse/KARAF-4563
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4516) Extend Karaf feature import version range in Decanter Kibana bundle

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4516:


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

[KARAF-4516] Extend feature service import version range in Kibana 4.x bundle


> Extend Karaf feature import version range in Decanter Kibana bundle
> ---
>
> Key: KARAF-4516
> URL: https://issues.apache.org/jira/browse/KARAF-4516
> Project: Karaf
>  Issue Type: Bug
>  Components: decanter
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: decanter-1.1.1
>
>
> Decanter Kibana bundle implements a FeatureListener to automatically update 
> the Kibana index and dashboards when user installs a collector.
> Unfortunately, the Karaf feature import range is {{[4,)}}, blocking the 
> installation of Decanter Kibana on Karaf 3.x, whereas it works fine with the 
> Karaf 3 feature service.
> I will extend the version range to {{[3,)}} to allow to install Decanter 
> Kibana on Karaf 3 and Karaf 4.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4084) Only one flag could be used in list command

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4084:


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

[KARAF-4084] Support multi-options in bundle:list


> Only one flag could be used in list command
> ---
>
> Key: KARAF-4084
> URL: https://issues.apache.org/jira/browse/KARAF-4084
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 3.0.5, 4.0.2
>Reporter: Sergey 
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> For bundle:list command we have -r to list revisons, -u to list update 
> locations, etc. 
> But why revisions *or* update locations only?
> We can't use -r -u, or even -ru, as it possible for unix-like systems. It 
> should be possible to specify any valid set of flags.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4084) Only one flag could be used in list command

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4084:


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

[KARAF-4084] Support multi-options in bundle:list


> Only one flag could be used in list command
> ---
>
> Key: KARAF-4084
> URL: https://issues.apache.org/jira/browse/KARAF-4084
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Affects Versions: 3.0.5, 4.0.2
>Reporter: Sergey 
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> For bundle:list command we have -r to list revisons, -u to list update 
> locations, etc. 
> But why revisions *or* update locations only?
> We can't use -r -u, or even -ru, as it possible for unix-like systems. It 
> should be possible to specify any valid set of flags.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4556) Upgrade to Aries Blueprint CM 1.0.9

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4556:


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

[KARAF-4556] Upgrade to Aries Blueprint CM 1.0.9


> Upgrade to Aries Blueprint CM 1.0.9
> ---
>
> Key: KARAF-4556
> URL: https://issues.apache.org/jira/browse/KARAF-4556
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4556) Upgrade to Aries Blueprint CM 1.0.9

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4556:


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

[KARAF-4556] Upgrade to Aries Blueprint CM 1.0.9


> Upgrade to Aries Blueprint CM 1.0.9
> ---
>
> Key: KARAF-4556
> URL: https://issues.apache.org/jira/browse/KARAF-4556
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4556) Upgrade to Aries Blueprint CM 1.0.9

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4556:


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

[KARAF-4556] Upgrade to Aries Blueprint CM 1.0.9


> Upgrade to Aries Blueprint CM 1.0.9
> ---
>
> Key: KARAF-4556
> URL: https://issues.apache.org/jira/browse/KARAF-4556
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4555) Update to jline 2.14.2

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4555:


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

[KARAF-4555] Upgrade to jline 2.14.2


> Update to jline 2.14.2
> --
>
> Key: KARAF-4555
> URL: https://issues.apache.org/jira/browse/KARAF-4555
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4546) Support embedding decanter into spring boot apps

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4546:


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

[KARAF-4546] Fix test fail


> Support embedding decanter into spring boot apps
> 
>
> Key: KARAF-4546
> URL: https://issues.apache.org/jira/browse/KARAF-4546
> Project: Karaf
>  Issue Type: New Feature
>  Components: decanter
>Affects Versions: decanter-1.1.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: decanter-1.1.1
>
>
> I just did a POC to use decanter as a distributed logging system for spring 
> boot applications.
> My first approach was to use the log4j socket appender to log into a local 
> (but separate process) decanter-agent that then forwards to kafka.
> A central decanter server would then pick up the logs and store them into ES. 
> The disadvantage was that each node needs a local decanter-agent which makes 
> the packaging for the cloud more difficult.
> So I looked into a way to embed decanter into spring boot and found felix 
> connect. It allows to pick some bundles from the normal classpath and start 
> them in a partial OSGi container.
> It seems to be good enough to nicely host decanter and the kafka appender. I 
> created a custom logback appender class for spring boot that forwards all 
> logs into the embedded decanter instance.
> To make it easy to use I packaged this as a spring boot starter. So people 
> only have to add the dependency and configure their logging to use the new 
> decanter appender.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4557) Add config:property-get and getProperty operation on the ConfigMBean

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4557:


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

[KARAF-4557] Add config:property-get command and getProperty operation on 
ConfigMBean


> Add config:property-get and getProperty operation on the ConfigMBean
> 
>
> Key: KARAF-4557
> URL: https://issues.apache.org/jira/browse/KARAF-4557
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-config, karaf-management
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> For convenience, it would be great to add a {{getProperty}} operation on the 
> {{ConfigMBean}}.
> Same thing in the shell with a {{config:property-get}} command.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4555) Update to jline 2.14.2

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4555:


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

[KARAF-4555] Upgrade to jline 2.14.2


> Update to jline 2.14.2
> --
>
> Key: KARAF-4555
> URL: https://issues.apache.org/jira/browse/KARAF-4555
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4557) Add config:property-get and getProperty operation on the ConfigMBean

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4557:


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

[KARAF-4557] Add config:property-get command and getProperty operation on 
ConfigMBean


> Add config:property-get and getProperty operation on the ConfigMBean
> 
>
> Key: KARAF-4557
> URL: https://issues.apache.org/jira/browse/KARAF-4557
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-config, karaf-management
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> For convenience, it would be great to add a {{getProperty}} operation on the 
> {{ConfigMBean}}.
> Same thing in the shell with a {{config:property-get}} command.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4557) Add config:property-get and getProperty operation on the ConfigMBean

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4557:


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

[KARAF-4557] Add config:property-get command and getProperty operation on 
ConfigMBean


> Add config:property-get and getProperty operation on the ConfigMBean
> 
>
> Key: KARAF-4557
> URL: https://issues.apache.org/jira/browse/KARAF-4557
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-config, karaf-management
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> For convenience, it would be great to add a {{getProperty}} operation on the 
> {{ConfigMBean}}.
> Same thing in the shell with a {{config:property-get}} command.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4564) Can't start karaf using symbolic link

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4564:


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

[KARAF-4564] This closes #196


>  Can't start karaf using symbolic link
> --
>
> Key: KARAF-4564
> URL: https://issues.apache.org/jira/browse/KARAF-4564
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 3.0.6
> Environment: Ubuntu (Linux vagrant 3.19.0-25-generic 
> #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 
> GNU/Linux)
> OSX (Darwin inocybe.local 14.5.0 Darwin Kernel Version 14.5.0: Tue Sep  1 
> 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64)
> Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc)
>Reporter: Alexis de Talhouët
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> When using a symbolic link to use the scripts defined here: 
> https://github.com/apache/karaf/tree/karaf-3.0.6/assemblies/features/framework/src/main/filtered-resources/resources/bin
>  e.g. karaf or client and so on, it's failing to start the container and show 
> this error:
> Error: Could not find or load main class org.apache.karaf.main.Main
> This issue is related to the DIRNAME variable and the way it is setup.
> This bug has been found in OpenDaylight, here is the ticket with more 
> information https://bugs.opendaylight.org/show_bug.cgi?id=6027
> I have also propose a candidate fix in ODL: 
> https://git.opendaylight.org/gerrit/#/c/39982/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4564) Can't start karaf using symbolic link

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4564:


Commit 65f55dca52d66b15ea50b25fb54bed50a3c7fa3e in karaf's branch 
refs/heads/karaf-3.0.x from [~adetalhouet]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=65f55dc ]

[KARAF-4564] Can't start karaf using symbolic link

Signed-off-by: Alexis de Talhouët 


>  Can't start karaf using symbolic link
> --
>
> Key: KARAF-4564
> URL: https://issues.apache.org/jira/browse/KARAF-4564
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 3.0.6
> Environment: Ubuntu (Linux vagrant 3.19.0-25-generic 
> #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 
> GNU/Linux)
> OSX (Darwin inocybe.local 14.5.0 Darwin Kernel Version 14.5.0: Tue Sep  1 
> 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64)
> Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc)
>Reporter: Alexis de Talhouët
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> When using a symbolic link to use the scripts defined here: 
> https://github.com/apache/karaf/tree/karaf-3.0.6/assemblies/features/framework/src/main/filtered-resources/resources/bin
>  e.g. karaf or client and so on, it's failing to start the container and show 
> this error:
> Error: Could not find or load main class org.apache.karaf.main.Main
> This issue is related to the DIRNAME variable and the way it is setup.
> This bug has been found in OpenDaylight, here is the ticket with more 
> information https://bugs.opendaylight.org/show_bug.cgi?id=6027
> I have also propose a candidate fix in ODL: 
> https://git.opendaylight.org/gerrit/#/c/39982/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4564) Can't start karaf using symbolic link

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4564:


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

[KARAF-4564] Use readlink when possible in scripts to deal with symlink. This 
closes #196


>  Can't start karaf using symbolic link
> --
>
> Key: KARAF-4564
> URL: https://issues.apache.org/jira/browse/KARAF-4564
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 3.0.6
> Environment: Ubuntu (Linux vagrant 3.19.0-25-generic 
> #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 
> GNU/Linux)
> OSX (Darwin inocybe.local 14.5.0 Darwin Kernel Version 14.5.0: Tue Sep  1 
> 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64)
> Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc)
>Reporter: Alexis de Talhouët
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> When using a symbolic link to use the scripts defined here: 
> https://github.com/apache/karaf/tree/karaf-3.0.6/assemblies/features/framework/src/main/filtered-resources/resources/bin
>  e.g. karaf or client and so on, it's failing to start the container and show 
> this error:
> Error: Could not find or load main class org.apache.karaf.main.Main
> This issue is related to the DIRNAME variable and the way it is setup.
> This bug has been found in OpenDaylight, here is the ticket with more 
> information https://bugs.opendaylight.org/show_bug.cgi?id=6027
> I have also propose a candidate fix in ODL: 
> https://git.opendaylight.org/gerrit/#/c/39982/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4564) Can't start karaf using symbolic link

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4564:


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

[KARAF-4564] Use readlink when possible in scripts to deal with symlink. This 
closes #196


>  Can't start karaf using symbolic link
> --
>
> Key: KARAF-4564
> URL: https://issues.apache.org/jira/browse/KARAF-4564
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 3.0.6
> Environment: Ubuntu (Linux vagrant 3.19.0-25-generic 
> #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015 x86_64 x86_64 x86_64 
> GNU/Linux)
> OSX (Darwin inocybe.local 14.5.0 Darwin Kernel Version 14.5.0: Tue Sep  1 
> 21:23:09 PDT 2015; root:xnu-2782.50.1~1/RELEASE_X86_64 x86_64)
> Solaris (SunOS solaris11.3 5.11 11.3 i86pc i386 i86pc)
>Reporter: Alexis de Talhouët
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> When using a symbolic link to use the scripts defined here: 
> https://github.com/apache/karaf/tree/karaf-3.0.6/assemblies/features/framework/src/main/filtered-resources/resources/bin
>  e.g. karaf or client and so on, it's failing to start the container and show 
> this error:
> Error: Could not find or load main class org.apache.karaf.main.Main
> This issue is related to the DIRNAME variable and the way it is setup.
> This bug has been found in OpenDaylight, here is the ticket with more 
> information https://bugs.opendaylight.org/show_bug.cgi?id=6027
> I have also propose a candidate fix in ODL: 
> https://git.opendaylight.org/gerrit/#/c/39982/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4502) REGRESSION: using OpenJDK on CentOS 7 causes bin/client to fail with "Unable to negotiate key exchange for kex algorithms"

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4502:


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

[KARAF-4062][KARAF-4502] Check elliptic curves using SecurityUtils.hasEcc() and 
compute the maximum length for DHGEX factories

> REGRESSION: using OpenJDK on CentOS 7 causes bin/client to fail with "Unable 
> to negotiate key exchange for kex algorithms"
> --
>
> Key: KARAF-4502
> URL: https://issues.apache.org/jira/browse/KARAF-4502
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.3, 3.0.6, 4.0.4
> Environment: CentOS Linux release 7.0.1406 (Core) 
> openjdk version "1.8.0_77"
>Reporter: Damjan Jovanovic
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.7, 4.0.6
>
>
> On a fresh install of CentOS 7 with OpenJDK 1.8, running karaf container 
> versions > 4.0.2 either with "bin/karaf" or as a service (whether sysvinit or 
> systemd), trying to log in with "bin/client" always fails with an exception.
> Oracle JDK - by comparison - works.
> "git bisect" narrowed down the regression to the following commit:
> 539540cde099aee52fd523a09aca92e36522261c is the first bad commit
> commit 539540cde099aee52fd523a09aca92e36522261c
> Author: Freeman Fang 
> Date:   Wed Oct 14 12:09:09 2015 +0800
> [KARAF-4062]Karaf client does now work after installing BouncyCastle
> :04 04 926f15997510a671ff77db9623f8b65ce4186706 
> da83c22e043de3004a620f1cc88e25ee672bd09d Mclient
> The exception is:
> # bin/client
> Logging in as karaf
> 3771 [sshd-SshClient[593634ad]-nio2-thread-2] WARN 
> org.apache.sshd.client.session.ClientSessionImpl - Exception caught
> java.lang.IllegalStateException: Unable to negotiate key exchange for kex 
> algorithms (client: 
> ecdh-sha2-nistp256,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp384,ecdh-sha2-nistp521,ecdh-sha2-nistp521
>  / server: 
> diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1)
>   at 
> org.apache.sshd.common.session.AbstractSession.negotiate(AbstractSession.java:1159)
>   at 
> org.apache.sshd.common.session.AbstractSession.doHandleMessage(AbstractSession.java:388)
>   at 
> org.apache.sshd.common.session.AbstractSession.handleMessage(AbstractSession.java:326)
>   at 
> org.apache.sshd.client.session.ClientSessionImpl.handleMessage(ClientSessionImpl.java:306)
>   at 
> org.apache.sshd.common.session.AbstractSession.decode(AbstractSession.java:780)
>   at 
> org.apache.sshd.common.session.AbstractSession.messageReceived(AbstractSession.java:308)
>   at 
> org.apache.sshd.common.AbstractSessionIoHandler.messageReceived(AbstractSessionIoHandler.java:54)
>   at 
> org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:184)
>   at 
> org.apache.sshd.common.io.nio2.Nio2Session$1.onCompleted(Nio2Session.java:170)
>   at 
> org.apache.sshd.common.io.nio2.Nio2CompletionHandler$1.run(Nio2CompletionHandler.java:32)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at 
> org.apache.sshd.common.io.nio2.Nio2CompletionHandler.completed(Nio2CompletionHandler.java:30)
>   at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
>   at sun.nio.ch.Invoker$2.run(Invoker.java:218)
>   at 
> sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Authentication failed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4062) Karaf client does now work after installing BouncyCastle

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4062:


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

[KARAF-4062][KARAF-4502] Check elliptic curves using SecurityUtils.hasEcc() and 
compute the maximum length for DHGEX factories

> Karaf client does now work after installing BouncyCastle
> 
>
> Key: KARAF-4062
> URL: https://issues.apache.org/jira/browse/KARAF-4062
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.2
> Environment: OS X, Windows
>Reporter: Pavlo Vasylchenko
>Assignee: Freeman Fang
> Fix For: 2.4.4, 4.0.3, 3.0.6
>
>
> Karaf client throws:
> " Exception caught
> java.security.InvalidAlgorithmParameterException: Prime size must be multiple 
> of 64, and can only ra
> nge from 512 to 2048 (inclusive)
> at 
> com.sun.crypto.provider.DHKeyPairGenerator.initialize(DHKeyPairGenerator.java:120)"
> after installing mvn:org.bouncycastle/bcprov-jdk15on/1.52 into container



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4553) Allow karaf boot starters to define maven plugins to call

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4553:


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

[KARAF-4553] Allow karaf boot starters to define maven plugins to call


> Allow karaf boot starters to define maven plugins to call
> -
>
> Key: KARAF-4553
> URL: https://issues.apache.org/jira/browse/KARAF-4553
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-boot
>Reporter: Christian Schneider
>Assignee: Christian Schneider
>
> Karaf boot starters are added to user projects as simple depdendencies.
> This normally does not allow the starters to define additional plugins to 
> call.
> One example where we need this is the blueprint starter. It needs to call the 
> blueprint-maven-plugin. 
> The idea is to define a special file karaf-boot/plugins.xml that the starter 
> can use to define which maven plugins to call. The karaf boot maven plugin 
> will evalutate this and call the plugins.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4546) Support embedding decanter into spring boot apps

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4546:


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

[KARAF-4546] initial Spring boot support


> Support embedding decanter into spring boot apps
> 
>
> Key: KARAF-4546
> URL: https://issues.apache.org/jira/browse/KARAF-4546
> Project: Karaf
>  Issue Type: New Feature
>  Components: decanter
>Affects Versions: decanter-1.1.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: decanter-1.1.1
>
>
> I just did a POC to use decanter as a distributed logging system for spring 
> boot applications.
> My first approach was to use the log4j socket appender to log into a local 
> (but separate process) decanter-agent that then forwards to kafka.
> A central decanter server would then pick up the logs and store them into ES. 
> The disadvantage was that each node needs a local decanter-agent which makes 
> the packaging for the cloud more difficult.
> So I looked into a way to embed decanter into spring boot and found felix 
> connect. It allows to pick some bundles from the normal classpath and start 
> them in a partial OSGi container.
> It seems to be good enough to nicely host decanter and the kafka appender. I 
> created a custom logback appender class for spring boot that forwards all 
> logs into the embedded decanter instance.
> To make it easy to use I packaged this as a spring boot starter. So people 
> only have to add the dependency and configure their logging to use the new 
> decanter appender.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4546) Support embedding decanter into spring boot apps

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4546:


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

[KARAF-4546] Adding snapshot repo


> Support embedding decanter into spring boot apps
> 
>
> Key: KARAF-4546
> URL: https://issues.apache.org/jira/browse/KARAF-4546
> Project: Karaf
>  Issue Type: New Feature
>  Components: decanter
>Affects Versions: decanter-1.1.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: decanter-1.1.1
>
>
> I just did a POC to use decanter as a distributed logging system for spring 
> boot applications.
> My first approach was to use the log4j socket appender to log into a local 
> (but separate process) decanter-agent that then forwards to kafka.
> A central decanter server would then pick up the logs and store them into ES. 
> The disadvantage was that each node needs a local decanter-agent which makes 
> the packaging for the cloud more difficult.
> So I looked into a way to embed decanter into spring boot and found felix 
> connect. It allows to pick some bundles from the normal classpath and start 
> them in a partial OSGi container.
> It seems to be good enough to nicely host decanter and the kafka appender. I 
> created a custom logback appender class for spring boot that forwards all 
> logs into the embedded decanter instance.
> To make it easy to use I packaged this as a spring boot starter. So people 
> only have to add the dependency and configure their logging to use the new 
> decanter appender.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4548) Avoid extensive spifly logging

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4548:


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

[KARAF-4548] Log spifly only at WARN level


> Avoid extensive spifly logging
> --
>
> Key: KARAF-4548
> URL: https://issues.apache.org/jira/browse/KARAF-4548
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-core
>Affects Versions: 4.0.5
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.0.6
>
>
> Spifly logs each bundle it ignores at info level. So we should configure it 
> to only log at WARN level



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4546) Support embedding decanter into spring boot apps

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4546:


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

[KARAF-4546] Allow configs for decanter in spring


> Support embedding decanter into spring boot apps
> 
>
> Key: KARAF-4546
> URL: https://issues.apache.org/jira/browse/KARAF-4546
> Project: Karaf
>  Issue Type: New Feature
>  Components: decanter
>Affects Versions: decanter-1.1.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: decanter-1.1.1
>
>
> I just did a POC to use decanter as a distributed logging system for spring 
> boot applications.
> My first approach was to use the log4j socket appender to log into a local 
> (but separate process) decanter-agent that then forwards to kafka.
> A central decanter server would then pick up the logs and store them into ES. 
> The disadvantage was that each node needs a local decanter-agent which makes 
> the packaging for the cloud more difficult.
> So I looked into a way to embed decanter into spring boot and found felix 
> connect. It allows to pick some bundles from the normal classpath and start 
> them in a partial OSGi container.
> It seems to be good enough to nicely host decanter and the kafka appender. I 
> created a custom logback appender class for spring boot that forwards all 
> logs into the embedded decanter instance.
> To make it easy to use I packaged this as a spring boot starter. So people 
> only have to add the dependency and configure their logging to use the new 
> decanter appender.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4574) EventAdmin not injected in file collector

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4574:


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

[KARAF-4574] Only start if config is present


> EventAdmin not injected in file collector
> -
>
> Key: KARAF-4574
> URL: https://issues.apache.org/jira/browse/KARAF-4574
> Project: Karaf
>  Issue Type: Bug
>  Components: decanter
>Affects Versions: decanter-1.1.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: decanter-1.1.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4588) Features service lost install options

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4588:


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

[KARAF-4588] Pass along options


> Features service lost install options
> -
>
> Key: KARAF-4588
> URL: https://issues.apache.org/jira/browse/KARAF-4588
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.5
>Reporter: Alexey Markevich
> Attachments: pass-options-argument-during-feature-install.patch
>
>
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeature(Feature,
>  EnumSet) doesn't pass options



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4588) Features service lost install options

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4588:


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

[KARAF-4588] Pass along options


> Features service lost install options
> -
>
> Key: KARAF-4588
> URL: https://issues.apache.org/jira/browse/KARAF-4588
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.5
>Reporter: Alexey Markevich
> Attachments: pass-options-argument-during-feature-install.patch
>
>
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeature(Feature,
>  EnumSet) doesn't pass options



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4576) Upgrade to Narayana 5.3.3.Final

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4576:


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

[KARAF-4576] Upgrade to Narayana 5.3.3.Final


> Upgrade to Narayana 5.3.3.Final
> ---
>
> Key: KARAF-4576
> URL: https://issues.apache.org/jira/browse/KARAF-4576
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4574) EventAdmin not injected in file collector

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4574:


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

[KARAF-4574] Only start if config is present


> EventAdmin not injected in file collector
> -
>
> Key: KARAF-4574
> URL: https://issues.apache.org/jira/browse/KARAF-4574
> Project: Karaf
>  Issue Type: Bug
>  Components: decanter
>Affects Versions: decanter-1.1.0
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: decanter-1.1.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4577) Use ServiceComponentRuntime api and provide a BundleStateService for DS

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4577:


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

[KARAF-4577] Use ServiceComponentRuntime api and provide a BundleStateService 
for DS

> Use ServiceComponentRuntime api and provide a BundleStateService for DS
> ---
>
> Key: KARAF-4577
> URL: https://issues.apache.org/jira/browse/KARAF-4577
> Project: Karaf
>  Issue Type: Improvement
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4584) Update Exec Maven Plugin to version 1.5.0

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4584:


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

[KARAF-4584] Update Exec Maven Plugin to version 1.5.0


> Update Exec Maven Plugin to version 1.5.0
> -
>
> Key: KARAF-4584
> URL: https://issues.apache.org/jira/browse/KARAF-4584
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4547) Embed resolver in features.core to avoid errors in bundle resolution when installing CXF as boot feature

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4547:


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

[KARAF-4547] Defer setting startlevel to after bundles are installed


> Embed resolver in features.core to avoid errors in bundle resolution when 
> installing CXF as boot feature
> 
>
> Key: KARAF-4547
> URL: https://issues.apache.org/jira/browse/KARAF-4547
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.5
> Environment: Framework switched to Equinox
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.1.0, 4.0.6
>
>
> To reproduce:
> - download and unpack karaf 4.0.5
> - Add CXF 3.1.5 to the boot features like below
> - Switch framework to equinox
> Start karaf using bin/karaf
> 2016-06-02 11:59:05,644 | ERROR | 0bd-8aec27f84fc4 | cxf-core 
> | 67 - org.apache.cxf.cxf-core - 3.1.5 | FrameworkEvent ERROR - 
> org.apache.cxf.cxf-core
> org.osgi.framework.BundleException: Could not resolve module: 
> org.apache.cxf.cxf-core [67]
> ...
>   Unresolved requirement: Import-Package: org.apache.ws.commons.schema; 
> version="[2.2.0,3.0.0)"
>   Unresolved requirement: Import-Package: javax.annotation; 
> version="[0.0.0,2.0.0)"
> See this for the full log:
> http://apaste.info/QD8
> If the error does not occur stop karaf, delete data dir and start karaf again 
> some times.
> This bug was originally reported by our Talend ESB team. I have attached the 
> link to the issue.
> The issue seems to happen on windows and linux but only on equinox. On felix 
> it works fine.
> I assume that this might be releated to the felix resolver. Equinox contains 
> an older version of the resolver.
> 
> featuresRepositories = \
> mvn:org.apache.karaf.features/spring/4.0.5/xml/features, \
> mvn:org.apache.karaf.features/standard/4.0.5/xml/features, \
> mvn:org.apache.karaf.features/framework/4.0.5/xml/features, \
> mvn:org.apache.karaf.features/enterprise/4.0.5/xml/features, \
> mvn:org.apache.cxf.karaf/apache-cxf/3.1.5/xml/features
> featuresBoot = \
> (instance, \
> package, \
> log, \
> ssh, \
> aries-blueprint, \
> framework, \
> system, \
> feature, \
> shell, \
> management, \
> service, \
> jaas, \
> shell-compat, \
> deployer, \
> diagnostic, \
> wrap, \
> bundle, \
> config, \
> kar), \
>   spring-dm, \
> cxf-abdera, \
> cxf, \
> cxf-commands



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4583) Upgrade to equinox 3.10.101.v20150820-1432

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4583:


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

[KARAF-4583] Update to equinox 3.10.101.v20150820-1432


> Upgrade to equinox 3.10.101.v20150820-1432
> --
>
> Key: KARAF-4583
> URL: https://issues.apache.org/jira/browse/KARAF-4583
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.1.0, 4.0.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4569) OSGi framework is not shut-down gracefully on SIGTERM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4569:


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

KARAF-4569: OSGi framework is not shut-down gracefully on SIGTERM


> OSGi framework is not shut-down gracefully on SIGTERM
> -
>
> Key: KARAF-4569
> URL: https://issues.apache.org/jira/browse/KARAF-4569
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-core
>Reporter: Luca Burgazzoli
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> When Karaf receive a signal like SIGTERM, the OSGi framework is not 
> terminated properly but the JVM simply exits.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4569) OSGi framework is not shut-down gracefully on SIGTERM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4569:


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

Merge branch 'KARAF-4569' of https://github.com/lburgazzoli/karaf


> OSGi framework is not shut-down gracefully on SIGTERM
> -
>
> Key: KARAF-4569
> URL: https://issues.apache.org/jira/browse/KARAF-4569
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-core
>Reporter: Luca Burgazzoli
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> When Karaf receive a signal like SIGTERM, the OSGi framework is not 
> terminated properly but the JVM simply exits.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4583) Upgrade to equinox 3.10.101.v20150820-1432

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4583:


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

[KARAF-4583] Update to equinox 3.10.101.v20150820-1432


> Upgrade to equinox 3.10.101.v20150820-1432
> --
>
> Key: KARAF-4583
> URL: https://issues.apache.org/jira/browse/KARAF-4583
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.1.0, 4.0.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4547) Embed resolver in features.core to avoid errors in bundle resolution when installing CXF as boot feature

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4547:


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

[KARAF-4547] Defer setting startlevel to after bundles are installed


> Embed resolver in features.core to avoid errors in bundle resolution when 
> installing CXF as boot feature
> 
>
> Key: KARAF-4547
> URL: https://issues.apache.org/jira/browse/KARAF-4547
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.5
> Environment: Framework switched to Equinox
>Reporter: Christian Schneider
>Assignee: Christian Schneider
> Fix For: 4.1.0, 4.0.6
>
>
> To reproduce:
> - download and unpack karaf 4.0.5
> - Add CXF 3.1.5 to the boot features like below
> - Switch framework to equinox
> Start karaf using bin/karaf
> 2016-06-02 11:59:05,644 | ERROR | 0bd-8aec27f84fc4 | cxf-core 
> | 67 - org.apache.cxf.cxf-core - 3.1.5 | FrameworkEvent ERROR - 
> org.apache.cxf.cxf-core
> org.osgi.framework.BundleException: Could not resolve module: 
> org.apache.cxf.cxf-core [67]
> ...
>   Unresolved requirement: Import-Package: org.apache.ws.commons.schema; 
> version="[2.2.0,3.0.0)"
>   Unresolved requirement: Import-Package: javax.annotation; 
> version="[0.0.0,2.0.0)"
> See this for the full log:
> http://apaste.info/QD8
> If the error does not occur stop karaf, delete data dir and start karaf again 
> some times.
> This bug was originally reported by our Talend ESB team. I have attached the 
> link to the issue.
> The issue seems to happen on windows and linux but only on equinox. On felix 
> it works fine.
> I assume that this might be releated to the felix resolver. Equinox contains 
> an older version of the resolver.
> 
> featuresRepositories = \
> mvn:org.apache.karaf.features/spring/4.0.5/xml/features, \
> mvn:org.apache.karaf.features/standard/4.0.5/xml/features, \
> mvn:org.apache.karaf.features/framework/4.0.5/xml/features, \
> mvn:org.apache.karaf.features/enterprise/4.0.5/xml/features, \
> mvn:org.apache.cxf.karaf/apache-cxf/3.1.5/xml/features
> featuresBoot = \
> (instance, \
> package, \
> log, \
> ssh, \
> aries-blueprint, \
> framework, \
> system, \
> feature, \
> shell, \
> management, \
> service, \
> jaas, \
> shell-compat, \
> deployer, \
> diagnostic, \
> wrap, \
> bundle, \
> config, \
> kar), \
>   spring-dm, \
> cxf-abdera, \
> cxf, \
> cxf-commands



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4584) Update Exec Maven Plugin to version 1.5.0

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4584:


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

[KARAF-4584] Update Exec Maven Plugin to version 1.5.0


> Update Exec Maven Plugin to version 1.5.0
> -
>
> Key: KARAF-4584
> URL: https://issues.apache.org/jira/browse/KARAF-4584
> Project: Karaf
>  Issue Type: Dependency upgrade
>  Components: karaf-core
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.1.0, 4.0.6
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4569) OSGi framework is not shut-down gracefully on SIGTERM

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4569:


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

[KARAF-4569] OSGi framework is not shut-down gracefully on SIGTERM


> OSGi framework is not shut-down gracefully on SIGTERM
> -
>
> Key: KARAF-4569
> URL: https://issues.apache.org/jira/browse/KARAF-4569
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-core
>Reporter: Luca Burgazzoli
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> When Karaf receive a signal like SIGTERM, the OSGi framework is not 
> terminated properly but the JVM simply exits.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4575) Re-add "install all" and "uninstall all" features repository options

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4575:


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

[KARAF-4575] Re-add support of install and uninstall mode for feature repo-add 
and repo-remove


> Re-add "install all" and "uninstall all" features repository options
> 
>
> Key: KARAF-4575
> URL: https://issues.apache.org/jira/browse/KARAF-4575
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> On Karaf 2.x and 3.x, it was possible to install all features contained in a 
> features repository using {{-i}} option on {{feature:repo-add}} command (the 
> same for uninstall with {{-u}} option on {{feature:repo-remove}}).
> These options have been removed on Karaf 4.x (throwing 
> {{UnsupportedOperationException}}.
> I will re-add support of these options.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4575) Re-add "install all" and "uninstall all" features repository options

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4575:


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

[KARAF-4575] Re-add support of install and uninstall mode for feature repo-add 
and repo-remove


> Re-add "install all" and "uninstall all" features repository options
> 
>
> Key: KARAF-4575
> URL: https://issues.apache.org/jira/browse/KARAF-4575
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> On Karaf 2.x and 3.x, it was possible to install all features contained in a 
> features repository using {{-i}} option on {{feature:repo-add}} command (the 
> same for uninstall with {{-u}} option on {{feature:repo-remove}}).
> These options have been removed on Karaf 4.x (throwing 
> {{UnsupportedOperationException}}.
> I will re-add support of these options.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4571) karaf-maven-plugin should respect version ranges when generating features repos

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4571:


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

[KARAF-4571] This closes #200


> karaf-maven-plugin should respect version ranges when generating features 
> repos
> ---
>
> Key: KARAF-4571
> URL: https://issues.apache.org/jira/browse/KARAF-4571
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-tooling
>Affects Versions: 4.0.5
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> When for the dependencies of a feature project version ranges are used, then 
> the produced feature.xml 
> references the highest available version of a bundle. This is not always the 
> desired behavior. Instead of that, 
> it should be configurable if the latest base version of a dependency or the 
> version range itself should be written 
> to the feature file (when a dependency is declared with a version range). I 
> would suggest a new plugin configuration 
> property "useVersionRange". Suppose a dependency to commons-lang3:
> {code:title=pom.xml}
> 
>   
>   org.apache.commons
>   commons-lang3
>   [3.0,3.4)
>   
> 
> 
> 
> 
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.1.0-SNAPSHOT
> true
> 
> 
> 
> {code}
> If "useVersionRange" is set to "false" (default), then nothing changes, so 
> the resulting feature.xml would look like this:
> {code:title=feature.xml}
> http://karaf.apache.org/xmlns/features/v1.4.0; 
> name="test-feature-use-base-version">
>  description="test-feature-use-base-version" version="1.0.0.SNAPSHOT">
> mvn:org.apache.commons/commons-lang3/3.4
> 
> 
> {code}
> If "useVersionRange" is set to "true", instead of the base version the 
> declared version range will be used in the bundle element:
> {code:title=pom.xml}
> 
> 
> 
> org.apache.karaf.tooling
> karaf-maven-plugin
> @pom.version@
> true
> 
>   true
> 
> 
> 
> 
> {code}
> {code:title=feature.xml}
> http://karaf.apache.org/xmlns/features/v1.4.0; 
> name="test-feature-use-version-range">
>  description="test-feature-use-version-range" version="1.0.0.SNAPSHOT">
> mvn:org.apache.commons/commons-lang3/[3.0,3.4)
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4571) karaf-maven-plugin should respect version ranges when generating features repos

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4571:


Commit f69e9b8f55a6447659a7c3bbef2d609af84631b9 in karaf's branch 
refs/heads/master from [~roland.hau...@bechtle.ch]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=f69e9b8 ]

[KARAF-4571] Use version range in feature.xml if useVersionRange is true


> karaf-maven-plugin should respect version ranges when generating features 
> repos
> ---
>
> Key: KARAF-4571
> URL: https://issues.apache.org/jira/browse/KARAF-4571
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-tooling
>Affects Versions: 4.0.5
>Reporter: Roland Hauser
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> When for the dependencies of a feature project version ranges are used, then 
> the produced feature.xml 
> references the highest available version of a bundle. This is not always the 
> desired behavior. Instead of that, 
> it should be configurable if the latest base version of a dependency or the 
> version range itself should be written 
> to the feature file (when a dependency is declared with a version range). I 
> would suggest a new plugin configuration 
> property "useVersionRange". Suppose a dependency to commons-lang3:
> {code:title=pom.xml}
> 
>   
>   org.apache.commons
>   commons-lang3
>   [3.0,3.4)
>   
> 
> 
> 
> 
> org.apache.karaf.tooling
> karaf-maven-plugin
> 4.1.0-SNAPSHOT
> true
> 
> 
> 
> {code}
> If "useVersionRange" is set to "false" (default), then nothing changes, so 
> the resulting feature.xml would look like this:
> {code:title=feature.xml}
> http://karaf.apache.org/xmlns/features/v1.4.0; 
> name="test-feature-use-base-version">
>  description="test-feature-use-base-version" version="1.0.0.SNAPSHOT">
> mvn:org.apache.commons/commons-lang3/3.4
> 
> 
> {code}
> If "useVersionRange" is set to "true", instead of the base version the 
> declared version range will be used in the bundle element:
> {code:title=pom.xml}
> 
> 
> 
> org.apache.karaf.tooling
> karaf-maven-plugin
> @pom.version@
> true
> 
>   true
> 
> 
> 
> 
> {code}
> {code:title=feature.xml}
> http://karaf.apache.org/xmlns/features/v1.4.0; 
> name="test-feature-use-version-range">
>  description="test-feature-use-version-range" version="1.0.0.SNAPSHOT">
> mvn:org.apache.commons/commons-lang3/[3.0,3.4)
> 
> 
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4236) Cellar DNS nodes discovery

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4236:


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

[KARAF-4236] Cellar DNS nodes discovery


> Cellar DNS nodes discovery
> --
>
> Key: KARAF-4236
> URL: https://issues.apache.org/jira/browse/KARAF-4236
> Project: Karaf
>  Issue Type: New Feature
>  Components: cellar-cloud
>Reporter: Luca Burgazzoli
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: cellar-4.0.1
>
>
> Cellar currently provides nodes discovery via Kubernetes, it would be nice to 
> support also other types like DNS.
> I will provide a PR



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (KARAF-4590) Document environment variable reference from configuration files

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4590:


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

[KARAF-4590] Document environment variable reference from configuration files


> Document environment variable reference from configuration files
> 
>
> Key: KARAF-4590
> URL: https://issues.apache.org/jira/browse/KARAF-4590
> Project: Karaf
>  Issue Type: Documentation
>  Components: karaf-documentation
>Affects Versions: 4.0.5
>Reporter: Ion Savin
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6
>
>
> Document the functionality discussed in KARAF-2466 and KARAF-3434



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)