[jira] [Resolved] (KARAF-4748) Make Felix Resolver Threads configurable
[ https://issues.apache.org/jira/browse/KARAF-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabian Lange resolved KARAF-4748. - Resolution: Fixed > Make Felix Resolver Threads configurable > > > Key: KARAF-4748 > URL: https://issues.apache.org/jira/browse/KARAF-4748 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange > Fix For: 4.2.0, 4.1.2 > > Attachments: Screen Shot 2016-10-03 at 20.13.47.png, Screen Shot > 2016-10-04 at 09.25.48.png, Screen Shot 2016-10-04 at 09.26.04.png, Screen > Shot 2016-10-04 at 09.26.17.png, Screen Shot 2016-10-04 at 09.27.45.png, > Screen Shot 2016-10-04 at 09.28.20.png, Screen Shot 2016-10-04 at > 09.28.50.png, Screen Shot 2016-10-04 at 09.30.14.png, Screen Shot 2016-10-04 > at 09.31.16.png, Screen Shot 2016-10-04 at 11.54.19.png > > > It was requested in https://issues.apache.org/jira/browse/FELIX-5247 to make > the resolver threads configurable to avoid creating many threads by karaf. > It turns out Felix already has that feature, but Karaf is not using it: > https://github.com/apache/karaf/blob/karaf-4.0.x/features/core/src/main/java/org/apache/karaf/features/internal/osgi/Activator.java#L119 > Resolver resolver = new ResolverImpl(new Logger(Logger.LOG_INFO)); > I propose to configure and supply an Executor with the desired threads. As > additional up, this prevents situations where there are unnecessary threads > created. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-4748) Make Felix Resolver Threads configurable
[ https://issues.apache.org/jira/browse/KARAF-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabian Lange updated KARAF-4748: Fix Version/s: 4.1.2 4.2.0 > Make Felix Resolver Threads configurable > > > Key: KARAF-4748 > URL: https://issues.apache.org/jira/browse/KARAF-4748 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange > Fix For: 4.2.0, 4.1.2 > > Attachments: Screen Shot 2016-10-03 at 20.13.47.png, Screen Shot > 2016-10-04 at 09.25.48.png, Screen Shot 2016-10-04 at 09.26.04.png, Screen > Shot 2016-10-04 at 09.26.17.png, Screen Shot 2016-10-04 at 09.27.45.png, > Screen Shot 2016-10-04 at 09.28.20.png, Screen Shot 2016-10-04 at > 09.28.50.png, Screen Shot 2016-10-04 at 09.30.14.png, Screen Shot 2016-10-04 > at 09.31.16.png, Screen Shot 2016-10-04 at 11.54.19.png > > > It was requested in https://issues.apache.org/jira/browse/FELIX-5247 to make > the resolver threads configurable to avoid creating many threads by karaf. > It turns out Felix already has that feature, but Karaf is not using it: > https://github.com/apache/karaf/blob/karaf-4.0.x/features/core/src/main/java/org/apache/karaf/features/internal/osgi/Activator.java#L119 > Resolver resolver = new ResolverImpl(new Logger(Logger.LOG_INFO)); > I propose to configure and supply an Executor with the desired threads. As > additional up, this prevents situations where there are unnecessary threads > created. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KARAF-4748) Make Felix Resolver Threads configurable
[ https://issues.apache.org/jira/browse/KARAF-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabian Lange reassigned KARAF-4748: --- Assignee: Fabian Lange > Make Felix Resolver Threads configurable > > > Key: KARAF-4748 > URL: https://issues.apache.org/jira/browse/KARAF-4748 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange >Assignee: Fabian Lange > Fix For: 4.2.0, 4.1.2 > > Attachments: Screen Shot 2016-10-03 at 20.13.47.png, Screen Shot > 2016-10-04 at 09.25.48.png, Screen Shot 2016-10-04 at 09.26.04.png, Screen > Shot 2016-10-04 at 09.26.17.png, Screen Shot 2016-10-04 at 09.27.45.png, > Screen Shot 2016-10-04 at 09.28.20.png, Screen Shot 2016-10-04 at > 09.28.50.png, Screen Shot 2016-10-04 at 09.30.14.png, Screen Shot 2016-10-04 > at 09.31.16.png, Screen Shot 2016-10-04 at 11.54.19.png > > > It was requested in https://issues.apache.org/jira/browse/FELIX-5247 to make > the resolver threads configurable to avoid creating many threads by karaf. > It turns out Felix already has that feature, but Karaf is not using it: > https://github.com/apache/karaf/blob/karaf-4.0.x/features/core/src/main/java/org/apache/karaf/features/internal/osgi/Activator.java#L119 > Resolver resolver = new ResolverImpl(new Logger(Logger.LOG_INFO)); > I propose to configure and supply an Executor with the desired threads. As > additional up, this prevents situations where there are unnecessary threads > created. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-4748) Make Felix Resolver Threads configurable
[ https://issues.apache.org/jira/browse/KARAF-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fabian Lange updated KARAF-4748: Issue Type: Improvement (was: Bug) > Make Felix Resolver Threads configurable > > > Key: KARAF-4748 > URL: https://issues.apache.org/jira/browse/KARAF-4748 > Project: Karaf > Issue Type: Improvement >Reporter: Fabian Lange >Assignee: Fabian Lange > Fix For: 4.2.0, 4.1.2 > > Attachments: Screen Shot 2016-10-03 at 20.13.47.png, Screen Shot > 2016-10-04 at 09.25.48.png, Screen Shot 2016-10-04 at 09.26.04.png, Screen > Shot 2016-10-04 at 09.26.17.png, Screen Shot 2016-10-04 at 09.27.45.png, > Screen Shot 2016-10-04 at 09.28.20.png, Screen Shot 2016-10-04 at > 09.28.50.png, Screen Shot 2016-10-04 at 09.30.14.png, Screen Shot 2016-10-04 > at 09.31.16.png, Screen Shot 2016-10-04 at 11.54.19.png > > > It was requested in https://issues.apache.org/jira/browse/FELIX-5247 to make > the resolver threads configurable to avoid creating many threads by karaf. > It turns out Felix already has that feature, but Karaf is not using it: > https://github.com/apache/karaf/blob/karaf-4.0.x/features/core/src/main/java/org/apache/karaf/features/internal/osgi/Activator.java#L119 > Resolver resolver = new ResolverImpl(new Logger(Logger.LOG_INFO)); > I propose to configure and supply an Executor with the desired threads. As > additional up, this prevents situations where there are unnecessary threads > created. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-4748) Make Felix Resolver Threads configurable
[ https://issues.apache.org/jira/browse/KARAF-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063415#comment-16063415 ] ASF subversion and git services commented on KARAF-4748: Commit 9469103f2abd913473fb47c76fa412bf2b4d23ba in karaf's branch refs/heads/karaf-4.1.x from [~fabianlange] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=9469103 ] [KARAF-4748] Allow making resolver threads configurable > Make Felix Resolver Threads configurable > > > Key: KARAF-4748 > URL: https://issues.apache.org/jira/browse/KARAF-4748 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange > Attachments: Screen Shot 2016-10-03 at 20.13.47.png, Screen Shot > 2016-10-04 at 09.25.48.png, Screen Shot 2016-10-04 at 09.26.04.png, Screen > Shot 2016-10-04 at 09.26.17.png, Screen Shot 2016-10-04 at 09.27.45.png, > Screen Shot 2016-10-04 at 09.28.20.png, Screen Shot 2016-10-04 at > 09.28.50.png, Screen Shot 2016-10-04 at 09.30.14.png, Screen Shot 2016-10-04 > at 09.31.16.png, Screen Shot 2016-10-04 at 11.54.19.png > > > It was requested in https://issues.apache.org/jira/browse/FELIX-5247 to make > the resolver threads configurable to avoid creating many threads by karaf. > It turns out Felix already has that feature, but Karaf is not using it: > https://github.com/apache/karaf/blob/karaf-4.0.x/features/core/src/main/java/org/apache/karaf/features/internal/osgi/Activator.java#L119 > Resolver resolver = new ResolverImpl(new Logger(Logger.LOG_INFO)); > I propose to configure and supply an Executor with the desired threads. As > additional up, this prevents situations where there are unnecessary threads > created. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-4748) Make Felix Resolver Threads configurable
[ https://issues.apache.org/jira/browse/KARAF-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063412#comment-16063412 ] ASF subversion and git services commented on KARAF-4748: Commit 7d32dc581387bf5cd2cfcd657bacb274639d0551 in karaf's branch refs/heads/master from [~fabianlange] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=7d32dc5 ] [KARAF-4748] Allow making resolver threads configurable > Make Felix Resolver Threads configurable > > > Key: KARAF-4748 > URL: https://issues.apache.org/jira/browse/KARAF-4748 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange > Attachments: Screen Shot 2016-10-03 at 20.13.47.png, Screen Shot > 2016-10-04 at 09.25.48.png, Screen Shot 2016-10-04 at 09.26.04.png, Screen > Shot 2016-10-04 at 09.26.17.png, Screen Shot 2016-10-04 at 09.27.45.png, > Screen Shot 2016-10-04 at 09.28.20.png, Screen Shot 2016-10-04 at > 09.28.50.png, Screen Shot 2016-10-04 at 09.30.14.png, Screen Shot 2016-10-04 > at 09.31.16.png, Screen Shot 2016-10-04 at 11.54.19.png > > > It was requested in https://issues.apache.org/jira/browse/FELIX-5247 to make > the resolver threads configurable to avoid creating many threads by karaf. > It turns out Felix already has that feature, but Karaf is not using it: > https://github.com/apache/karaf/blob/karaf-4.0.x/features/core/src/main/java/org/apache/karaf/features/internal/osgi/Activator.java#L119 > Resolver resolver = new ResolverImpl(new Logger(Logger.LOG_INFO)); > I propose to configure and supply an Executor with the desired threads. As > additional up, this prevents situations where there are unnecessary threads > created. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-4748) Make Felix Resolver Threads configurable
[ https://issues.apache.org/jira/browse/KARAF-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063409#comment-16063409 ] ASF subversion and git services commented on KARAF-4748: Commit 97a40ebbef8879594826f90181697316196dcbe0 in karaf's branch refs/heads/apache/karaf-4.1.x from [~fabianlange] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=97a40eb ] [KARAF-4748] Allow making resolver threads configurable > Make Felix Resolver Threads configurable > > > Key: KARAF-4748 > URL: https://issues.apache.org/jira/browse/KARAF-4748 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange > Attachments: Screen Shot 2016-10-03 at 20.13.47.png, Screen Shot > 2016-10-04 at 09.25.48.png, Screen Shot 2016-10-04 at 09.26.04.png, Screen > Shot 2016-10-04 at 09.26.17.png, Screen Shot 2016-10-04 at 09.27.45.png, > Screen Shot 2016-10-04 at 09.28.20.png, Screen Shot 2016-10-04 at > 09.28.50.png, Screen Shot 2016-10-04 at 09.30.14.png, Screen Shot 2016-10-04 > at 09.31.16.png, Screen Shot 2016-10-04 at 11.54.19.png > > > It was requested in https://issues.apache.org/jira/browse/FELIX-5247 to make > the resolver threads configurable to avoid creating many threads by karaf. > It turns out Felix already has that feature, but Karaf is not using it: > https://github.com/apache/karaf/blob/karaf-4.0.x/features/core/src/main/java/org/apache/karaf/features/internal/osgi/Activator.java#L119 > Resolver resolver = new ResolverImpl(new Logger(Logger.LOG_INFO)); > I propose to configure and supply an Executor with the desired threads. As > additional up, this prevents situations where there are unnecessary threads > created. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KARAF-5191) can't remove mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features
[ https://issues.apache.org/jira/browse/KARAF-5191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned KARAF-5191: -- Assignee: Guillaume Nodet > can't remove mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features > -- > > Key: KARAF-5191 > URL: https://issues.apache.org/jira/browse/KARAF-5191 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.1 >Reporter: Steven Spungin >Assignee: Guillaume Nodet > > I am trying to install pax-war/6.0.2. The current Karaf uses pax-war/6.0.3. > If I add mvn:org.ops4j.pax.web/pax-web-features/6.0.2/xml/features and then > install pax-war/6.0.2, features from both 6.0.2 and 6.0.3 are installed. > Now, if I try to uninstall > mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features, I get a confirm > message but the repo is not removed. > ``` > karaf@root()> repo-remove > mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features > 08:26:31 > Removing features repository > mvn:org.ops4j.pax.web/pax-web-features/6.0.3/xml/features > ``` > ``` > pax-jetty │ 9.3.14.v20161028 │ │ Started │ > org.ops4j.pax.web-6.0.3 │ Provide Jetty engine support > pax-http-jetty │ 6.0.3│ │ Started │ > org.ops4j.pax.web-6.0.3 │ > pax-http│ 6.0.3│ │ Started │ > org.ops4j.pax.web-6.0.3 │ Implementation of the OSGI HTTP Service > pax-http-whiteboard │ 6.0.3│ │ Started │ > org.ops4j.pax.web-6.0.3 │ Provide HTTP Whiteboard pattern support > pax-jetty │ 9.3.15.v20161220 │ │ Started │ > org.ops4j.pax.web-6.0.2 │ Provide Jetty engine support > pax-http-jetty │ 6.0.2│ │ Started │ > org.ops4j.pax.web-6.0.2 │ > pax-war │ 6.0.2│ x│ Started │ > org.ops4j.pax.web-6.0.2 │ Provide support of a full WebContainer > ``` -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KARAF-5199) Karaf installs both version of the feature (old and new) in case if referencing feature contains wrapped bundle with package import
[
https://issues.apache.org/jira/browse/KARAF-5199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned KARAF-5199:
--
Assignee: Guillaume Nodet
> Karaf installs both version of the feature (old and new) in case if
> referencing feature contains wrapped bundle with package import
> ---
>
> Key: KARAF-5199
> URL: https://issues.apache.org/jira/browse/KARAF-5199
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 4.0.9
>Reporter: Andrei Shakirin
>Assignee: Guillaume Nodet
> Attachments: org.apache.karaf.features.cfg, test-feature-project.zip
>
>
> Accordingly documentation, if feature is available in multiple versions, the
> newest version have to be installed:
> {code}
> The element contains the name of a feature. A specific feature
> version can be defined using the version attribute to the element
> (feature1). If the version attribute is
> not specified, Apache Karaf will install the latest version available.
> {code}
> Unfortunatelly it is not always the case.
> Use case:
> 1) feature basit-thirdparty-jollyday references wrapped jar (jollyday
> library); this feature is available in two different versions (1.0.0-SNAPSHOT
> and 2.0.0-SNAPSHOT) and contains different versions of jolly (0.4.6 and 0.5.2
> correspondingly);
> 2) bundle test-jolly uses packages from wrapped jar (jollyday library);
> 3) feature test-feature references basit-thirdparty-jollyday and test-jolly
> bundle.
> Karaf repositories list contains both versions of basit-thirdparty-jollyday
> and test-feature:
> {code}
> karaf@root()> feature:list | grep basit
> basit-thirdparty-jollyday | 2.0.0.SNAPSHOT | | Uninstalled |
> ccp
> |
> basit-thirdparty-jollyday | 1.0.0.SNAPSHOT | | Uninstalled |
> ccp
> |
> basit-test-feature| 1.0.0.SNAPSHOT | | Uninstalled |
> ccp
> |
> karaf@root()>{code}
> If I try to install basit-thirdparty-jollyday feature - it works as expected:
> only 2.0.0.SNAPSHOT will be installed:
> {code}
> karaf@root()> feature:install -t -v basit-thirdparty-jollyday
> Adding features: basit-thirdparty-jollyday/[2.0.0.SNAPSHOT,2.0.0.SNAPSHOT]
> Changes to perform:
> Region: root
> Bundles to install:
> wrap:mvn:de.jollyday/jollyday/0.5.2
> {code}
> But if I try to install basit-test-feature, Karaf installs BOTH versions of
> basit-thirdparty-jollyday:
> {code}
> karaf@root()> feature:install -t -v basit-test-feature
> Adding features: basit-test-feature/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT]
> Changes to perform:
> Region: root
> Bundles to install:
> mvn:de.conrad.ccp.basit/test-jolly/1.0.0-SNAPSHOT
> wrap:mvn:de.jollyday/jollyday/0.4.6
> wrap:mvn:de.jollyday/jollyday/0.5.2
> karaf@root()>
> {code}
> If I exclude bundle test-jolly from basit-test-feature, installation works as
> expected again (only new jolly feature will be installed)
> The test projects to reproduce the problem and org.apache.karaf.features.cfg
> are attached
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (KARAF-5180) The framework is restarted and sometimes spits an exception when refreshing a fragment
[
https://issues.apache.org/jira/browse/KARAF-5180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved KARAF-5180.
Resolution: Fixed
> The framework is restarted and sometimes spits an exception when refreshing a
> fragment
> --
>
> Key: KARAF-5180
> URL: https://issues.apache.org/jira/browse/KARAF-5180
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 4.1.1
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.2.0, 4.1.1
>
>
> The following exception sometimes occurs too:
> {code}
> java.lang.IllegalStateException: No inital startlevel yet
> at
> org.apache.felix.framework.FrameworkStartLevelImpl.setStartLevel(FrameworkStartLevelImpl.java:131)
> at org.apache.karaf.main.Main.setStartLevel(Main.java:605)
> at org.apache.karaf.main.Main$KarafLockCallback.lockAquired(Main.java:711)
> at org.apache.karaf.main.Main.doMonitor(Main.java:382)
> at org.apache.karaf.main.Main.access$100(Main.java:75)
> at org.apache.karaf.main.Main$3.run(Main.java:369)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5223) "Error in initialization script" messages printed to the main console when clients connect through ssh
[ https://issues.apache.org/jira/browse/KARAF-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063237#comment-16063237 ] ASF subversion and git services commented on KARAF-5223: Commit 257a994a19ac2fc1853df80c14463104878fc16d in karaf's branch refs/heads/karaf-4.1.x from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=257a994 ] [KARAF-5223] "Error in initialization script" messages printed to the main console when clients connect through ssh > "Error in initialization script" messages printed to the main console when > clients connect through ssh > -- > > Key: KARAF-5223 > URL: https://issues.apache.org/jira/browse/KARAF-5223 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.0 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.2.0, 4.1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-5223) "Error in initialization script" messages printed to the main console when clients connect through ssh
[ https://issues.apache.org/jira/browse/KARAF-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet resolved KARAF-5223. Resolution: Fixed > "Error in initialization script" messages printed to the main console when > clients connect through ssh > -- > > Key: KARAF-5223 > URL: https://issues.apache.org/jira/browse/KARAF-5223 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.0 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.2.0, 4.1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5223) "Error in initialization script" messages printed to the main console when clients connect through ssh
[ https://issues.apache.org/jira/browse/KARAF-5223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063236#comment-16063236 ] ASF subversion and git services commented on KARAF-5223: Commit bf731d6e5c9dc4ecad902e6bf68a99468002ffdc in karaf's branch refs/heads/master from [~gnt] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=bf731d6 ] [KARAF-5223] "Error in initialization script" messages printed to the main console when clients connect through ssh > "Error in initialization script" messages printed to the main console when > clients connect through ssh > -- > > Key: KARAF-5223 > URL: https://issues.apache.org/jira/browse/KARAF-5223 > Project: Karaf > Issue Type: Bug >Affects Versions: 4.1.0 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.2.0, 4.1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KARAF-5223) "Error in initialization script" messages printed to the main console when clients connect through ssh
Guillaume Nodet created KARAF-5223: -- Summary: "Error in initialization script" messages printed to the main console when clients connect through ssh Key: KARAF-5223 URL: https://issues.apache.org/jira/browse/KARAF-5223 Project: Karaf Issue Type: Bug Affects Versions: 4.1.0 Reporter: Guillaume Nodet Assignee: Guillaume Nodet Fix For: 4.2.0, 4.1.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5222) Make possible to force the start of a karaf instance even if another one has been detected as running.
[
https://issues.apache.org/jira/browse/KARAF-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063130#comment-16063130
]
ASF GitHub Bot commented on KARAF-5222:
---
Github user asfgit closed the pull request at:
https://github.com/apache/karaf/pull/323
> Make possible to force the start of a karaf instance even if another one has
> been detected as running.
> --
>
> Key: KARAF-5222
> URL: https://issues.apache.org/jira/browse/KARAF-5222
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core, karaf-instance
>Affects Versions: 4.1.1
>Reporter: Andrea Tarocchi
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>
> For debug or troubleshooting purposes would be good to have a way to force
> the run, through {{bin/karaf}} script, of a karaf instance even if another
> one (the root one) has been detected as already running.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (KARAF-5222) Make possible to force the start of a karaf instance even if another one has been detected as running.
[
https://issues.apache.org/jira/browse/KARAF-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-5222.
-
Resolution: Fixed
> Make possible to force the start of a karaf instance even if another one has
> been detected as running.
> --
>
> Key: KARAF-5222
> URL: https://issues.apache.org/jira/browse/KARAF-5222
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core, karaf-instance
>Affects Versions: 4.1.1
>Reporter: Andrea Tarocchi
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>
> For debug or troubleshooting purposes would be good to have a way to force
> the run, through {{bin/karaf}} script, of a karaf instance even if another
> one (the root one) has been detected as already running.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5222) Make possible to force the start of a karaf instance even if another one has been detected as running.
[
https://issues.apache.org/jira/browse/KARAF-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063125#comment-16063125
]
ASF subversion and git services commented on KARAF-5222:
Commit c1f081cff612dbe8a6ffedb227e135195a5bd4df in karaf's branch
refs/heads/karaf-4.1.x from [~valdar]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=c1f081c ]
[KARAF-5222] Made possible to force a karaf instance start even if another one
has been found as running.
> Make possible to force the start of a karaf instance even if another one has
> been detected as running.
> --
>
> Key: KARAF-5222
> URL: https://issues.apache.org/jira/browse/KARAF-5222
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core, karaf-instance
>Affects Versions: 4.1.1
>Reporter: Andrea Tarocchi
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>
> For debug or troubleshooting purposes would be good to have a way to force
> the run, through {{bin/karaf}} script, of a karaf instance even if another
> one (the root one) has been detected as already running.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5222) Make possible to force the start of a karaf instance even if another one has been detected as running.
[
https://issues.apache.org/jira/browse/KARAF-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063122#comment-16063122
]
ASF subversion and git services commented on KARAF-5222:
Commit 9da58fcf0db5c9f45db886696a545827d52521e9 in karaf's branch
refs/heads/master from [~valdar]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=9da58fc ]
[KARAF-5222] Made possible to force a karaf instance start even if another one
has been found as running.
> Make possible to force the start of a karaf instance even if another one has
> been detected as running.
> --
>
> Key: KARAF-5222
> URL: https://issues.apache.org/jira/browse/KARAF-5222
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core, karaf-instance
>Affects Versions: 4.1.1
>Reporter: Andrea Tarocchi
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>
> For debug or troubleshooting purposes would be good to have a way to force
> the run, through {{bin/karaf}} script, of a karaf instance even if another
> one (the root one) has been detected as already running.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5222) Make possible to force the start of a karaf instance even if another one has been detected as running.
[
https://issues.apache.org/jira/browse/KARAF-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063123#comment-16063123
]
ASF subversion and git services commented on KARAF-5222:
Commit 8c1e8218f9c6185b51792d44fe317453408d3ae6 in karaf's branch
refs/heads/master from [~jbonofre]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=8c1e821 ]
[KARAF-5222] This closes #323
> Make possible to force the start of a karaf instance even if another one has
> been detected as running.
> --
>
> Key: KARAF-5222
> URL: https://issues.apache.org/jira/browse/KARAF-5222
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core, karaf-instance
>Affects Versions: 4.1.1
>Reporter: Andrea Tarocchi
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>
> For debug or troubleshooting purposes would be good to have a way to force
> the run, through {{bin/karaf}} script, of a karaf instance even if another
> one (the root one) has been detected as already running.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-4748) Make Felix Resolver Threads configurable
[ https://issues.apache.org/jira/browse/KARAF-4748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16063102#comment-16063102 ] Fabian Lange commented on KARAF-4748: - [~gnt] what do you think? The Felix change has been merged, but the problem remains for me. I really would like to control this somehow. Could we allow Resolver resolver = new ResolverImpl(new Slf4jResolverLog(LoggerFactory.getLogger(ResolverImpl.class))); to take the additional new parallelism argument? > Make Felix Resolver Threads configurable > > > Key: KARAF-4748 > URL: https://issues.apache.org/jira/browse/KARAF-4748 > Project: Karaf > Issue Type: Bug >Reporter: Fabian Lange > Attachments: Screen Shot 2016-10-03 at 20.13.47.png, Screen Shot > 2016-10-04 at 09.25.48.png, Screen Shot 2016-10-04 at 09.26.04.png, Screen > Shot 2016-10-04 at 09.26.17.png, Screen Shot 2016-10-04 at 09.27.45.png, > Screen Shot 2016-10-04 at 09.28.20.png, Screen Shot 2016-10-04 at > 09.28.50.png, Screen Shot 2016-10-04 at 09.30.14.png, Screen Shot 2016-10-04 > at 09.31.16.png, Screen Shot 2016-10-04 at 11.54.19.png > > > It was requested in https://issues.apache.org/jira/browse/FELIX-5247 to make > the resolver threads configurable to avoid creating many threads by karaf. > It turns out Felix already has that feature, but Karaf is not using it: > https://github.com/apache/karaf/blob/karaf-4.0.x/features/core/src/main/java/org/apache/karaf/features/internal/osgi/Activator.java#L119 > Resolver resolver = new ResolverImpl(new Logger(Logger.LOG_INFO)); > I propose to configure and supply an Executor with the desired threads. As > additional up, this prevents situations where there are unnecessary threads > created. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-5222) Make possible to force the start of a karaf instance even if another one has been detected as running.
[
https://issues.apache.org/jira/browse/KARAF-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-5222:
Summary: Make possible to force the start of a karaf instance even if
another one has been detected as running. (was: Meke possible to force the
start of a karaf instance even if another one has been detected as running.)
> Make possible to force the start of a karaf instance even if another one has
> been detected as running.
> --
>
> Key: KARAF-5222
> URL: https://issues.apache.org/jira/browse/KARAF-5222
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core, karaf-instance
>Affects Versions: 4.1.1
>Reporter: Andrea Tarocchi
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>
> For debug or troubleshooting purposes would be good to have a way to force
> the run, through {{bin/karaf}} script, of a karaf instance even if another
> one (the root one) has been detected as already running.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (KARAF-5222) Meke possible to force the start of a karaf instance even if another one has been detected as running.
[ https://issues.apache.org/jira/browse/KARAF-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré reassigned KARAF-5222: --- Assignee: Jean-Baptiste Onofré > Meke possible to force the start of a karaf instance even if another one has > been detected as running. > -- > > Key: KARAF-5222 > URL: https://issues.apache.org/jira/browse/KARAF-5222 > Project: Karaf > Issue Type: Improvement > Components: karaf-core, karaf-instance >Affects Versions: 4.1.1 >Reporter: Andrea Tarocchi >Assignee: Jean-Baptiste Onofré > Fix For: 4.2.0, 4.1.2 > > > For debug or troubleshooting purposes would be good to have a way to force > the run, through bin/kara script, of a karaf instance even if another one > (the root one) has been detected as already running. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KARAF-5222) Meke possible to force the start of a karaf instance even if another one has been detected as running.
[
https://issues.apache.org/jira/browse/KARAF-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-5222:
Description: For debug or troubleshooting purposes would be good to have a
way to force the run, through {{bin/karaf}} script, of a karaf instance even if
another one (the root one) has been detected as already running. (was: For
debug or troubleshooting purposes would be good to have a way to force the run,
through bin/kara script, of a karaf instance even if another one (the root one)
has been detected as already running.)
> Meke possible to force the start of a karaf instance even if another one has
> been detected as running.
> --
>
> Key: KARAF-5222
> URL: https://issues.apache.org/jira/browse/KARAF-5222
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core, karaf-instance
>Affects Versions: 4.1.1
>Reporter: Andrea Tarocchi
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.1.2
>
>
> For debug or troubleshooting purposes would be good to have a way to force
> the run, through {{bin/karaf}} script, of a karaf instance even if another
> one (the root one) has been detected as already running.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KARAF-5222) Meke possible to force the start of a karaf instance even if another one has been detected as running.
[ https://issues.apache.org/jira/browse/KARAF-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-5222: Fix Version/s: 4.1.2 4.2.0 > Meke possible to force the start of a karaf instance even if another one has > been detected as running. > -- > > Key: KARAF-5222 > URL: https://issues.apache.org/jira/browse/KARAF-5222 > Project: Karaf > Issue Type: Improvement > Components: karaf-core, karaf-instance >Affects Versions: 4.1.1 >Reporter: Andrea Tarocchi >Assignee: Jean-Baptiste Onofré > Fix For: 4.2.0, 4.1.2 > > > For debug or troubleshooting purposes would be good to have a way to force > the run, through bin/kara script, of a karaf instance even if another one > (the root one) has been detected as already running. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5222) Meke possible to force the start of a karaf instance even if another one has been detected as running.
[ https://issues.apache.org/jira/browse/KARAF-5222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062941#comment-16062941 ] ASF GitHub Bot commented on KARAF-5222: --- GitHub user valdar opened a pull request: https://github.com/apache/karaf/pull/323 [KARAF-5222] made possible to force a karaf instance start even if an… …other one has been found as running. You can merge this pull request into a Git repository by running: $ git pull https://github.com/valdar/karaf KARAF-5222 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/karaf/pull/323.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #323 commit 705d5fbfd09803dfe4bb68a258c27b136b5e9a7f Author: Andrea Tarocchi Date: 2017-06-26T11:15:33Z [KARAF-5222] made possible to force a karaf instance start even if another one has been found as running. > Meke possible to force the start of a karaf instance even if another one has > been detected as running. > -- > > Key: KARAF-5222 > URL: https://issues.apache.org/jira/browse/KARAF-5222 > Project: Karaf > Issue Type: Improvement > Components: karaf-core, karaf-instance >Affects Versions: 4.1.1 >Reporter: Andrea Tarocchi > > For debug or troubleshooting purposes would be good to have a way to force > the run, through bin/kara script, of a karaf instance even if another one > (the root one) has been detected as already running. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KARAF-5222) Meke possible to force the start of a karaf instance even if another one has been detected as running.
Andrea Tarocchi created KARAF-5222: -- Summary: Meke possible to force the start of a karaf instance even if another one has been detected as running. Key: KARAF-5222 URL: https://issues.apache.org/jira/browse/KARAF-5222 Project: Karaf Issue Type: Improvement Components: karaf-core, karaf-instance Affects Versions: 4.1.1 Reporter: Andrea Tarocchi For debug or troubleshooting purposes would be good to have a way to force the run, through bin/kara script, of a karaf instance even if another one (the root one) has been detected as already running. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-5221) karaf-maven-plugin's pidsToExtract handled incorrectly
[
https://issues.apache.org/jira/browse/KARAF-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek resolved KARAF-5221.
-
Resolution: Fixed
> karaf-maven-plugin's pidsToExtract handled incorrectly
> --
>
> Key: KARAF-5221
> URL: https://issues.apache.org/jira/browse/KARAF-5221
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
> Fix For: 4.2.0, 4.1.2
>
>
> {{org.apache.karaf.tooling.AssemblyMojo#pidsToExtract}} is simply split by
> comma and:
> {code:xml}
>
> !jmx.acl.*,
> !org.apache.karaf.command.acl.*,
> *
>
> {code}
> doesn't work.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (KARAF-5221) karaf-maven-plugin's pidsToExtract handled incorrectly
[
https://issues.apache.org/jira/browse/KARAF-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek updated KARAF-5221:
Fix Version/s: 4.1.2
4.2.0
> karaf-maven-plugin's pidsToExtract handled incorrectly
> --
>
> Key: KARAF-5221
> URL: https://issues.apache.org/jira/browse/KARAF-5221
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
> Fix For: 4.2.0, 4.1.2
>
>
> {{org.apache.karaf.tooling.AssemblyMojo#pidsToExtract}} is simply split by
> comma and:
> {code:xml}
>
> !jmx.acl.*,
> !org.apache.karaf.command.acl.*,
> *
>
> {code}
> doesn't work.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5221) karaf-maven-plugin's pidsToExtract handled incorrectly
[
https://issues.apache.org/jira/browse/KARAF-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062797#comment-16062797
]
ASF subversion and git services commented on KARAF-5221:
Commit 42fef157a227fc59457e8db3d2a7a3d6b444fa24 in karaf's branch
refs/heads/karaf-4.1.x from [~gzres]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=42fef15 ]
[KARAF-5221] Fix AssemblyMojo.pidsToExtract
(cherry picked from commit 818ab2ca36662e3ef05cd42be73058bae2b4879d)
> karaf-maven-plugin's pidsToExtract handled incorrectly
> --
>
> Key: KARAF-5221
> URL: https://issues.apache.org/jira/browse/KARAF-5221
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>
> {{org.apache.karaf.tooling.AssemblyMojo#pidsToExtract}} is simply split by
> comma and:
> {code:xml}
>
> !jmx.acl.*,
> !org.apache.karaf.command.acl.*,
> *
>
> {code}
> doesn't work.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5221) karaf-maven-plugin's pidsToExtract handled incorrectly
[
https://issues.apache.org/jira/browse/KARAF-5221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062798#comment-16062798
]
ASF subversion and git services commented on KARAF-5221:
Commit 818ab2ca36662e3ef05cd42be73058bae2b4879d in karaf's branch
refs/heads/master from [~gzres]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=818ab2c ]
[KARAF-5221] Fix AssemblyMojo.pidsToExtract
> karaf-maven-plugin's pidsToExtract handled incorrectly
> --
>
> Key: KARAF-5221
> URL: https://issues.apache.org/jira/browse/KARAF-5221
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Reporter: Grzegorz Grzybek
>Assignee: Grzegorz Grzybek
>
> {{org.apache.karaf.tooling.AssemblyMojo#pidsToExtract}} is simply split by
> comma and:
> {code:xml}
>
> !jmx.acl.*,
> !org.apache.karaf.command.acl.*,
> *
>
> {code}
> doesn't work.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5220) Cellar-Kubernetes: Bump to Kubernetes-client 2.4.1
[ https://issues.apache.org/jira/browse/KARAF-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062782#comment-16062782 ] ASF subversion and git services commented on KARAF-5220: Commit cdf924edce7e6766c89f6ccfeef5a03d458e807f in karaf-cellar's branch refs/heads/master from [~ancosen] [ https://git-wip-us.apache.org/repos/asf?p=karaf-cellar.git;h=cdf924e ] [KARAF-5220] Cellar-Kubernetes: Bump to Kubernetes-client 2.4.1 > Cellar-Kubernetes: Bump to Kubernetes-client 2.4.1 > -- > > Key: KARAF-5220 > URL: https://issues.apache.org/jira/browse/KARAF-5220 > Project: Karaf > Issue Type: Dependency upgrade > Components: cellar-core >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-5220) Cellar-Kubernetes: Bump to Kubernetes-client 2.4.1
[ https://issues.apache.org/jira/browse/KARAF-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved KARAF-5220. - Resolution: Fixed > Cellar-Kubernetes: Bump to Kubernetes-client 2.4.1 > -- > > Key: KARAF-5220 > URL: https://issues.apache.org/jira/browse/KARAF-5220 > Project: Karaf > Issue Type: Dependency upgrade > Components: cellar-core >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KARAF-5221) karaf-maven-plugin's pidsToExtract handled incorrectly
Grzegorz Grzybek created KARAF-5221:
---
Summary: karaf-maven-plugin's pidsToExtract handled incorrectly
Key: KARAF-5221
URL: https://issues.apache.org/jira/browse/KARAF-5221
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Reporter: Grzegorz Grzybek
Assignee: Grzegorz Grzybek
{{org.apache.karaf.tooling.AssemblyMojo#pidsToExtract}} is simply split by
comma and:
{code:xml}
!jmx.acl.*,
!org.apache.karaf.command.acl.*,
*
{code}
doesn't work.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (KARAF-5220) Cellar-Kubernetes: Bump to Kubernetes-client 2.4.1
[ https://issues.apache.org/jira/browse/KARAF-5220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062781#comment-16062781 ] Andrea Cosentino commented on KARAF-5220: - I marked this as cellar-core because I don't have permissions to create label, maybe a cellar-kubernetes label would be better :-) > Cellar-Kubernetes: Bump to Kubernetes-client 2.4.1 > -- > > Key: KARAF-5220 > URL: https://issues.apache.org/jira/browse/KARAF-5220 > Project: Karaf > Issue Type: Dependency upgrade > Components: cellar-core >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Minor > Fix For: 4.1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KARAF-5220) Cellar-Kubernetes: Bump to Kubernetes-client 2.4.1
Andrea Cosentino created KARAF-5220: --- Summary: Cellar-Kubernetes: Bump to Kubernetes-client 2.4.1 Key: KARAF-5220 URL: https://issues.apache.org/jira/browse/KARAF-5220 Project: Karaf Issue Type: Dependency upgrade Components: cellar-core Reporter: Andrea Cosentino Assignee: Andrea Cosentino Priority: Minor Fix For: 4.1.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-5219) Upgrade Narayana to version 5.6.2.Final
[ https://issues.apache.org/jira/browse/KARAF-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved KARAF-5219. - Resolution: Fixed > Upgrade Narayana to version 5.6.2.Final > --- > > Key: KARAF-5219 > URL: https://issues.apache.org/jira/browse/KARAF-5219 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5219) Upgrade Narayana to version 5.6.2.Final
[ https://issues.apache.org/jira/browse/KARAF-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062775#comment-16062775 ] ASF subversion and git services commented on KARAF-5219: Commit a2e46e8996087ee937b360fc1b01cd63afb37dd5 in karaf's branch refs/heads/master from [~ancosen] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=a2e46e8 ] [KARAF-5219] Upgrade Narayana to version 5.6.2.Final > Upgrade Narayana to version 5.6.2.Final > --- > > Key: KARAF-5219 > URL: https://issues.apache.org/jira/browse/KARAF-5219 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino > Fix For: 4.2.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KARAF-4329) Consider bundles from override.properties whie creating the assembly
[ https://issues.apache.org/jira/browse/KARAF-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek reassigned KARAF-4329: --- Assignee: Grzegorz Grzybek > Consider bundles from override.properties whie creating the assembly > > > Key: KARAF-4329 > URL: https://issues.apache.org/jira/browse/KARAF-4329 > Project: Karaf > Issue Type: Improvement > Components: karaf-tooling >Affects Versions: 4.1.0, 4.0.4 >Reporter: Krzysztof Sobkowiak >Assignee: Grzegorz Grzybek > > The assembly goal of the karaf-maven-plugin should check an > override.properties and always populate system folder with bundles defined > there -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KARAF-4655) karaf-maven-plugin add-features-to-repo goal can't add Camel feature
[
https://issues.apache.org/jira/browse/KARAF-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek reassigned KARAF-4655:
---
Assignee: Jean-Baptiste Onofré (was: Grzegorz Grzybek)
> karaf-maven-plugin add-features-to-repo goal can't add Camel feature
>
>
> Key: KARAF-4655
> URL: https://issues.apache.org/jira/browse/KARAF-4655
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Affects Versions: 4.0.5, 4.0.6
>Reporter: Igor Lazebny
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.2, 4.0.10
>
> Attachments: pom.xml
>
>
> camel-restlet 2.17.3 feature contains bundle reference like this:
> {{ dependency="true">mvn:http://maven.restlet.org@id=restlet!org.restlet.osgi/org.restlet/2.3.6}}
> add-features-to-repo can't interpret it correctly trying to connect to
> "id=restlet" host:
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.0.6-SNAPSHOT:features-add-to-repository
> (add-features-to-repo) on project karaf-maven-plugin-test: Error populating
> repository: Error resolving feature camel-restlet/2.17.3: Error resolving
> artifact
> mvn:http://maven.restlet.org@id=restlet!org.restlet.osgi/org.restlet/2.3.6:
> Can't resolve artifact org.restlet.osgi:org.restlet:jar:2.3.6: Could not
> transfer artifact org.restlet.osgi:org.restlet:jar:2.3.6 from/to
> http://maven.restlet.org@id=restlet (http://id=restlet): id=restlet: unknown
> error
> [ERROR] org.restlet.osgi:org.restlet:jar:2.3.6
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] http://maven.restlet.org@id=restlet (http://id=restlet,
> releases=true, snapshots=true): Unknown host id=restlet: unknown error
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (KARAF-4655) karaf-maven-plugin add-features-to-repo goal can't add Camel feature
[
https://issues.apache.org/jira/browse/KARAF-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grzegorz Grzybek reassigned KARAF-4655:
---
Assignee: Grzegorz Grzybek (was: Jean-Baptiste Onofré)
> karaf-maven-plugin add-features-to-repo goal can't add Camel feature
>
>
> Key: KARAF-4655
> URL: https://issues.apache.org/jira/browse/KARAF-4655
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Affects Versions: 4.0.5, 4.0.6
>Reporter: Igor Lazebny
>Assignee: Grzegorz Grzybek
> Fix For: 4.1.2, 4.0.10
>
> Attachments: pom.xml
>
>
> camel-restlet 2.17.3 feature contains bundle reference like this:
> {{ dependency="true">mvn:http://maven.restlet.org@id=restlet!org.restlet.osgi/org.restlet/2.3.6}}
> add-features-to-repo can't interpret it correctly trying to connect to
> "id=restlet" host:
> [ERROR] Failed to execute goal
> org.apache.karaf.tooling:karaf-maven-plugin:4.0.6-SNAPSHOT:features-add-to-repository
> (add-features-to-repo) on project karaf-maven-plugin-test: Error populating
> repository: Error resolving feature camel-restlet/2.17.3: Error resolving
> artifact
> mvn:http://maven.restlet.org@id=restlet!org.restlet.osgi/org.restlet/2.3.6:
> Can't resolve artifact org.restlet.osgi:org.restlet:jar:2.3.6: Could not
> transfer artifact org.restlet.osgi:org.restlet:jar:2.3.6 from/to
> http://maven.restlet.org@id=restlet (http://id=restlet): id=restlet: unknown
> error
> [ERROR] org.restlet.osgi:org.restlet:jar:2.3.6
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] http://maven.restlet.org@id=restlet (http://id=restlet,
> releases=true, snapshots=true): Unknown host id=restlet: unknown error
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (KARAF-5219) Upgrade Narayana to version 5.6.2.Final
Andrea Cosentino created KARAF-5219: --- Summary: Upgrade Narayana to version 5.6.2.Final Key: KARAF-5219 URL: https://issues.apache.org/jira/browse/KARAF-5219 Project: Karaf Issue Type: Dependency upgrade Components: karaf-core Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 4.2.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-2970) Software deployed on Karaf will not update if Karaf detects the presence of a previous .M2 directory
[ https://issues.apache.org/jira/browse/KARAF-2970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062669#comment-16062669 ] Grzegorz Grzybek commented on KARAF-2970: - Please read [aether configuration documentation|https://ops4j1.jira.com/wiki/display/paxurl/Aether+Configuration] where you can see various configuration options related to update policies etc. Also, I hope you'll find helpful my series of articles related to "Maven on OSGi": * [introduction|http://ggrzybek.blogspot.com/2016/07/using-maven-with-osgi-part-1.html] * [configuration|http://ggrzybek.blogspot.com/2016/07/using-maven-with-osgi-part-2.html] * [SNAPSHOTs|http://ggrzybek.blogspot.com/2016/10/using-maven-with-osgi-part-3.html] > Software deployed on Karaf will not update if Karaf detects the presence of a > previous .M2 directory > - > > Key: KARAF-2970 > URL: https://issues.apache.org/jira/browse/KARAF-2970 > Project: Karaf > Issue Type: Bug > Components: karaf-archetypes, karaf-config, karaf-core, > karaf-documentation, karaf-exam, karaf-feature, karaf-instance, karaf-kar, > karaf-os-integration, karaf-osgi, karaf-repository, karaf-scheduler, > karaf-scr, karaf-security, karaf-shell, karaf-test, karaf-tooling, > karaf-webconsole, karaf-webcontainer >Affects Versions: 3.0.0 > Environment: Windows Server 2008 R2, Windows 2008 R2 SP2, Windows > 2012 R2 >Reporter: Chris Longo > > The presence of a .M2 directory causes an application deployed on Karaf not > to update. > Prerequisites: > A) Deploy an application on Karaf > B) Verify there is the presence of an .M2 directory > Steps to Reproduce: > Deploy a revised application build on Karaf > Actual Result: > The bits from the local .M2 repo are kept and not overwritten with the newest > modified bits > Expected Result: > The bits from the local .M2 repo should be updated even if the .M2 directory > was present prior to installing the updated app deployed on Karaf > Workaround: > 1.Delete the .M2 directory > 2.Deploy the software on Karaf > 3.The local .M2 directory will now be updated -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5102) org.ops4j.pax.logging.cfg contains non-ASCII character
[ https://issues.apache.org/jira/browse/KARAF-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062661#comment-16062661 ] Grzegorz Grzybek commented on KARAF-5102: - Thanks [~amarkevich] for spotting this! > org.ops4j.pax.logging.cfg contains non-ASCII character > -- > > Key: KARAF-5102 > URL: https://issues.apache.org/jira/browse/KARAF-5102 > Project: Karaf > Issue Type: Improvement > Components: karaf-config >Affects Versions: 4.1.1 >Reporter: Alexey Markevich >Assignee: Grzegorz Grzybek > Fix For: 4.2.0, 4.1.2 > > > https://github.com/apache/karaf/blob/master/assemblies/features/base/src/main/resources/resources/etc/org.ops4j.pax.logging.cfg#L40 > & L68 > Cause problem like https://tickets.puppetlabs.com/browse/PUP-1031 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KARAF-5102) org.ops4j.pax.logging.cfg contains non-ASCII character
[ https://issues.apache.org/jira/browse/KARAF-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek resolved KARAF-5102. - Resolution: Fixed Fix Version/s: 4.1.2 4.2.0 > org.ops4j.pax.logging.cfg contains non-ASCII character > -- > > Key: KARAF-5102 > URL: https://issues.apache.org/jira/browse/KARAF-5102 > Project: Karaf > Issue Type: Improvement > Components: karaf-config >Affects Versions: 4.1.1 >Reporter: Alexey Markevich >Assignee: Grzegorz Grzybek > Fix For: 4.2.0, 4.1.2 > > > https://github.com/apache/karaf/blob/master/assemblies/features/base/src/main/resources/resources/etc/org.ops4j.pax.logging.cfg#L40 > & L68 > Cause problem like https://tickets.puppetlabs.com/browse/PUP-1031 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (KARAF-5102) org.ops4j.pax.logging.cfg contains non-ASCII character
[ https://issues.apache.org/jira/browse/KARAF-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Grzybek reassigned KARAF-5102: --- Assignee: Grzegorz Grzybek > org.ops4j.pax.logging.cfg contains non-ASCII character > -- > > Key: KARAF-5102 > URL: https://issues.apache.org/jira/browse/KARAF-5102 > Project: Karaf > Issue Type: Improvement > Components: karaf-config >Affects Versions: 4.1.1 >Reporter: Alexey Markevich >Assignee: Grzegorz Grzybek > Fix For: 4.2.0, 4.1.2 > > > https://github.com/apache/karaf/blob/master/assemblies/features/base/src/main/resources/resources/etc/org.ops4j.pax.logging.cfg#L40 > & L68 > Cause problem like https://tickets.puppetlabs.com/browse/PUP-1031 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5102) org.ops4j.pax.logging.cfg contains non-ASCII character
[ https://issues.apache.org/jira/browse/KARAF-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062659#comment-16062659 ] ASF subversion and git services commented on KARAF-5102: Commit 528455ab7fce6b3f6359caaefd844b4ea36c90e7 in karaf's branch refs/heads/karaf-4.1.x from [~gzres] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=528455a ] [KARAF-5102] Remove non-ascii characters from org.ops4j.pax.logging.cfg (cherry picked from commit b6e32ca5969222e934ed0bfdf7cd7703e0573588) > org.ops4j.pax.logging.cfg contains non-ASCII character > -- > > Key: KARAF-5102 > URL: https://issues.apache.org/jira/browse/KARAF-5102 > Project: Karaf > Issue Type: Improvement > Components: karaf-config >Affects Versions: 4.1.1 >Reporter: Alexey Markevich > > https://github.com/apache/karaf/blob/master/assemblies/features/base/src/main/resources/resources/etc/org.ops4j.pax.logging.cfg#L40 > & L68 > Cause problem like https://tickets.puppetlabs.com/browse/PUP-1031 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KARAF-5102) org.ops4j.pax.logging.cfg contains non-ASCII character
[ https://issues.apache.org/jira/browse/KARAF-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062660#comment-16062660 ] ASF subversion and git services commented on KARAF-5102: Commit b6e32ca5969222e934ed0bfdf7cd7703e0573588 in karaf's branch refs/heads/master from [~gzres] [ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=b6e32ca ] [KARAF-5102] Remove non-ascii characters from org.ops4j.pax.logging.cfg > org.ops4j.pax.logging.cfg contains non-ASCII character > -- > > Key: KARAF-5102 > URL: https://issues.apache.org/jira/browse/KARAF-5102 > Project: Karaf > Issue Type: Improvement > Components: karaf-config >Affects Versions: 4.1.1 >Reporter: Alexey Markevich > > https://github.com/apache/karaf/blob/master/assemblies/features/base/src/main/resources/resources/etc/org.ops4j.pax.logging.cfg#L40 > & L68 > Cause problem like https://tickets.puppetlabs.com/browse/PUP-1031 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
