[jira] [Assigned] (KARAF-5466) Karaf does not start on JDK 9.0.1
[ https://issues.apache.org/jira/browse/KARAF-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned KARAF-5466: --- Assignee: Freeman Fang (was: Jean-Baptiste Onofré) > Karaf does not start on JDK 9.0.1 > - > > Key: KARAF-5466 > URL: https://issues.apache.org/jira/browse/KARAF-5466 > Project: Karaf > Issue Type: Bug > Components: karaf-boot >Affects Versions: 4.1.3 > Environment: macOS 10.13, JDK 9.0.1 >Reporter: Roland Hauser >Assignee: Freeman Fang > > Karaf does not start on the newest JDK version (9.0.1) with following message: > "karaf: JVM must be greater than 1.8" > It seems that function *checkJvmVersion()* in *bin/inc* does not work > properly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-5466) Karaf does not start on JDK 9.0.1
[ https://issues.apache.org/jira/browse/KARAF-5466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved KARAF-5466. - Resolution: Fixed Fix Version/s: 4.2.0 > Karaf does not start on JDK 9.0.1 > - > > Key: KARAF-5466 > URL: https://issues.apache.org/jira/browse/KARAF-5466 > Project: Karaf > Issue Type: Bug > Components: karaf-boot >Affects Versions: 4.1.3 > Environment: macOS 10.13, JDK 9.0.1 >Reporter: Roland Hauser >Assignee: Freeman Fang > Fix For: 4.2.0 > > > Karaf does not start on the newest JDK version (9.0.1) with following message: > "karaf: JVM must be greater than 1.8" > It seems that function *checkJvmVersion()* in *bin/inc* does not work > properly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5467) Karaf doesn't recognize Java 9 on Ubuntu 16.04
[ https://issues.apache.org/jira/browse/KARAF-5467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16243524#comment-16243524 ] ASF subversion and git services commented on KARAF-5467: Commit 94cd1e0b096fc4b1c6972107ef7c8f15df4afa74 in karaf's branch refs/heads/master from [~ffang] [ https://gitbox.apache.org/repos/asf?p=karaf.git;h=94cd1e0 ] [KARAF-5467]more fix > Karaf doesn't recognize Java 9 on Ubuntu 16.04 > -- > > Key: KARAF-5467 > URL: https://issues.apache.org/jira/browse/KARAF-5467 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.0.M1 > Environment: Ubuntu 16.04 > Java SE 9.0.1+11 >Reporter: David Otasek >Assignee: Freeman Fang > Fix For: 4.2.0 > > > $JAVA_HOME is correctly set to Java 9, and running karaf returns: > karaf: JVM must be greater than 1.8 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KARAF-2792) shared cm-properties empty for second bundle
[
https://issues.apache.org/jira/browse/KARAF-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek reassigned KARAF-2792:
---
Assignee: Grzegorz Grzybek (was: Jean-Baptiste Onofré)
> shared cm-properties empty for second bundle
>
>
> Key: KARAF-2792
> URL: https://issues.apache.org/jira/browse/KARAF-2792
> Project: Karaf
> Issue Type: Bug
> Components: karaf-osgi
>Affects Versions: 2.3.3, 2.3.4
>Reporter: Alexey Markevich
>Assignee: Grzegorz Grzybek
> Attachments: cm-properties.zip, config.cfg
>
>
> - add to etc/custom.properties
> karaf.framework=equinox
> - put config.cfg to etc/
> - build cm-properties and put add-features-to-repo-0.1.kar to deploy/
> Output:
> Bundle1:{service.pid=config, hello=world,
> felix.fileinstall.filename=file:/D:/apache-karaf-2.3.3/etc/config.cfg}
> Bundle2:{}
> Note: sometimes multiple redeploy required
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (KARAF-5323) Set multi-location for created configurations
[
https://issues.apache.org/jira/browse/KARAF-5323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek reassigned KARAF-5323:
---
Assignee: Grzegorz Grzybek
> Set multi-location for created configurations
> -
>
> Key: KARAF-5323
> URL: https://issues.apache.org/jira/browse/KARAF-5323
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-config
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>
> By default, when fileinstall creates CM configurations, they have no
> locations set. According to spec:
> {quote}
> 104.4.2 Dynamic Binding:
> A null location parameter can be used to create Configuration objects that
> are not yet bound.
> In this case, the Configuration becomes bound to a specific location the
> first time that it is
> compared to a Bundle’s location.
> It is recommended that management agents explicitly set the location to a ?
> (a multi-location)
> to allow multiple bundles to share PIDs and not use the dynamic binding
> facility.
> {quote}
> I'd prefer "principle of least surprise", so CM configs created from
> {{etc/*.cfg}} files have multi-location is set by default (alternatively - we
> could have configuration option), so if for example there are two blueprint
> bundles using {{}} for same PID, they can use the
> configuration without problems
> See FELIX-5684
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KARAF-5469) Installation of a non blueprint feature triggers the installation of the blueprint compatibility bundle
Joao Assuncao created KARAF-5469:
Summary: Installation of a non blueprint feature triggers the
installation of the blueprint compatibility bundle
Key: KARAF-5469
URL: https://issues.apache.org/jira/browse/KARAF-5469
Project: Karaf
Issue Type: Bug
Components: karaf-core
Affects Versions: 4.1.3
Reporter: Joao Assuncao
In Karaf 4.1.3 when installing some custom made features karaf triggers the
installation of the org.apache.aries.blueprint.core.compatibility bundle
causing a refresh of all bundles and a Karaf shutdown.
None of the bundles in the feature uses blueprint and the more exotic thing is
that one of the bundles uses a Contional-Package instruction.
The feature I'm trying to install:
{{
karaf@root()> feature:info paybox-io-modbus
Feature paybox-io-modbus 0.1.0.SNAPSHOT
Description:
Modbus I/O implementation
Feature has no configuration
Feature has no configuration files
Feature has no dependencies.
Feature contains followed bundles:
mvn:pt.brisa.common/common-service-core/1.3.0
mvn:pt.brisa.paybox/io-api/0.1.0-SNAPSHOT
mvn:pt.brisa.paybox/io-modbus/0.1.0-SNAPSHOT
mvn:pt.brisa.paybox/io-commands/0.1.0-SNAPSHOT
Feature has no conditionals.}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5470) Karaf fails build with Java 9.0.1
[ https://issues.apache.org/jira/browse/KARAF-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16244635#comment-16244635 ] Jean-Baptiste Onofré commented on KARAF-5470: - Thanks. I'm extending the enforcer rule. > Karaf fails build with Java 9.0.1 > - > > Key: KARAF-5470 > URL: https://issues.apache.org/jira/browse/KARAF-5470 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.0.M1 >Reporter: David Otasek > > When attempting to build Karaf with Java build 9.0.1+11, it fails with the > following warning: > [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVersion failed > with message: > Detected JDK Version: 9.0.1 is not in the allowed range [1.8,9]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KARAF-5470) Karaf fails build with Java 9.0.1
[ https://issues.apache.org/jira/browse/KARAF-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-5470: --- Assignee: Jean-Baptiste Onofré > Karaf fails build with Java 9.0.1 > - > > Key: KARAF-5470 > URL: https://issues.apache.org/jira/browse/KARAF-5470 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.2.0.M1 >Reporter: David Otasek >Assignee: Jean-Baptiste Onofré > > When attempting to build Karaf with Java build 9.0.1+11, it fails with the > following warning: > [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireJavaVersion failed > with message: > Detected JDK Version: 9.0.1 is not in the allowed range [1.8,9]. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
