[jira] [Resolved] (KARAF-4767) Decanter: collectors and appenders can't be re-used without default configuration

[Achim Nierbeck (JIRA)]

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

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

fixed with last commit


> Decanter: collectors and appenders can't be re-used without default 
> configuration
> -
>
> Key: KARAF-4767
> URL: https://issues.apache.org/jira/browse/KARAF-4767
> Project: Karaf
>  Issue Type: Bug
>  Components: decanter
>Affects Versions: decanter-1.2.0
>Reporter: Achim Nierbeck
>Assignee: Achim Nierbeck
> Fix For: decanter-1.3.0
>
>
> Right now the jmx collector and various appenders can't be re-used without 
> the default configs, those features should be split into the current one 
> which references a *-core feature. This way it's easier to re-use the jmx 
> collector or the elasticsearch appender ... 



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

[jira] [Commented] (KARAF-4767) Decanter: collectors and appenders can't be re-used without default configuration

[ASF subversion and git services (JIRA)]

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

ASF subversion and git services commented on KARAF-4767:


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

[KARAF-4767] - Decanter: collectors and appenders can't be re-used
without default configuration

> Decanter: collectors and appenders can't be re-used without default 
> configuration
> -
>
> Key: KARAF-4767
> URL: https://issues.apache.org/jira/browse/KARAF-4767
> Project: Karaf
>  Issue Type: Bug
>  Components: decanter
>Affects Versions: decanter-1.2.0
>Reporter: Achim Nierbeck
>Assignee: Achim Nierbeck
> Fix For: decanter-1.3.0
>
>
> Right now the jmx collector and various appenders can't be re-used without 
> the default configs, those features should be split into the current one 
> which references a *-core feature. This way it's easier to re-use the jmx 
> collector or the elasticsearch appender ... 



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

[jira] [Updated] (KARAF-4764) Provide ability to configure RmiRegistryFactory create and locate options

[Dmitry Konstantinov (JIRA)]

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

Dmitry Konstantinov updated KARAF-4764:
---
Labels: perfomance  (was: )

> Provide ability to configure RmiRegistryFactory create and locate options
> -
>
> Key: KARAF-4764
> URL: https://issues.apache.org/jira/browse/KARAF-4764
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-management
>Affects Versions: 3.0.8, 4.0.7
>Reporter: Dmitry Konstantinov
>  Labels: performance
>
> At this moment locate and create options are set to true in code and there is 
> no ability to control these options via Configuration Admin.
> Sometimes it make sense:
> 1) to not create RMI Registry (to not open a port)
> 2) do not try to locate an existing one, the locate logic is needed rarely 
> but adds about 1 second to startup time (connection establishment attempt) 
> It would be nice to control these options via org.apache.karaf.management 
> configuration.



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

[jira] [Updated] (KARAF-4764) Provide ability to configure RmiRegistryFactory create and locate options

[Dmitry Konstantinov (JIRA)]

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

Dmitry Konstantinov updated KARAF-4764:
---
Labels: performance  (was: perfomance)

> Provide ability to configure RmiRegistryFactory create and locate options
> -
>
> Key: KARAF-4764
> URL: https://issues.apache.org/jira/browse/KARAF-4764
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-management
>Affects Versions: 3.0.8, 4.0.7
>Reporter: Dmitry Konstantinov
>  Labels: performance
>
> At this moment locate and create options are set to true in code and there is 
> no ability to control these options via Configuration Admin.
> Sometimes it make sense:
> 1) to not create RMI Registry (to not open a port)
> 2) do not try to locate an existing one, the locate logic is needed rarely 
> but adds about 1 second to startup time (connection establishment attempt) 
> It would be nice to control these options via org.apache.karaf.management 
> configuration.



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

[jira] [Commented] (KARAF-4767) Decanter: collectors and appenders can't be re-used without default configuration

[JIRA]

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

Jean-Baptiste Onofré commented on KARAF-4767:
-

By the way, I already created a Jira regarding the JMX appender and already 
started for this one.

> Decanter: collectors and appenders can't be re-used without default 
> configuration
> -
>
> Key: KARAF-4767
> URL: https://issues.apache.org/jira/browse/KARAF-4767
> Project: Karaf
>  Issue Type: Bug
>  Components: decanter
>Affects Versions: decanter-1.2.0
>Reporter: Achim Nierbeck
>Assignee: Achim Nierbeck
> Fix For: decanter-1.3.0
>
>
> Right now the jmx collector and various appenders can't be re-used without 
> the default configs, those features should be split into the current one 
> which references a *-core feature. This way it's easier to re-use the jmx 
> collector or the elasticsearch appender ... 



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

[jira] [Commented] (KARAF-4707) Add pax-url-classpath feature

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet commented on KARAF-4707:


I think for url handlers, it's better to use the uber jars.  The urls handlers 
integrate tightly into the framework / VM in an usual way and used without much 
way to actually "wait" for them, unlike plain OSGi services.
I'd rather avoid having url handlers depend on too many things, as it may 
become the target of a refresh for an unneeded reason and increase the risk of 
entering an unwanted state.  In particular, url handlers are used by the 
feature service, usually as prerequisite features to install bundles using 
those urls.  
So I'm all for having features for those handlers, but not really one 
installing all the small bundles.

Also, we already have builtin support for the main 3 ones: mvn, wrap and war 
(through pax-web). All of them are using the uber bundles.

> Add pax-url-classpath feature
> -
>
> Key: KARAF-4707
> URL: https://issues.apache.org/jira/browse/KARAF-4707
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-feature
>Reporter: Alex Soto
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.8
>
>
> To make it easier to use class path URLs.  Something like.
> {code:xml}
> 
>   mvn:org.ops4j.base/ops4j-base-util-property/1.5.0
> mvn:org.ops4j.base/ops4j-base-lang/1.5.0
>   mvn:org.ops4j.pax.swissbox/pax-swissbox-property/1.8.2
> mvn:org.ops4j.pax.url/pax-url-commons/2.4.7
> mvn:org.ops4j.pax.url/pax-url-classpath/2.4.7
> 
> {code}
> Also, it would be nice to have documentation about how to use it for 
> deploying config files in features.xml:
> {code:xml}
> 
>   classpath:my.config.cfg
> 
> {code}



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

[jira] [Work started] (KARAF-2454) Portable way to make custom shell commands (without inheriting from OsgiCommandSupport)

[Guillaume Nodet (JIRA)]

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

Work on KARAF-2454 started by Guillaume Nodet.
--
> Portable way to make custom shell commands (without inheriting from 
> OsgiCommandSupport)
> ---
>
> Key: KARAF-2454
> URL: https://issues.apache.org/jira/browse/KARAF-2454
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 2.3.2
> Environment: All
>Reporter: Morten Christensen
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> I would like to be able to create osgi shell commands that work across karaf 
> and standard osgi implementations like felix, eclipse (both using gogo). When 
> deployed in karaf, the shell commands should support completion and the other 
> karaf specific features and when deployed in plain felix just work as in the 
> standard. Currently, karaf makes this difficult as commands must extend from 
> karaf specific OsgiCommandSupport class. I would like a way to support karaf 
> using some karaf specific configuration outside the command classes that 
> should use standard OSGI stuff only. 



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

[jira] [Created] (KARAF-4767) Decanter: collectors and appenders can't be re-used without default configuration

[Achim Nierbeck (JIRA)]

Achim Nierbeck created KARAF-4767:
-

 Summary: Decanter: collectors and appenders can't be re-used 
without default configuration
 Key: KARAF-4767
 URL: https://issues.apache.org/jira/browse/KARAF-4767
 Project: Karaf
  Issue Type: Bug
  Components: decanter
Affects Versions: decanter-1.2.0
Reporter: Achim Nierbeck
Assignee: Achim Nierbeck
 Fix For: decanter-1.3.0


Right now the jmx collector and various appenders can't be re-used without the 
default configs, those features should be split into the current one which 
references a *-core feature. This way it's easier to re-use the jmx collector 
or the elasticsearch appender ... 



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

[jira] [Work started] (KARAF-4767) Decanter: collectors and appenders can't be re-used without default configuration

[Achim Nierbeck (JIRA)]

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

Work on KARAF-4767 started by Achim Nierbeck.
-
> Decanter: collectors and appenders can't be re-used without default 
> configuration
> -
>
> Key: KARAF-4767
> URL: https://issues.apache.org/jira/browse/KARAF-4767
> Project: Karaf
>  Issue Type: Bug
>  Components: decanter
>Affects Versions: decanter-1.2.0
>Reporter: Achim Nierbeck
>Assignee: Achim Nierbeck
> Fix For: decanter-1.3.0
>
>
> Right now the jmx collector and various appenders can't be re-used without 
> the default configs, those features should be split into the current one 
> which references a *-core feature. This way it's easier to re-use the jmx 
> collector or the elasticsearch appender ... 



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

[jira] [Commented] (KARAF-4764) Provide ability to configure RmiRegistryFactory create and locate options

[ASF GitHub Bot (JIRA)]

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

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

GitHub user netudima opened a pull request:

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

[KARAF-4764] Add ability to configure RMI Registry locate and create …

…flags

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/netudima/karaf master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/karaf/pull/248.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 #248


commit 1ba9f42b197177174d5b4edea9ed759c24ca3c11
Author: Dmitry Konstantinov 
Date:   2016-10-12T14:36:46Z

[KARAF-4764] Add ability to configure RMI Registry locate and create flags




> Provide ability to configure RmiRegistryFactory create and locate options
> -
>
> Key: KARAF-4764
> URL: https://issues.apache.org/jira/browse/KARAF-4764
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-management
>Affects Versions: 3.0.8, 4.0.7
>Reporter: Dmitry Konstantinov
>
> At this moment locate and create options are set to true in code and there is 
> no ability to control these options via Configuration Admin.
> Sometimes it make sense:
> 1) to not create RMI Registry (to not open a port)
> 2) do not try to locate an existing one, the locate logic is needed rarely 
> but adds about 1 second to startup time (connection establishment attempt) 
> It would be nice to control these options via org.apache.karaf.management 
> configuration.



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

[jira] [Closed] (KARAF-2973) Writing to stderr results in a blocked thread

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet closed KARAF-2973.
--
Resolution: Won't Fix
  Assignee: Guillaume Nodet

This looks the correct behavior.
Karaf acts like an OS, so if you launch a command the err stream will always be 
printed to your terminal, be it local or remote through ssh.

> Writing to stderr results in a blocked thread
> -
>
> Key: KARAF-2973
> URL: https://issues.apache.org/jira/browse/KARAF-2973
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 2.3.4
>Reporter: Martin Lichtin
>Assignee: Guillaume Nodet
>
> An innocent-looking e.printStackTrace() resulted in a blocked thread.
> {noformat}
> "Camel (CamelContext) thread #0 - JmsConsumer[myname]" daemon prio=10 
> tid=0x2aaab886d000 nid=0x3396 in Object.wait() [0x4963d000]
>java.lang.Thread.State: WAITING (on object monitor)
>   at java.lang.Object.wait(Native Method)
>   - waiting on <0xce040a38> (a 
> org.apache.sshd.common.channel.Window)
>   at java.lang.Object.wait(Object.java:503)
>   at org.apache.sshd.common.channel.Window.waitForSpace(Window.java:146)
>   - locked <0xce040a38> (a org.apache.sshd.common.channel.Window)
>   at 
> org.apache.sshd.common.channel.ChannelOutputStream.flush(ChannelOutputStream.java:104)
>   - locked <0xcdfac4a0> (a 
> org.apache.sshd.common.channel.ChannelOutputStream)
>   at 
> org.apache.sshd.common.channel.ChannelOutputStream.write(ChannelOutputStream.java:75)
>   - locked <0xcdfac4a0> (a 
> org.apache.sshd.common.channel.ChannelOutputStream)
>   at 
> org.apache.sshd.common.channel.ChannelOutputStream.write(ChannelOutputStream.java:57)
>   - locked <0xcdfac4a0> (a 
> org.apache.sshd.common.channel.ChannelOutputStream)
>   at 
> org.apache.karaf.shell.ssh.ShellFactoryImpl$LfToCrLfFilterOutputStream.write(ShellFactoryImpl.java:215)
>   at java.io.FilterOutputStream.write(FilterOutputStream.java:125)
>   at java.io.PrintStream.write(PrintStream.java:480)
>   - locked <0xce500078> (a java.io.PrintStream)
>   at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
>   at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291)
>   at sun.nio.cs.StreamEncoder.flushBuffer(StreamEncoder.java:104)
>   - locked <0xce5064c0> (a java.io.OutputStreamWriter)
>   at java.io.OutputStreamWriter.flushBuffer(OutputStreamWriter.java:185)
>   at java.io.PrintStream.write(PrintStream.java:527)
>   - locked <0xce500078> (a java.io.PrintStream)
>   at java.io.PrintStream.print(PrintStream.java:669)
>   at java.io.PrintStream.println(PrintStream.java:823)
>   - locked <0xce500078> (a java.io.PrintStream)
>   at 
> org.apache.felix.gogo.runtime.threadio.ThreadPrintStream.println(ThreadPrintStream.java:205)
>   at java.lang.Throwable$WrappedPrintStream.println(Throwable.java:747)
>   at java.lang.Throwable.printStackTrace(Throwable.java:657)
>   - locked <0xcd8f9110> (a 
> org.apache.felix.gogo.runtime.threadio.ThreadPrintStream)
>   at java.lang.Throwable.printStackTrace(Throwable.java:642)
>   at java.lang.Throwable.printStackTrace(Throwable.java:633)
> ...
> {noformat}
> What's weird is that it tries to write to a (probably no longer existing) SSH 
> session.
> Why does Felix intercept stderr writes from bundles. 
> I'd expect printing a stack trace goes directly to fd 3 (which is redirected 
> to data/karaf.out) and is not affected by some temporary SSH console sessions.



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

[jira] [Created] (KARAF-4766) Add a MQTT collector

[JIRA]

Jean-Baptiste Onofré created KARAF-4766:
---

 Summary: Add a MQTT collector
 Key: KARAF-4766
 URL: https://issues.apache.org/jira/browse/KARAF-4766
 Project: Karaf
  Issue Type: Improvement
  Components: decanter
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
 Fix For: decanter-1.3.0


As we have a MQTT appender, it makes sense to provide a MQTT collector.



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

[jira] [Created] (KARAF-4765) Provide decanter-collector-jmx-core that doesn't install the default cfg file

[JIRA]

Jean-Baptiste Onofré created KARAF-4765:
---

 Summary: Provide decanter-collector-jmx-core that doesn't install 
the default cfg file
 Key: KARAF-4765
 URL: https://issues.apache.org/jira/browse/KARAF-4765
 Project: Karaf
  Issue Type: Improvement
  Components: decanter
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
 Fix For: decanter-1.3.0


Now, the {{decanter-collector-jmx}} feature systematically installs the default 
{{jmx-local}} configuration.

Some users may want to no install it by default and install their own cfg files.

So, Decanter will provide a {{decanter-collector-jmx-core}} just installing the 
transitive features and bundles, but not the default cfg file.

The {{decanter-collector-jmx}} feature will install the 
{{decanter-collector-jmx-core}} feature with the default cfg (so it doesn't 
change compared to what we do today).



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

[jira] [Commented] (KARAF-4761) EnterpriseFeaturesTest installTransaction130Feature test fails during full build

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino commented on KARAF-4761:
-

Fixed with 
https://git1-us-west.apache.org/repos/asf?p=karaf.git;a=commit;h=cd72111c

> EnterpriseFeaturesTest installTransaction130Feature test fails during full 
> build
> 
>
> Key: KARAF-4761
> URL: https://issues.apache.org/jira/browse/KARAF-4761
> Project: Karaf
>  Issue Type: Test
>  Components: karaf-test
>Affects Versions: 4.1.0
>Reporter: Andrea Cosentino
>Priority: Minor
> Fix For: 4.1.0, 4.0.8
>
>
> Tests run: 18, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.153 sec 
> <<< FAILURE! - in org.apache.karaf.itests.features.EnterpriseFeaturesTest
> installTransaction130Feature(org.apache.karaf.itests.features.EnterpriseFeaturesTest)
>   Time elapsed: 0.024 sec  <<< ERROR!
> java.lang.IllegalArgumentException: No matching features for transaction/1.3.0
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:908)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:827)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:812)
>   at 
> org.apache.karaf.itests.KarafTestSupport.installAssertAndUninstallFeatures(KarafTestSupport.java:568)
>   at 
> org.apache.karaf.itests.KarafTestSupport.installAssertAndUninstallFeature(KarafTestSupport.java:561)
>   at 
> org.apache.karaf.itests.features.EnterpriseFeaturesTest.installTransaction130Feature(EnterpriseFeaturesTest.java:38)



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

[jira] [Updated] (KARAF-4761) EnterpriseFeaturesTest installTransaction130Feature test fails during full build

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino updated KARAF-4761:

Assignee: Jean-Baptiste Onofré

> EnterpriseFeaturesTest installTransaction130Feature test fails during full 
> build
> 
>
> Key: KARAF-4761
> URL: https://issues.apache.org/jira/browse/KARAF-4761
> Project: Karaf
>  Issue Type: Test
>  Components: karaf-test
>Affects Versions: 4.1.0
>Reporter: Andrea Cosentino
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.8
>
>
> Tests run: 18, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.153 sec 
> <<< FAILURE! - in org.apache.karaf.itests.features.EnterpriseFeaturesTest
> installTransaction130Feature(org.apache.karaf.itests.features.EnterpriseFeaturesTest)
>   Time elapsed: 0.024 sec  <<< ERROR!
> java.lang.IllegalArgumentException: No matching features for transaction/1.3.0
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:908)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:827)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:812)
>   at 
> org.apache.karaf.itests.KarafTestSupport.installAssertAndUninstallFeatures(KarafTestSupport.java:568)
>   at 
> org.apache.karaf.itests.KarafTestSupport.installAssertAndUninstallFeature(KarafTestSupport.java:561)
>   at 
> org.apache.karaf.itests.features.EnterpriseFeaturesTest.installTransaction130Feature(EnterpriseFeaturesTest.java:38)



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

[jira] [Updated] (KARAF-4761) EnterpriseFeaturesTest installTransaction130Feature test fails during full build

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino updated KARAF-4761:

Fix Version/s: 4.0.8
   4.1.0

> EnterpriseFeaturesTest installTransaction130Feature test fails during full 
> build
> 
>
> Key: KARAF-4761
> URL: https://issues.apache.org/jira/browse/KARAF-4761
> Project: Karaf
>  Issue Type: Test
>  Components: karaf-test
>Affects Versions: 4.1.0
>Reporter: Andrea Cosentino
>Priority: Minor
> Fix For: 4.1.0, 4.0.8
>
>
> Tests run: 18, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.153 sec 
> <<< FAILURE! - in org.apache.karaf.itests.features.EnterpriseFeaturesTest
> installTransaction130Feature(org.apache.karaf.itests.features.EnterpriseFeaturesTest)
>   Time elapsed: 0.024 sec  <<< ERROR!
> java.lang.IllegalArgumentException: No matching features for transaction/1.3.0
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:908)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:827)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:812)
>   at 
> org.apache.karaf.itests.KarafTestSupport.installAssertAndUninstallFeatures(KarafTestSupport.java:568)
>   at 
> org.apache.karaf.itests.KarafTestSupport.installAssertAndUninstallFeature(KarafTestSupport.java:561)
>   at 
> org.apache.karaf.itests.features.EnterpriseFeaturesTest.installTransaction130Feature(EnterpriseFeaturesTest.java:38)



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

[jira] [Resolved] (KARAF-4761) EnterpriseFeaturesTest installTransaction130Feature test fails during full build

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino resolved KARAF-4761.
-
Resolution: Fixed

> EnterpriseFeaturesTest installTransaction130Feature test fails during full 
> build
> 
>
> Key: KARAF-4761
> URL: https://issues.apache.org/jira/browse/KARAF-4761
> Project: Karaf
>  Issue Type: Test
>  Components: karaf-test
>Affects Versions: 4.1.0
>Reporter: Andrea Cosentino
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.1.0, 4.0.8
>
>
> Tests run: 18, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.153 sec 
> <<< FAILURE! - in org.apache.karaf.itests.features.EnterpriseFeaturesTest
> installTransaction130Feature(org.apache.karaf.itests.features.EnterpriseFeaturesTest)
>   Time elapsed: 0.024 sec  <<< ERROR!
> java.lang.IllegalArgumentException: No matching features for transaction/1.3.0
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:908)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:827)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:812)
>   at 
> org.apache.karaf.itests.KarafTestSupport.installAssertAndUninstallFeatures(KarafTestSupport.java:568)
>   at 
> org.apache.karaf.itests.KarafTestSupport.installAssertAndUninstallFeature(KarafTestSupport.java:561)
>   at 
> org.apache.karaf.itests.features.EnterpriseFeaturesTest.installTransaction130Feature(EnterpriseFeaturesTest.java:38)



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

[jira] [Created] (KARAF-4764) Provide ability to configure RmiRegistryFactory create and locate options

[Dmitry Konstantinov (JIRA)]

Dmitry Konstantinov created KARAF-4764:
--

 Summary: Provide ability to configure RmiRegistryFactory create 
and locate options
 Key: KARAF-4764
 URL: https://issues.apache.org/jira/browse/KARAF-4764
 Project: Karaf
  Issue Type: Improvement
  Components: karaf-management
Affects Versions: 4.0.7, 3.0.8
Reporter: Dmitry Konstantinov


At this moment locate and create options are set to true in code and there is 
no ability to control these options via Configuration Admin.
Sometimes it make sense:
1) to not create RMI Registry (to not open a port)
2) do not try to locate an existing one, the locate logic is needed rarely but 
adds about 1 second to startup time (connection establishment attempt) 
It would be nice to control these options via org.apache.karaf.management 
configuration.



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

[jira] [Closed] (KARAF-1382) Error during executing few commands with pipes

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet closed KARAF-1382.
--
Resolution: Won't Fix

> Error during executing few commands with pipes
> --
>
> Key: KARAF-1382
> URL: https://issues.apache.org/jira/browse/KARAF-1382
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 2.2.6
> Environment: W7 x64
>Reporter: Pavel Vasilchenko
>
> I trying create karaf script for starting Cellar like this:
> tesb:start-cluster = { features:install cellar | cluster:group-create $args | 
> cluster:group-set $args} ;
> But when I execute this command I get exception at command 
> cluster:group-create because, if I right understand, Karaf invoke pipes as 
> parallel commands.
> Line 187 
> http://svn.apache.org/viewvc/karaf/tags/karaf-2.2.6/shell/console/src/main/java/org/apache/felix/gogo/runtime/Closure.java?view=markup
> And in this case Karaf tries to run command cluster:group-create before 
> cellar is successfully installed.
> How can I run cluster:group-create in Karaf after Cellar feature will be 
> successfully installed?



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

[jira] [Work started] (KARAF-4763) Upgrade to PaxCdi 1.0.0

[Guillaume Nodet (JIRA)]

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

Work on KARAF-4763 started by Guillaume Nodet.
--
> Upgrade to PaxCdi 1.0.0
> ---
>
> Key: KARAF-4763
> URL: https://issues.apache.org/jira/browse/KARAF-4763
> Project: Karaf
>  Issue Type: Dependency upgrade
>Reporter: Guillaume Nodet
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>




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

[jira] [Created] (KARAF-4763) Upgrade to PaxCdi 1.0.0

[Guillaume Nodet (JIRA)]

Guillaume Nodet created KARAF-4763:
--

 Summary: Upgrade to PaxCdi 1.0.0
 Key: KARAF-4763
 URL: https://issues.apache.org/jira/browse/KARAF-4763
 Project: Karaf
  Issue Type: Dependency upgrade
Reporter: Guillaume Nodet
Assignee: Guillaume Nodet
 Fix For: 4.1.0






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

[jira] [Assigned] (KARAF-4762) Upgrade to PaxUrl 2.5.0

[Grzegorz Grzybek (JIRA)]

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

Grzegorz Grzybek reassigned KARAF-4762:
---

Assignee: Grzegorz Grzybek  (was: Jonathan Anstey)

> Upgrade to PaxUrl 2.5.0
> ---
>
> Key: KARAF-4762
> URL: https://issues.apache.org/jira/browse/KARAF-4762
> Project: Karaf
>  Issue Type: Dependency upgrade
>Reporter: Guillaume Nodet
>Assignee: Grzegorz Grzybek
> Fix For: 4.1.0
>
>




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

[jira] [Assigned] (KARAF-3172) boot features with mvn: handler can't be resolved when maven repo is a https url

[Grzegorz Grzybek (JIRA)]

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

Grzegorz Grzybek reassigned KARAF-3172:
---

Assignee: Grzegorz Grzybek

> boot features with mvn: handler can't be resolved when maven repo is a https 
> url
> 
>
> Key: KARAF-3172
> URL: https://issues.apache.org/jira/browse/KARAF-3172
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 2.3.6
>Reporter: Daniel Haag
>Assignee: Grzegorz Grzybek
>  Labels: features, maven
>
> When specifying a https maven repo in the
> org.ops4j.pax.url.mvn.repositories
> karaf does only query the http maven repos for features on bootup:
> org.apache.karaf.features.cfg:featuresBoot
> On the Repository Site no https requests are seen and also the debug output 
> of karaf indicates only requests for the http repos:
> {code}
> 2014-08-20 14:53:43,423 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  260 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 | Collecting versions from repository 
> [file:/home/esb/.m2/repository/,releases=true,snapshots=true]
> 2014-08-20 14:53:43,423 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  378 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 |   Resolving exact version
> 2014-08-20 14:53:43,424 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  260 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 | Collecting versions from repository 
> [https://mvnrepo.uibk.ac.at/artifactory/repo1/,releases=true,snapshots=false]
> 2014-08-20 14:53:43,424 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  378 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 |   Resolving exact version
> 2014-08-20 14:53:43,424 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  260 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 | Collecting versions from repository 
> [https://mvnrepo.uibk.ac.at/artifactory/esb-repos/,releases=true,snapshots=false]
> 2014-08-20 14:53:43,424 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  378 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 |   Resolving exact version
> 2014-08-20 14:53:43,425 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  260 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 | Collecting versions from repository 
> [https://svn.apache.org/repos/asf/servicemix/m2-repo/,releases=true,snapshots=false]
> 2014-08-20 14:53:43,425 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  378 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 |   Resolving exact version
> 2014-08-20 14:53:43,425 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  260 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 | Collecting versions from repository 
> [http://repository.springsource.com/maven/bundles/release/,releases=true,snapshots=false]
> 2014-08-20 14:53:43,426 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  378 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 |   Resolving exact version
> 2014-08-20 14:53:43,426 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  260 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 | Collecting versions from repository 
> [http://repository.springsource.com/maven/bundles/external/,releases=true,snapshots=false]
> 2014-08-20 14:53:43,426 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  378 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 |   Resolving exact version
> 2014-08-20 14:53:43,427 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  260 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 | Collecting versions from repository 
> [https://oss.sonatype.org/content/repositories/releases/,releases=true,snapshots=false]
> 2014-08-20 14:53:43,427 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  378 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 |   Resolving exact version
> 2014-08-20 14:53:43,427 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  190 | 1 - org.ops4j.pax.url.mvn - 
> 1.3.7 |   Could not download [Version [2.12.0] from URL 
> [file:/home/esb/.m2/repository/org/apache/camel/karaf/apache-camel/2.12.0/apache-camel-2.12.0-features.xml]]
> 2014-08-20 14:53:43,435 | DEBUG | FelixStartLevel  | Connection   
> | .pax.url.mvn.internal.Connection  190 | 1 - 

[jira] [Assigned] (KARAF-4719) Aether cannot to resolve m2 repositories after adjustments in org.ops4j.pax.url.mvn.cfg

[Grzegorz Grzybek (JIRA)]

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

Grzegorz Grzybek reassigned KARAF-4719:
---

Assignee: Grzegorz Grzybek

> Aether cannot to resolve m2 repositories after adjustments in 
> org.ops4j.pax.url.mvn.cfg
> ---
>
> Key: KARAF-4719
> URL: https://issues.apache.org/jira/browse/KARAF-4719
> Project: Karaf
>  Issue Type: Bug
>Affects Versions: 4.0.5, 4.0.6
>Reporter: Antonio Maria
>Assignee: Grzegorz Grzybek
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Start levels for pax-url-aether(5) and org.apache.felix.configadmin(10) are 
> defined in framework xml feature. Therefore pax url aether is configured 
> after org.ops4j.pax.url.mvn.local properties are loaded.
> This causes that in case of assemble Karaf using offline repository, by 
> adjusting:
> {code}
> org.ops4j.pax.url.mvn.localRepository=${karaf.home}/${karaf.default.repository}
> {code}
> Don't really work, because is too late for aether, that is already started.
> Eventually causes an error when karaf starts. The error is quite random, and 
> happens quite often when karaf starts using the wrapper as a windows services.
> By decreasing the aether starts level to any value after felix configadmin, 
> it improves the bootstrap robustness when creating offline distribution.



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

[jira] [Assigned] (KARAF-4513) pax-url-aether fails to resolve test-jar artifacts from local repo

[Grzegorz Grzybek (JIRA)]

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

Grzegorz Grzybek reassigned KARAF-4513:
---

Assignee: Grzegorz Grzybek

> pax-url-aether fails to resolve test-jar artifacts from local repo
> --
>
> Key: KARAF-4513
> URL: https://issues.apache.org/jira/browse/KARAF-4513
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-core
>Affects Versions: 4.0.5
> Environment: JDK 1.8, Win7 x64
>Reporter: Felix Wassmer
>Assignee: Grzegorz Grzybek
>
> Since the version upgrade to pax-url-aether 2.4.7 of KARAF-4477 
> Karaf fails to locate maven dependencies of the type test-jar from the local 
> repository and tries to fetch it from central.
> Every other type is properly resolved from the local repo.
> Current use case:
> Pax exam test has a dependency on the artifact
> {code:xml}
> 
> org.broken.test
> broken-test-util
> 1.0.0.POM-TEST
> test-jar
> test
> 
> {code}
> which causes following execption on startup:
> {noformat}
> 2016-04-29T14:26:45,864 | WARN  | pool-11-thread-7 | 5   - 
> 4j.pax.logging.pax-logging-api - 1.8.5  | AetherBasedResolver 
>  | Error resolving artifact 
> org.broken.test:broken-test-util:jar:tests:1.0.0.POM-TEST:Could not find 
> artifact org.broken.test:broken-test-util:jar:tests:1.0.0.POM-TEST in central 
> (http://repo1.maven.org/maven2/)
> shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not 
> find artifact org.broken.test:broken-test-util:jar:tests:1.0.0.POM-TEST in 
> central (http://repo1.maven.org/maven2/)
>   at 
> shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
>  [4:org.ops4j.pax.url.mvn:2.4.7]
>   at 
> shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
>  [4:org.ops4j.pax.url.mvn:2.4.7]
>   at 
> shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
>  [4:org.ops4j.pax.url.mvn:2.4.7]
>   at 
> shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:294)
>  [4:org.ops4j.pax.url.mvn:2.4.7]
>   at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:650)
>  [4:org.ops4j.pax.url.mvn:2.4.7]
>   at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:598)
>  [4:org.ops4j.pax.url.mvn:2.4.7]
>   at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:576)
>  [4:org.ops4j.pax.url.mvn:2.4.7]
>   at 
> org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:550)
>  [4:org.ops4j.pax.url.mvn:2.4.7]
>   at 
> org.apache.karaf.features.internal.download.impl.MavenDownloadTask.download(MavenDownloadTask.java:34)
>  [9:org.apache.karaf.features.core:4.0.5]
>   at 
> org.apache.karaf.features.internal.download.impl.AbstractRetryableDownloadTask.run(AbstractRetryableDownloadTask.java:58)
>  [9:org.apache.karaf.features.core:4.0.5]
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:?]
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>  [?:?]
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>  [?:?]
>   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) [?:?]
> Caused by: shaded.org.eclipse.aether.transfer.ArtifactNotFoundException: 
> Could not find artifact 
> org.broken.test:broken-test-util:jar:tests:1.0.0.POM-TEST in central 
> (http://repo1.maven.org/maven2/)
>   at 
> shaded.org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:39)
>  ~[?:?]
>   at 
> shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355)
>  ~[?:?]
>   at 
> shaded.org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
>  ~[?:?]
>   at 
> shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:581)
>  ~[?:?]
>   at 
> shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:249)
>  ~[?:?]
>   at 
> 

[jira] [Updated] (KARAF-4100) [karaf-3.0.x] Error resolving artifact of feature due to org.ops4j.pax.url.mvn.cfg not loaded yet

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet updated KARAF-4100:
---
Fix Version/s: 4.1.0

> [karaf-3.0.x] Error resolving artifact of feature due to 
> org.ops4j.pax.url.mvn.cfg not loaded yet
> -
>
> Key: KARAF-4100
> URL: https://issues.apache.org/jira/browse/KARAF-4100
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-feature
>Affects Versions: 3.0.5
> Environment: Karaf 3.0.4, Windows 7
>Reporter: Jerry Meng
> Fix For: 4.1.0
>
>
> I set the mvn repository to the karaf_home/system directory in 
> org.ops4j.pax.url.mvn.cfg.
> However, I found there is a chance that Karaf was trying to access the 
> Internet and threw an exception since it's in a closed environment.
> {code}
> Error resolving artifact 
> org.apache.karaf.features:enterprise:xml:features:3.0.4: Could not transfer 
> artifact org.apache.karaf.features:enterprise:xml:features:3.0.4 from/to  
> (http://mvn.mycompany.net/content/groups/public): Not authorized , 
> ReasonPhrase:Unauthorized.
> {code}
> Root Cause
> =
> Through further tracking, the root cause may happen in 
> org.ops4j.pax.url.mvn.internal.Activator (pax-url-aether). The pax url fails 
> to load org.ops4j.pax.url.mvn.cfg before Karaf connects the feature url. 
> Therefore Karaf ignores my settings in the configuration file but tries to 
> access default remote repository. Here are some logs to describe the 
> situation...
> {code}
> 1. activator.updated.dictionary: null
> 2. updated directory from safeRegisterService: null
> 3. activator.openConnection: 
> mvn:org.apache.karaf.features/enterprise/3.0.4/xml/features
> 4. Unable to add features repository 
> mvn:org.apache.karaf.features/enterprise/3.0.4/xml/features at startup
> 5. updated directory from safeRegisterService: 
> {felix.fileinstall.filename={file:/D:/karaf/etc/org.ops4j.pax.url.mvn.cfg... }
> 6. activator.updated.dictionary: 
> {felix.fileinstall.filename={file:/D:/karaf/etc/org.ops4j.pax.url.mvn.cfg... }
> {code}
> Workaround
> =
> I'm not sure if I should call this a bug, but in my case I can assume 
> org.ops4j.pax.url.mvn.cfg is existent definitely.
> Therefore, I make Activator.openConnection to wait if the Dictionary is not 
> set.
> Then invoke notifyAll in Activator.updated after receiving an non-null 
> Dictionary.



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

[jira] [Resolved] (KARAF-4762) Upgrade to PaxUrl 2.5.0

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet resolved KARAF-4762.

Resolution: Fixed

https://git1-us-west.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=0628a170e4fd92fc770224f8295037bcaa5288ae

> Upgrade to PaxUrl 2.5.0
> ---
>
> Key: KARAF-4762
> URL: https://issues.apache.org/jira/browse/KARAF-4762
> Project: Karaf
>  Issue Type: Dependency upgrade
>Reporter: Guillaume Nodet
>Assignee: Jonathan Anstey
> Fix For: 4.1.0
>
>




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

[jira] [Created] (KARAF-4762) Upgrade to PaxUrl 2.5.0

[Guillaume Nodet (JIRA)]

Guillaume Nodet created KARAF-4762:
--

 Summary: Upgrade to PaxUrl 2.5.0
 Key: KARAF-4762
 URL: https://issues.apache.org/jira/browse/KARAF-4762
 Project: Karaf
  Issue Type: Dependency upgrade
Reporter: Guillaume Nodet
Assignee: Jonathan Anstey
 Fix For: 4.1.0






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

[jira] [Updated] (KARAF-397) Allow completion of non Karaf based osgi commands

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet updated KARAF-397:
--
Issue Type: New Feature  (was: Improvement)

> Allow completion of non Karaf based osgi commands
> -
>
> Key: KARAF-397
> URL: https://issues.apache.org/jira/browse/KARAF-397
> Project: Karaf
>  Issue Type: New Feature
>  Components: karaf-shell
>Reporter: Guillaume Nodet
> Fix For: 4.1.0
>
>




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

[jira] [Updated] (KARAF-397) Allow completion of non Karaf based osgi commands

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet updated KARAF-397:
--
Fix Version/s: 4.1.0

> Allow completion of non Karaf based osgi commands
> -
>
> Key: KARAF-397
> URL: https://issues.apache.org/jira/browse/KARAF-397
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-shell
>Reporter: Guillaume Nodet
> Fix For: 4.1.0
>
>




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

[jira] [Assigned] (KARAF-2454) Portable way to make custom shell commands (without inheriting from OsgiCommandSupport)

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet reassigned KARAF-2454:
--

Assignee: Guillaume Nodet

> Portable way to make custom shell commands (without inheriting from 
> OsgiCommandSupport)
> ---
>
> Key: KARAF-2454
> URL: https://issues.apache.org/jira/browse/KARAF-2454
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 2.3.2
> Environment: All
>Reporter: Morten Christensen
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> I would like to be able to create osgi shell commands that work across karaf 
> and standard osgi implementations like felix, eclipse (both using gogo). When 
> deployed in karaf, the shell commands should support completion and the other 
> karaf specific features and when deployed in plain felix just work as in the 
> standard. Currently, karaf makes this difficult as commands must extend from 
> karaf specific OsgiCommandSupport class. I would like a way to support karaf 
> using some karaf specific configuration outside the command classes that 
> should use standard OSGI stuff only. 



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

[jira] [Updated] (KARAF-2454) Portable way to make custom shell commands (without inheriting from OsgiCommandSupport)

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet updated KARAF-2454:
---
Fix Version/s: 4.1.0

> Portable way to make custom shell commands (without inheriting from 
> OsgiCommandSupport)
> ---
>
> Key: KARAF-2454
> URL: https://issues.apache.org/jira/browse/KARAF-2454
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 2.3.2
> Environment: All
>Reporter: Morten Christensen
> Fix For: 4.1.0
>
>
> I would like to be able to create osgi shell commands that work across karaf 
> and standard osgi implementations like felix, eclipse (both using gogo). When 
> deployed in karaf, the shell commands should support completion and the other 
> karaf specific features and when deployed in plain felix just work as in the 
> standard. Currently, karaf makes this difficult as commands must extend from 
> karaf specific OsgiCommandSupport class. I would like a way to support karaf 
> using some karaf specific configuration outside the command classes that 
> should use standard OSGI stuff only. 



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

[jira] [Closed] (KARAF-4665) Skip Maven itest when using -DskipTests

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet closed KARAF-4665.
--
   Resolution: Duplicate
 Assignee: Guillaume Nodet  (was: Jean-Baptiste Onofré)
Fix Version/s: (was: 4.0.8)
   (was: 4.1.0)

> Skip Maven itest when using -DskipTests
> ---
>
> Key: KARAF-4665
> URL: https://issues.apache.org/jira/browse/KARAF-4665
> Project: Karaf
>  Issue Type: Improvement
>  Components: karaf-tooling
>Reporter: Jean-Baptiste Onofré
>Assignee: Guillaume Nodet
>
> When using {{-DskipTests}} to skip unit tests, the Maven integration test in 
> tooling (using Maven invoker) are executed anyway (slowing down the build). I 
> think it make sense to "link" Maven itest with {{-DskipTests}} usage.



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

[jira] [Assigned] (KARAF-4680) Karaf shell console (jline 3) leaves the terminal in "bad" state

[Guillaume Nodet (JIRA)]

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

Guillaume Nodet reassigned KARAF-4680:
--

Assignee: Guillaume Nodet  (was: Jean-Baptiste Onofré)

> Karaf shell console (jline 3) leaves the terminal in "bad" state
> 
>
> Key: KARAF-4680
> URL: https://issues.apache.org/jira/browse/KARAF-4680
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 4.1.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Guillaume Nodet
> Fix For: 4.1.0
>
>
> Karaf 4.1.x is now using JLine 3. The Karaf shell works pretty well.
> However, when stopping Karaf 4.1.x (using CTRL-D), the Linux terminal is left 
> in a bad state (input and output stream are "lost").
> We have to do a {{reset}} to have a terminal back to "normal".



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

[jira] [Created] (KARAF-4761) EnterpriseFeaturesTest installTransaction130Feature test fails during full build

[Andrea Cosentino (JIRA)]

Andrea Cosentino created KARAF-4761:
---

 Summary: EnterpriseFeaturesTest installTransaction130Feature test 
fails during full build
 Key: KARAF-4761
 URL: https://issues.apache.org/jira/browse/KARAF-4761
 Project: Karaf
  Issue Type: Test
  Components: karaf-test
Reporter: Andrea Cosentino
Priority: Minor


Tests run: 18, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.153 sec <<< 
FAILURE! - in org.apache.karaf.itests.features.EnterpriseFeaturesTest
installTransaction130Feature(org.apache.karaf.itests.features.EnterpriseFeaturesTest)
  Time elapsed: 0.024 sec  <<< ERROR!
java.lang.IllegalArgumentException: No matching features for transaction/1.3.0
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:908)
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:827)
at 
org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:812)
at 
org.apache.karaf.itests.KarafTestSupport.installAssertAndUninstallFeatures(KarafTestSupport.java:568)
at 
org.apache.karaf.itests.KarafTestSupport.installAssertAndUninstallFeature(KarafTestSupport.java:561)
at 
org.apache.karaf.itests.features.EnterpriseFeaturesTest.installTransaction130Feature(EnterpriseFeaturesTest.java:38)




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

[jira] [Updated] (KARAF-4761) EnterpriseFeaturesTest installTransaction130Feature test fails during full build

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino updated KARAF-4761:

Affects Version/s: 4.1.0

> EnterpriseFeaturesTest installTransaction130Feature test fails during full 
> build
> 
>
> Key: KARAF-4761
> URL: https://issues.apache.org/jira/browse/KARAF-4761
> Project: Karaf
>  Issue Type: Test
>  Components: karaf-test
>Affects Versions: 4.1.0
>Reporter: Andrea Cosentino
>Priority: Minor
>
> Tests run: 18, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.153 sec 
> <<< FAILURE! - in org.apache.karaf.itests.features.EnterpriseFeaturesTest
> installTransaction130Feature(org.apache.karaf.itests.features.EnterpriseFeaturesTest)
>   Time elapsed: 0.024 sec  <<< ERROR!
> java.lang.IllegalArgumentException: No matching features for transaction/1.3.0
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:908)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:827)
>   at 
> org.apache.karaf.features.internal.service.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:812)
>   at 
> org.apache.karaf.itests.KarafTestSupport.installAssertAndUninstallFeatures(KarafTestSupport.java:568)
>   at 
> org.apache.karaf.itests.KarafTestSupport.installAssertAndUninstallFeature(KarafTestSupport.java:561)
>   at 
> org.apache.karaf.itests.features.EnterpriseFeaturesTest.installTransaction130Feature(EnterpriseFeaturesTest.java:38)



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

[jira] [Resolved] (KARAF-4377) Refer to hibernate-validator feature repository instead of using the current one

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino resolved KARAF-4377.
-
Resolution: Fixed

> Refer to hibernate-validator feature repository instead of using the current 
> one 
> -
>
> Key: KARAF-4377
> URL: https://issues.apache.org/jira/browse/KARAF-4377
> Project: Karaf
>  Issue Type: Task
>  Components: karaf-feature
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.1.0
>
>
> https://github.com/hibernate/hibernate-validator/blob/5.2.4.Final/osgi/karaf-features/src/main/features/features.xml
> Since Hibernate-validator has his own feature repository, we can use it and 
> remove our feature.



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

[jira] [Commented] (KARAF-4377) Refer to hibernate-validator feature repository instead of using the current one

[Andrea Cosentino (JIRA)]

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

Andrea Cosentino commented on KARAF-4377:
-

Hibernate-validator 5.3.0.Final is out. I'm gonna push.

> Refer to hibernate-validator feature repository instead of using the current 
> one 
> -
>
> Key: KARAF-4377
> URL: https://issues.apache.org/jira/browse/KARAF-4377
> Project: Karaf
>  Issue Type: Task
>  Components: karaf-feature
>Reporter: Andrea Cosentino
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 4.1.0
>
>
> https://github.com/hibernate/hibernate-validator/blob/5.2.4.Final/osgi/karaf-features/src/main/features/features.xml
> Since Hibernate-validator has his own feature repository, we can use it and 
> remove our feature.



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