[jira] [Created] (KARAF-3480) jndi:contexts command doesn't display sub-context
Jean-Baptiste Onofré created KARAF-3480: --- Summary: jndi:contexts command doesn't display sub-context Key: KARAF-3480 URL: https://issues.apache.org/jira/browse/KARAF-3480 Project: Karaf Issue Type: Bug Components: karaf-jndi Affects Versions: 3.0.2, 3.0.3 Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 3.0.4 The jndi:contexts command doesn't display anything, even whe a sub-context has been created using jndi:create or an alias has been done with jndi:bind or jndi:alias. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2508) make osgi:find-class a more useful command
[ https://issues.apache.org/jira/browse/KARAF-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2508: Fix Version/s: (was: 3.0.3) 3.0.4 > make osgi:find-class a more useful command > -- > > Key: KARAF-2508 > URL: https://issues.apache.org/jira/browse/KARAF-2508 > Project: Karaf > Issue Type: Improvement > Components: karaf-shell >Affects Versions: 2.3.3 >Reporter: Amichai Rothman >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > I recently had to track down which bundle contains a certain class, and found > the find-class command wanting. A few simple improvements would make it much > more useful: > 1. Add an --exact/-e option which doesn't automatically add asterisks at both > ends of the string. In my case I was looking for the javax.jms.Connection > class, and since the search is only on the last part of the name, this > returned all classes in all packages which have the word Connection in their > name, which added up to hundreds of results. with --exact I could look for > what I want exactly, or choose to add asterisks at one or both ends > explicitly in the search string if I wanted to. > 2. Add a --local/-l option which adds BundleWiring.LISTRESOURCES_LOCAL to the > listResources method call bitmask. With the current implementation, it > returns both bundles containing the given class name and classes that import > it from other bundles, which is useful in some cases. But with the --local > option it could show only the bundles that actually contain the class > (whether exported or not, unlike the exports command), which is far more > useful in tracking down some classloading issues. > 3. Add the bundle ID (at least) on the beginning of every printed line. This > makes it amenable to grepping (without it a grep loses all bundle > information, which is the whole point of using this command). > 4. As a somewhat more complex alternative to #3, it would be nice if you > could specify a fully qualified class name and not only the last part of the > name. The command can split the search string around periods, pass the last > part to listResources, then internally grep/match the full name. That would > make it truly flexible in finding classes. Asterisks would have to be treated > accordingly. > I think adding these options (#1-#3 are trivial implementations), or at least > some of them, would make the command extremely useful when performing > classloading diagnosis. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2468) karaf-maven-plugin to support creation of partialbundlelists for sling launchpad
[ https://issues.apache.org/jira/browse/KARAF-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2468: Fix Version/s: (was: 3.0.3) 3.0.4 > karaf-maven-plugin to support creation of partialbundlelists for sling > launchpad > > > Key: KARAF-2468 > URL: https://issues.apache.org/jira/browse/KARAF-2468 > Project: Karaf > Issue Type: Improvement > Components: karaf-tooling >Reporter: Reto Gmür >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > Attachments: karaf-maven-plugin.patch > > > The sling launchpad maven plugin > (http://sling.apache.org/documentation/development/maven-launchpad-plugin.html) > supports the use partialbundlelists to group together related bundles. While > with the sling launchpad plugin one can create both partialbundlelists and > karaf features the flexibility for creating karaf features is somehow limited. > So it would be great to also provide the ability in the karaf-maven-plugin to > create partialbundlelist for sling. That is for users who primarily want to > create a karaf features to also have the possibility to server sling > launchpad using projects without having to duplicate the list of bundles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-2466) make it easy to access environment variables inside karaf configuration properties files - via ${ENV.foo}?
[
https://issues.apache.org/jira/browse/KARAF-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293110#comment-14293110
]
Jean-Baptiste Onofré commented on KARAF-2466:
-
AFAIR, we did some improvements about that. I have to double check the syntax
and update the documentation. I will do that for 3.0.4.
> make it easy to access environment variables inside karaf configuration
> properties files - via ${ENV.foo}?
> --
>
> Key: KARAF-2466
> URL: https://issues.apache.org/jira/browse/KARAF-2466
> Project: Karaf
> Issue Type: Improvement
>Reporter: james strachan
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 2.4.2, 3.0.4
>
>
> when using karaf in clouds & PaaS infrastructures like OpenShift, Docker,
> OpenStack et al; its common to use environment variables to pass in
> environment specific values; then keep a single disk image. It would be nice
> if there was an easy way to reference environment variables similar to the
> ${foo.bar} syntax for accessing system properties.
> Maybe karaf should support some kind of environment variable expansion like
> {code}
> # define a property based on an env var
> foo = ${ENV.nameOfEnvVar}
> # e.g. here's the host name
> host = ${ENV.HOSTNAME}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2495) reverse lookup of feature by bundle
[ https://issues.apache.org/jira/browse/KARAF-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2495: Fix Version/s: (was: 3.0.3) 3.0.4 > reverse lookup of feature by bundle > --- > > Key: KARAF-2495 > URL: https://issues.apache.org/jira/browse/KARAF-2495 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Affects Versions: 2.3.2 >Reporter: Jason Reilly >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > Lookup feature from bundle information. Where did a particular bundle come > from? Similar to how "features:info " lists the bundles, but the > reverse. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2466) make it easy to access environment variables inside karaf configuration properties files - via ${ENV.foo}?
[
https://issues.apache.org/jira/browse/KARAF-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2466:
Fix Version/s: (was: 3.0.3)
3.0.4
> make it easy to access environment variables inside karaf configuration
> properties files - via ${ENV.foo}?
> --
>
> Key: KARAF-2466
> URL: https://issues.apache.org/jira/browse/KARAF-2466
> Project: Karaf
> Issue Type: Improvement
>Reporter: james strachan
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 2.4.2, 3.0.4
>
>
> when using karaf in clouds & PaaS infrastructures like OpenShift, Docker,
> OpenStack et al; its common to use environment variables to pass in
> environment specific values; then keep a single disk image. It would be nice
> if there was an easy way to reference environment variables similar to the
> ${foo.bar} syntax for accessing system properties.
> Maybe karaf should support some kind of environment variable expansion like
> {code}
> # define a property based on an env var
> foo = ${ENV.nameOfEnvVar}
> # e.g. here's the host name
> host = ${ENV.HOSTNAME}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2382) Add a command to show bundles with split packages
[ https://issues.apache.org/jira/browse/KARAF-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2382: Fix Version/s: (was: 3.0.3) 3.0.4 > Add a command to show bundles with split packages > - > > Key: KARAF-2382 > URL: https://issues.apache.org/jira/browse/KARAF-2382 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Reporter: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2456) Shutdown is stuck after wrapper:install
[ https://issues.apache.org/jira/browse/KARAF-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2456: Fix Version/s: (was: 3.0.3) 3.0.4 > Shutdown is stuck after wrapper:install > --- > > Key: KARAF-2456 > URL: https://issues.apache.org/jira/browse/KARAF-2456 > Project: Karaf > Issue Type: Bug > Components: karaf-os-integration >Affects Versions: 2.3.2, 2.4.0, 3.0.0.RC1, 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.3.10, 2.4.2, 3.0.4 > > > After installing the wrapper feature (feature:install wrapper), and install > the wrapper (wrapper:install), CTRL-D binding keys stuck to shutdown Karaf: > ... > To uninstall the service : > $ rm /etc/init.d/karaf-service > karaf@root()> ^D -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2392) Remove unneeded manifest headers, add service import definitions for blueprint namespaces
[ https://issues.apache.org/jira/browse/KARAF-2392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2392: Fix Version/s: (was: 3.0.3) 3.0.4 > Remove unneeded manifest headers, add service import definitions for > blueprint namespaces > - > > Key: KARAF-2392 > URL: https://issues.apache.org/jira/browse/KARAF-2392 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.3.2 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.0.0, 2.4.2, 3.0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2140) Add an explicit allowEmptyPasswords to the LDAPLoginModule defaulting to false
[ https://issues.apache.org/jira/browse/KARAF-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2140: Fix Version/s: (was: 3.0.3) 3.0.4 > Add an explicit allowEmptyPasswords to the LDAPLoginModule defaulting to false > -- > > Key: KARAF-2140 > URL: https://issues.apache.org/jira/browse/KARAF-2140 > Project: Karaf > Issue Type: Improvement > Components: karaf-core >Reporter: Guillaume Nodet >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > LDAP servers usually allow anonymous identification by sending an empty > passwords. The roles checks should guard against this, but a specific option > would close any risk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2121) Add Support For Displaying Gogo Commands in Karaf Shell Help
[ https://issues.apache.org/jira/browse/KARAF-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2121: Fix Version/s: (was: 3.0.3) 3.0.4 > Add Support For Displaying Gogo Commands in Karaf Shell Help > > > Key: KARAF-2121 > URL: https://issues.apache.org/jira/browse/KARAF-2121 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Affects Versions: 2.3.0 >Reporter: Gareth Collins >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 2.4.2, 3.0.4 > > Attachments: KARAF-2121.patch > > > Discussion on this originated in this thread: > http://karaf.922171.n3.nabble.com/Gogo-vs-Karaf-Commands-td4027219.html > Whist Gogo commands run in Karaf, these commands do not show up in the Karaf > shell help. For Karaf users potentially needing to target multiple > environments, it would be nice if Karaf could also display help for these > Gogo commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1972) karaf-maven-plugin should respect scope
[
https://issues.apache.org/jira/browse/KARAF-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-1972:
Fix Version/s: (was: 3.0.3)
3.0.4
> karaf-maven-plugin should respect scope
> ---
>
> Key: KARAF-1972
> URL: https://issues.apache.org/jira/browse/KARAF-1972
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Affects Versions: 3.0.0.RC1
>Reporter: Andrei Pozolotin
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.4
>
> Attachments: 0001-Fixing-the-scope-handling.patch, KARAF-1972.patch
>
>
> PROBLEM:
> currently, in project with dependencies such as these:
> {code}
>
> org.osgi
> org.osgi.core
> provided
>
>
> org.osgi
> org.osgi.compendium
> provided
>
> {code}
> karaf-maven-plugin with invocation like this:
> {code}
>
>
>
> org.apache.karaf.tooling
> karaf-maven-plugin
> 3.0.0-SNAPSHOT
>
>
> generate-descriptor
> package
>
>
> features-generate-descriptor
>
>
>
> auto
>
> 90
>
> ./target/${project.artifactId}-${project.version}-features.xml
>
>
>
>
>
>
> {code}
> will produce features.xml with entries:
> {code}
> mvn:org.osgi/org.osgi.core/4.3.0
> start-level="90">mvn:org.osgi/org.osgi.compendium/4.2.0
> {code}
> which is not as expected. scope==provided should not show up there.
> SOLUTION:
> instead, karaf-maven-plugin should respect scope;
> I suggest to add karaf-maven-plugin config parameters such as:
> {code}
>
>compile
>
> {code}
> or
> {code}
>
>provided
>runtime
>test
>
> {code}
> IMPACT:
> current plugin behavior forces to create a separate maven
> project to generate features.xml, since scope==provided
> is in fact excluded from transitive dependencies in that case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2011) dev:watch looks in an incorrect local maven repository
[ https://issues.apache.org/jira/browse/KARAF-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2011: Fix Version/s: (was: 3.0.3) 3.0.4 > dev:watch looks in an incorrect local maven repository > -- > > Key: KARAF-2011 > URL: https://issues.apache.org/jira/browse/KARAF-2011 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 2.2.9, 2.3.0 >Reporter: Bengt Rodehav >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > If a non-default maven repository is used (by setting the "localRepository" > property in maven's settings.xml), then dev:watch does not work. It seems > like dev:watch does not consider the "localRepository" setting when looking > for a bundle in maven. > Note that other parts of Karaf does take the "localRepository" setting into > account since installing features and using the "update" command works. > This has been discussed on the user mailing list: > http://karaf.922171.n3.nabble.com/dev-watch-problems-td4026725.html#a4026730 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3475) No refresh of bundles during feature install
[
https://issues.apache.org/jira/browse/KARAF-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292978#comment-14292978
]
Frank Diebolt commented on KARAF-3475:
--
Hi,
Sorry, I neither saw JIRA -3371 neither any commit fixing this issue in the
3.0.x branch...
I encountered the issue after deploying the webconsole feature (that must
deploy the pax-web-runtime bundle I guess) then later the war feature which
adds the pax-web-jsp bundle.
Since pax-web-jsp is deployed after pax-web-runtime, the JSP support isn't
working.
Indeed, JSP is an optional import of the runtime and must be available before
the runtime is resolved or the runtime must be refreshed. The karaf feature
installer seems to deal with it, since I can see a list of bundles to refresh
identified to have optional imports that have been updated at the end of the
feature install...
Miserably, the karaf feature announces a bundle refresh but actually does
nothing since only the 0 system bundle exports the FrameworkWiring service.
It's strange that this fix has such a side effect on IT tests :-(
Sorry, I won't be able to make additional tests before 3 weeks.
But it would be great to have this fix (same as JIRA-3371) in the 3.0.3 version.
BR
Frank
> No refresh of bundles during feature install
>
>
> Key: KARAF-3475
> URL: https://issues.apache.org/jira/browse/KARAF-3475
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 3.0.2
>Reporter: Frank Diebolt
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.4
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> Hi,
> I successfully tested the fix below :
> In the source file
> features/core/src/main/java/org/apache/karaf/features/internal/BundleManager.java
> protected void refreshPackages(Collection bundles) {
> final Object refreshLock = new Object();
> -FrameworkWiring wiring =
> bundleContext.getBundle().adapt(FrameworkWiring.class);
> +FrameworkWiring wiring =
> bundleContext.getBundle(0).adapt(FrameworkWiring.class);
> Currently wiring is always null, FrameworkWiring can be obtained on bundle 0
> only.
> BR
> Frank
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (KARAF-3457) Unable to install cxf in apache karaf 3.0.2
[ https://issues.apache.org/jira/browse/KARAF-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292942#comment-14292942 ] Dhinakaran commented on KARAF-3457: --- OK... thanks for your update. I will check it up with 3.1.0 version with fresh setup & installation and will update the status here. > Unable to install cxf in apache karaf 3.0.2 > --- > > Key: KARAF-3457 > URL: https://issues.apache.org/jira/browse/KARAF-3457 > Project: Karaf > Issue Type: Bug >Affects Versions: 3.0.2 > Environment: jdk 1.7.0_25 >Reporter: Dhinakaran >Priority: Blocker > Labels: Karaf > > I have karaf 3.0.2 up and running. I tried setting up rest services feature > into the container. The following command is been run, > feature:repo-add cxf 2.7.5 - successfully added > feature:install cxf > The above command started installing the below components... > Installing feature http 3.0.2 > Installing feature pax-http 3.1.2 > Installing feature standard-condition-webconsole_0_0_0 3.0.2 > Installing feature cxf 3.1.0-SNAPSHOT > Installing feature cxf-core 3.1.0-SNAPSHOT > Installing feature cxf-specs 3.1.0-SNAPSHOT > Installing feature cxf-jaxws 3.1.0-SNAPSHOT > Installing feature cxf-wsdl 3.1.0-SNAPSHOT > Installing feature cxf-databinding-jaxb 3.1.0-SNAPSHOT > Installing feature cxf-bindings-soap 3.1.0-SNAPSHOT > Installing feature cxf-http 3.1.0-SNAPSHOT > Installing feature cxf-jaxrs 3.1.0-SNAPSHOT > Installing feature cxf-databinding-aegis 3.1.0-SNAPSHOT > Installing feature cxf-databinding-xmlbeans 3.1.0-SNAPSHOT > Installing feature cxf-bindings-corba 3.1.0-SNAPSHOT > Installing feature cxf-bindings-coloc 3.1.0-SNAPSHOT > Installing feature cxf-bindings-object 3.1.0-SNAPSHOT > Installing feature cxf-transports-local 3.1.0-SNAPSHOT > Installing feature cxf-http-jetty 3.1.0-SNAPSHOT > Installing feature jetty 8.1.9.v20130131 > Installing feature cxf-transports-jms 3.1.0-SNAPSHOT > Installing feature cxf-transports-udp 3.1.0-SNAPSHOT > Installing feature cxf-xjc-runtime 3.1.0-SNAPSHOT > Installing feature cxf-jaxb 3.1.0-SNAPSHOT > Installing feature cxf-ws-security 3.1.0-SNAPSHOT > Installing feature cxf-ws-policy 3.1.0-SNAPSHOT > Installing feature wss4j 2.0.3-SNAPSHOT > Installing feature cxf-ws-addr 3.1.0-SNAPSHOT > Installing feature cxf-ws-rm 3.1.0-SNAPSHOT > Installing feature cxf-ws-mex 3.1.0-SNAPSHOT > Installing feature cxf-javascript 3.1.0-SNAPSHOT > Installing feature cxf-frontend-javascript 3.1.0-SNAPSHOT > Installing feature cxf-features-clustering 3.1.0-SNAPSHOT > Installing feature standard-condition-webconsole_0_0_0 3.0.2 > Adding the extensions from bundle org.apache.cxf.cxf-core (153) > [org.apache.cxf.phase.PhaseManager, > org.apache.cxf.workqueue.WorkQueueManager, > org.apache.cxf.buslifecycle.BusLifeCycleManager, > org.apache.cxf.endpoint.ServerRegistry, > org.apache.cxf.endpoint.EndpointResolverRegistry, > org.apache.cxf.headers.HeaderManager, > org.apache.cxf.service.factory.FactoryBeanListenerManager, > org.apache.cxf.endpoint.ServerLifeCycleManager, > org.apache.cxf.endpoint.ClientLifeCycleManager, > org.apache.cxf.resource.ResourceManager, > org.apache.cxf.catalog.OASISCatalogManager] > And then, I got the error... > Removing the extensions for bundle 153 > ERROR | l for user karaf | ShellUtil| 25 - > org.apache.karaf.shell.console - 3.0.2 | Exception caught while executing > command > java.lang.Exception: Could not start bundle > mvn:org.apache.cxf/cxf-core/3.1.0-SNAPSHOT in feature(s) > cxf-core-3.1.0-SNAPSHOT: Activator start error in bundle > org.apache.cxf.cxf-core [153]. > at > org.apache.karaf.features.internal.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:480) > at > org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:435) > at > org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:375) > at > org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:364) > at Proxy1a038244_414b_4a92_8f4b_e01546b1a943.installFeature(Unknown > Source) > at > org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:67) > at > org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:38) > at > org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)[25:org.apache.karaf.shell.console:3.0.2] > at > org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)[25:org.apache.karaf.shell.console:3.0.2] > at > org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)[25:org.apache.karaf.shell.console:3.0.2] >
[jira] [Updated] (KARAF-1952) Allow Karaf monitoring using host:port
[ https://issues.apache.org/jira/browse/KARAF-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1952: Fix Version/s: (was: 3.0.3) 3.0.4 > Allow Karaf monitoring using host:port > -- > > Key: KARAF-1952 > URL: https://issues.apache.org/jira/browse/KARAF-1952 > Project: Karaf > Issue Type: Improvement > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > Currently, to be able to monitore Karaf (for instance in jconsole), we have > to use the service URL looking like: > service:rmi:jmx:///://hostname:port/karaf-root > To simplify the monitoring, it would be great to support directly > hostname:port. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1729) Cannot uninstall bundle, bundle xx is invalid
[
https://issues.apache.org/jira/browse/KARAF-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-1729:
Priority: Critical (was: Major)
> Cannot uninstall bundle, bundle xx is invalid
> -
>
> Key: KARAF-1729
> URL: https://issues.apache.org/jira/browse/KARAF-1729
> Project: Karaf
> Issue Type: Bug
> Components: karaf-osgi
>Affects Versions: 3.0.0
>Reporter: Hendy Irawan
>Assignee: Jean-Baptiste Onofré
>Priority: Critical
> Fix For: 4.0.0, 3.0.4
>
> Attachments: karaf-invalid-bundle.tgz
>
>
> Karaf marks a bundle as installed and active, but I can't uninstall it, stop
> it.
> {code}
> karaf@root()> list -t 0 -s | grep pool
> [1295] [Active] [ 50] org.apache.commons.pool (1.6.0)
> karaf@root()> uninstall 1295
> Bundle 1295 is invalid
> No bundles specified.
> karaf@root()> uninstall 1295
> Bundle 1295 is invalid
> No bundles specified.
> karaf@root()> list -t 0 -s | grep pool
> [1295] [Active] [ 50] org.apache.commons.pool (1.6.0)
> karaf@root()> uninstall org.apache.commons.pool
> No bundles specified.
> karaf@root()> list -t 0 -s | grep pool
> [1295] [Active] [ 50] org.apache.commons.pool (1.6.0)
> karaf@root()> stop 1295
> Bundle 1295 is invalid
> No bundles specified.
> {code}
> Workaround: Delete folder karaf/data/cache/bundle1295
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-1729) Cannot uninstall bundle, bundle xx is invalid
[
https://issues.apache.org/jira/browse/KARAF-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-1729:
Fix Version/s: (was: 3.0.3)
3.0.4
> Cannot uninstall bundle, bundle xx is invalid
> -
>
> Key: KARAF-1729
> URL: https://issues.apache.org/jira/browse/KARAF-1729
> Project: Karaf
> Issue Type: Bug
> Components: karaf-osgi
>Affects Versions: 3.0.0
>Reporter: Hendy Irawan
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.4
>
> Attachments: karaf-invalid-bundle.tgz
>
>
> Karaf marks a bundle as installed and active, but I can't uninstall it, stop
> it.
> {code}
> karaf@root()> list -t 0 -s | grep pool
> [1295] [Active] [ 50] org.apache.commons.pool (1.6.0)
> karaf@root()> uninstall 1295
> Bundle 1295 is invalid
> No bundles specified.
> karaf@root()> uninstall 1295
> Bundle 1295 is invalid
> No bundles specified.
> karaf@root()> list -t 0 -s | grep pool
> [1295] [Active] [ 50] org.apache.commons.pool (1.6.0)
> karaf@root()> uninstall org.apache.commons.pool
> No bundles specified.
> karaf@root()> list -t 0 -s | grep pool
> [1295] [Active] [ 50] org.apache.commons.pool (1.6.0)
> karaf@root()> stop 1295
> Bundle 1295 is invalid
> No bundles specified.
> {code}
> Workaround: Delete folder karaf/data/cache/bundle1295
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-1886) Create transaction-jdbc and transaction-jms enterprise features
[ https://issues.apache.org/jira/browse/KARAF-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1886: Fix Version/s: (was: 3.0.3) 3.0.4 > Create transaction-jdbc and transaction-jms enterprise features > --- > > Key: KARAF-1886 > URL: https://issues.apache.org/jira/browse/KARAF-1886 > Project: Karaf > Issue Type: New Feature > Components: karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > Aries transaction now replaces the "wrappers" by jdbc and jms provider. It > makes sense to let the user choose the provider installing a given feature > (for JDBC or JMS). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1728) BundleException: Bundle installation rejected by hook. error when installing from features XML file
[
https://issues.apache.org/jira/browse/KARAF-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-1728:
Fix Version/s: (was: 3.0.3)
3.0.4
> BundleException: Bundle installation rejected by hook. error when installing
> from features XML file
> ---
>
> Key: KARAF-1728
> URL: https://issues.apache.org/jira/browse/KARAF-1728
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 3.0.0
>Reporter: Hendy Irawan
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.4
>
>
> Console:
> {code}
> karaf@root()> feature:install -v commerce-shell
> Installing feature commerce-shell 4.0.1-SNAPSHOT
> Installing feature commerce-core 4.0.1-SNAPSHOT
> Installing feature oss-deps 1.0.0
> Installing feature httpclient 4.2.1
> Installing feature jpa 1.0.0
> Installing feature xml-specs-api 1.9.0
> Installing feature soluvas-framework 1.0.0-SNAPSHOT
> Installing feature magja 1.0.3-SNAPSHOT
> Installing feature http 3.0.0-SNAPSHOT
> Installing feature apache-ldap-client 1.0.0-M12
> Installing feature drools 5.4.0
> Installing feature blueprints-neo4j 1.2
> Installing feature neo4j 1.7.2
> Installing bundle
> wrap:mvn:org.neo4j/neo4j-kernel/1.8.M07$Export-Package=org.neo4j.unsafe.batchinsert;neo4j-kernel;=split,*
> Installing bundle
> wrap:mvn:org.neo4j/neo4j-lucene-index/1.8.M07$Export-Package=org.neo4j.unsafe.batchinsert;neo4j-lucene-index;=split,*
> Installing bundle wrap:mvn:org.neo4j/neo4j-cypher/1.8.M07
> Installing bundle wrap:mvn:org.neo4j/neo4j-rest-graphdb/1.7
> Installing bundle wrap:mvn:com.tinkerpop.blueprints/blueprints-core/1.2
> Installing bundle wrap:mvn:com.tinkerpop.blueprints/blueprints-neo4j-graph/1.2
> Installing bundle wrap:mvn:com.tinkerpop/frames/0.7
> Installing feature soluvas-image-store 1.0.0-SNAPSHOT
> Installing bundle wrap:mvn:net.coobird/thumbnailator/0.4.1
> Installing bundle mvn:org.soluvas/soluvas-image-store/1.0.0-SNAPSHOT
> Installing feature soluvas-ldap 1.0.0-SNAPSHOT
> Installing bundle
> mvn:org.apache.geronimo.specs/geronimo-validation_1.0_spec/1.1
> Installing bundle
> wrap:mvn:org.picketlink.idm/picketlink-idm-common/1.5.0.Alpha02$Export-Package=*;version=1.5.0.Alpha02
> Installing bundle
> wrap:mvn:org.picketlink.idm/picketlink-idm-api/1.5.0.Alpha02$Export-Package=*;version=1.5.0.Alpha02
> Installing bundle mvn:org.soluvas/soluvas-ldap/1.0.0-SNAPSHOT
> Installing feature openjpa 2.2.0
> Installing feature jndi 1.0.0
> Found installed bundle: org.apache.aries.util [9]
> Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.api/1.0.0
> Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.core/1.0.0
> Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.rmi/1.0.0
> Installing bundle mvn:org.apache.aries.jndi/org.apache.aries.jndi.url/1.0.0
> Installing bundle
> mvn:org.apache.aries.jndi/org.apache.aries.jndi.legacy.support/1.0.0
> Installing feature transaction 1.0.0
> Installing bundle mvn:commons-pool/commons-pool/1.6
> Error executing command: Bundle installation rejected by hook.
> {code}
> Log and stack trace:
> {code}
> 2012-08-15 18:12:42,454 | INFO | Thread-6 | ShellUtil
> | 40 - org.apache.karaf.shell.console - 3.0.0.SNAPSHOT | Exception
> caught while executing command
> org.osgi.framework.BundleException: Bundle installation rejected by hook.
> at org.apache.felix.framework.Felix.installBundle(Felix.java:2872)
> at
> org.apache.felix.framework.BundleContextImpl.installBundle(BundleContextImpl.java:165)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installBundleIfNeeded(FeaturesServiceImpl.java:894)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:606)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatureDependency(FeaturesServiceImpl.java:657)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:600)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatureDependency(FeaturesServiceImpl.java:657)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.doInstallFeature(FeaturesServiceImpl.java:600)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:450)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:431)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:420)
> at Proxyd6c71027_7662_4a47_bbd6_ba300c8a7c7a.installFeature(U
[jira] [Updated] (KARAF-1618) Exception when restarting Karaf with shutdown -r . Can not delete jansi.dll
[ https://issues.apache.org/jira/browse/KARAF-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1618: Fix Version/s: (was: 3.0.3) 3.0.4 > Exception when restarting Karaf with shutdown -r . Can not delete jansi.dll > --- > > Key: KARAF-1618 > URL: https://issues.apache.org/jira/browse/KARAF-1618 > Project: Karaf > Issue Type: Bug >Reporter: Christian Schneider > Fix For: 4.0.0, 3.0.4 > > > karaf@root()> shutdown -r > Confirm: reboot instance root (yes/no): > karaf@root()> Could not launch framework: java.io.IOException: Unable to > delete file: > C:\java\apache-karaf-3.0.0-SNAPSHOT\data\cache\bundle37\version0.0\bundle.jar-lib\0\META-INF\native\windows32\jansi.dll > java.io.IOException: Unable to delete file: > C:\java\apache-karaf-3.0.0-SNAPSHOT\data\cache\bundle37\version0.0\bundle.jar-lib\0\META-INF\native\windows32\jansi.dll > at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:204) > at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) > at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) > at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) > at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) > at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) > at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) > at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) > at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) > at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) > at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) > at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) > at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) > at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) > at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) > at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) > at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) > at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) > at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) > at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) > at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) > at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) > at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) > at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) > at org.apache.karaf.main.util.Utils.forceDelete(Utils.java:196) > at org.apache.karaf.main.util.Utils.cleanDirectory(Utils.java:168) > at org.apache.karaf.main.util.Utils.deleteDirectory(Utils.java:135) > at > org.apache.karaf.main.ConfigProperties.(ConfigProperties.java:143) > at org.apache.karaf.main.Main.launch(Main.java:212) > at org.apache.karaf.main.Main.main(Main.java:169) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1583) karaf-maven-plugin ignores dependency on feature
[
https://issues.apache.org/jira/browse/KARAF-1583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-1583:
Fix Version/s: (was: 3.0.3)
3.0.4
> karaf-maven-plugin ignores dependency on feature
>
>
> Key: KARAF-1583
> URL: https://issues.apache.org/jira/browse/KARAF-1583
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Affects Versions: 3.0.0.RC1
>Reporter: Brian Topping
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.4
>
>
> When a project has a dependency on a feature, the dependency should be
> rendered in the features.xml generated by
> {{karaf-maven-plugin:features-generate-descriptor}} as a {{}}
> element.
> I thought I added this, but it must have gotten lost in the patches and will
> submit another patch after KARAF-1537 is applied.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-1381) Use a history file per instance when possible
[ https://issues.apache.org/jira/browse/KARAF-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1381: Fix Version/s: (was: 3.0.3) 3.0.4 > Use a history file per instance when possible > - > > Key: KARAF-1381 > URL: https://issues.apache.org/jira/browse/KARAF-1381 > Project: Karaf > Issue Type: New Feature > Components: karaf-core, karaf-shell >Reporter: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > Currently, all instances launched with the same system user share the same > history file ($USER/.karaf/history), so we got the commands runned on another > instance. > A workaround is to use -Dkaraf.history property to use a history file > specific to each instance. However, the user has to change the startup > configuration to add this property. > When the instances are clearly identified (root, foobar, other, etc), Karaf > could store the history file in a dedicated location by default, for instance: > $USER/.karaf/history.root > $USER/.karaf/history.foobar > $USER/.karaf/history.other -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1385) Be able to disable the default PropertiesLoginModule
[ https://issues.apache.org/jira/browse/KARAF-1385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1385: Fix Version/s: (was: 3.0.3) 3.0.4 > Be able to disable the default PropertiesLoginModule > > > Key: KARAF-1385 > URL: https://issues.apache.org/jira/browse/KARAF-1385 > Project: Karaf > Issue Type: Improvement > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > Currently, the default PropertiesLoginModule is configured in the > jaas.modules bundle (in the blueprint descriptor). > It means that an user can't disable this login module easily. > I propose to "isolate" the default PropertiesLoginModule configuration in a > dedicated bundle in order to be able to uninstall it easily if needed (and > replaced by another "config" bundle). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1333) Support for M2E workspace resolution via reference: protocol
[
https://issues.apache.org/jira/browse/KARAF-1333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-1333:
Fix Version/s: (was: 3.0.3)
3.0.4
> Support for M2E workspace resolution via reference: protocol
>
>
> Key: KARAF-1333
> URL: https://issues.apache.org/jira/browse/KARAF-1333
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core, karaf-tooling
>Affects Versions: 3.0.0
>Reporter: Tuomas Kiviaho
>Assignee: Jean-Baptiste Onofré
> Labels: m2e, reference, workspace
> Fix For: 4.0.0, 3.0.4
>
> Attachments: FeaturesServiceImpl.patch, maven-plugin.patch
>
>
> Eclipse M2E plugin provides a 'workspace resolution' mode where Maven
> projects in Eclipse workspace are provided as workspace repository which
> takes precedence over other repositories.
> This leads to situation where artifact file isn't necessarily yet - depending
> on Mavens current lifecycle phase - provided as .jar but instead as directory
> pointing to project's output directory.
> {code:xml}
> http://karaf.apache.org/xmlns/features/v1.0.0";
> name="example">
>
> mvn:com/example/dependency/1.0.0
> ...
> mvn:com/example/project/0.0.1-SNAPSHOT
> ...
>
>
> {code}
> The patches provided in this issue not only takes care of treating
> directories as exploded .jar files (common approach) but also provisions
> them with reference: protocol that most of the OSGi frameworks understand as
> direct filesystem references thus allowing exploded .jars to be installed.
> {code:xml}
> http://karaf.apache.org/xmlns/features/v1.0.0";
> name="example">
>
> mvn:com/example/dependency/1.0.0
> ...
> reference:file:/~/workspace/example-project/classes/
> ...
>
>
> {code}
> Without intermediate round-trip via OSGi framework's bundle cache the
> 'workspace resolution' mode now offers also hot code replacement.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-1379) Provide exit alias and improve shell:logout command
[ https://issues.apache.org/jira/browse/KARAF-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1379: Fix Version/s: (was: 3.0.3) 3.0.4 > Provide exit alias and improve shell:logout command > --- > > Key: KARAF-1379 > URL: https://issues.apache.org/jira/browse/KARAF-1379 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Affects Versions: 2.2.6 >Reporter: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > Currently, the shell:logout command allow to exit from Karaf shell. > The problem is that it kills the Karaf process (shell:logout is called with > CRTL-D). > shell:logout should not kill the main Karaf process (the shutdown command is > dedicated for that) and an exit alias to shell:logout could be interesting. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1128) Introduce -Dkaraf.bind.address property
[ https://issues.apache.org/jira/browse/KARAF-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1128: Fix Version/s: (was: 3.0.3) 3.0.4 > Introduce -Dkaraf.bind.address property > --- > > Key: KARAF-1128 > URL: https://issues.apache.org/jira/browse/KARAF-1128 > Project: Karaf > Issue Type: Improvement > Components: karaf-core, karaf-instance, karaf-webcontainer >Reporter: David Jencks > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > Lets allow people to configure which host the rmi Registry is exposed on. > Currently, Karaf binds network services (RMI registry, HTTP server, etc) on > all IP addresses (0.0.0.0 interface). > It could be really helpful to have a property to mention the bind address > (something like -Dkaraf.bind.address=192.168.1.1 for instance). > This property should be used by most of the bundle binding network services > (Karaf management bundle for the RMI registry/server, HTTP service wia Pax > Web, etc). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-971) Add support for version ranges in features descriptor element
[ https://issues.apache.org/jira/browse/KARAF-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-971: --- Fix Version/s: (was: 3.0.3) 3.0.4 > Add support for version ranges in features descriptor element > --- > > Key: KARAF-971 > URL: https://issues.apache.org/jira/browse/KARAF-971 > Project: Karaf > Issue Type: Improvement >Affects Versions: 2.2.4 >Reporter: Gert Vanthienen >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > > Some features include a element to refer to another feature > descriptor. For example: > http://search.maven.org/remotecontent?filepath=org/apache/camel/karaf/apache-camel/2.8.2/apache-camel-2.8.2-features.xml > contains a reference to the CXF features descriptor. > For referring to the cxf feature, it already uses a version range [2.4, 2.6) > and if you put the same version range on the repository element URL, it would > just get resolved by Pax Url Maven support. > It would be good if the features service would first check for a matching > features descriptor - if there's already a matching descriptor installed, it > could just use the existing and skip/ignore the repository resolution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-1047) feature:uninstall command may provide -r option
[ https://issues.apache.org/jira/browse/KARAF-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1047: Fix Version/s: (was: 3.0.3) 3.0.4 > feature:uninstall command may provide -r option > --- > > Key: KARAF-1047 > URL: https://issues.apache.org/jira/browse/KARAF-1047 > Project: Karaf > Issue Type: New Feature > Components: karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.2, 3.0.4 > > > The feature:uninstall command could support -r (--recursive) option to > uninstall all dependent features. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-969) Feature installer should not accept different features with equal names
[
https://issues.apache.org/jira/browse/KARAF-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-969:
---
Fix Version/s: (was: 3.0.3)
3.0.4
> Feature installer should not accept different features with equal names
> ---
>
> Key: KARAF-969
> URL: https://issues.apache.org/jira/browse/KARAF-969
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 2.2.2
>Reporter: Geert Schuring
> Labels: duplicate, features, name, namespaces
> Fix For: 4.0.0, 2.4.2, 3.0.4
>
>
> The feature installer should reject feature files that contain features with
> conflicting names. The installer currently allows this, while the install
> command cannot differentiate between two features with the same name.
> Maybe the concept of feature namespaces would be a good solution. The feature
> repository name could function as the namespace. The install command should
> then support something like this:
> {code}
> features:install :
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-639) Karaf Plug-in validate goal doesn't support various aspects of PAX MVN/URL
[ https://issues.apache.org/jira/browse/KARAF-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-639: --- Fix Version/s: (was: 3.0.3) 3.0.4 > Karaf Plug-in validate goal doesn't support various aspects of PAX MVN/URL > -- > > Key: KARAF-639 > URL: https://issues.apache.org/jira/browse/KARAF-639 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 2.2.1 > Environment: Maven 2.2.1 or Maven 3.0.2, Java 1.6 >Reporter: David Valeri >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > Attachments: KARAF-639-2.2.x-tests.patch, KARAF-639-trunk-tests.patch > > > A number of scenarios that are common in feature descriptors cause issues > with the validate goal of the plug-in. Support is better in the trunk; > however, at least one of the scenarios is still unsupported. > The fixes must be backported to the 2.2.x branch as the trunk does not > validate feature descriptors without a namespace declaration and many > existing feature descriptors that are transitively included in validation do > not currently include the namespace declaration. > The scenarios in question are: > 1) A blueprint file referenced from a bundle element. > 2) Loading bundles from a repository other than the default repositories for > PAX MVN/URL. > 3) Loading a WAR from a bundle element. > 4) Loading a plain JAR with the wrap protocol in a bundle element. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-602) Exploded OSGi bundle deployment with META-INF/MANIFEST.MF is not consistent
[ https://issues.apache.org/jira/browse/KARAF-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-602: --- Fix Version/s: (was: 3.0.3) 3.0.4 > Exploded OSGi bundle deployment with META-INF/MANIFEST.MF is not consistent > --- > > Key: KARAF-602 > URL: https://issues.apache.org/jira/browse/KARAF-602 > Project: Karaf > Issue Type: Bug > Components: karaf-osgi >Affects Versions: 2.2.0 > Environment: Ubuntu 10.10, java version "1.6.0_20" / OpenJDK Runtime > Environment (IcedTea6 1.9.7) (6b20-1.9.7-0ubuntu1) / OpenJDK Server VM (build > 19.0-b09, mixed mode), Linux annafi 2.6.35-29-generic-pae > #51+kamal~mjgbacklight4-Ubuntu SMP Mon Apr 18 20:46:42 UTC 2011 i686 GNU/Linux >Reporter: Hendy Irawan > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > When deploying an OSGi bundle with OSGI-INF/blueprint/something.xml by > copying the JAR file to deploy/, it works. > However: > 1. Copying the contents *excluding* META-INF/MANIFEST.MF to deploy/, > it works > 2. Copy META-INF/MANIFEST.MF to deploy//META-INF/MANIFEST.MF, it > doesn't work > By it doesn't work, meaning the previous bundle (in step 1) is uninstalled, > but the new (i.e. updated) bundle is not resolved, not active, not installed > at all. > logs is not helpful: (level is TRACE) > 03:42:21,508 | DEBUG | lixDispatchQueue | framework| > ? ? | 0 - org.apache.felix.framework - > 3.0.8 | FrameworkEvent PACKAGES REFRESHED > 03:42:21,508 | DEBUG | lixDispatchQueue | framework| > ? ? | 0 - org.apache.felix.framework - > 3.0.8 | FrameworkEvent PACKAGES REFRESHED > The same thing happens when the order is reversed: > 1. Delete deploy/ so we get a "clean start" > 2. Copying the contents *including* META-INF/MANIFEST.MF to deploy/, > it works > 3. Delete deploy//META-INF/MANIFEST.MF, it doesn't work > Seems like the exploded bundle undeployer left it in an inconsistent state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-520) JLine wired autocompletion behaviour when starting in linux via java process
[ https://issues.apache.org/jira/browse/KARAF-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-520: --- Fix Version/s: (was: 3.0.3) 3.0.4 > JLine wired autocompletion behaviour when starting in linux via java process > > > Key: KARAF-520 > URL: https://issues.apache.org/jira/browse/KARAF-520 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 2.2.0, 3.0.0 > Environment: Linux via Java Process >Reporter: Andreas Pieber > Fix For: 4.0.0, 3.0.4 > > > When you try to start Karaf via a separate Java Process in Linux (as shown > here e.g. > https://github.com/openengsb/openengsb-maven-plugin/blob/master/src/main/java/org/openengsb/openengsbplugin/Provision.java) > the autocompletion on console creates wired completion problems. Text is > duplicated, back does not work as expected, ... While the "real" text always > is correct the otuput does not reflect this in any way. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-511) When updating a bundle, completers are not always refreshed
[ https://issues.apache.org/jira/browse/KARAF-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-511: --- Fix Version/s: (was: 3.0.3) 3.0.4 > When updating a bundle, completers are not always refreshed > --- > > Key: KARAF-511 > URL: https://issues.apache.org/jira/browse/KARAF-511 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Reporter: Guillaume Nodet >Priority: Minor > Fix For: 4.0.0, 3.0.4 > > > The problem is that the CommandsCompleter#checkData checks for new/removed > commands, but if the names are the same, completers aren't refreshed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-222) Provide karaf:run, karaf:deploy, karaf:client Maven goals
[ https://issues.apache.org/jira/browse/KARAF-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-222: --- Fix Version/s: (was: 3.0.3) 3.0.4 > Provide karaf:run, karaf:deploy, karaf:client Maven goals > - > > Key: KARAF-222 > URL: https://issues.apache.org/jira/browse/KARAF-222 > Project: Karaf > Issue Type: New Feature > Components: karaf-tooling >Reporter: james strachan >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > Attachments: KARAF-222-run-mojo-1.diff > > > Did a quick google & couldn't see one yet - please close if there is one > already :) > The really nice thing about jetty:run is it watches the source code & > target/classes dir & auto redeploys on change, so there's no deploy step - > you just hack & compile (which your IDE or incremental compile can do - e.g. > "mvn scala:cc"). > For added bonus would be being able to add some extra bundles, so it can be a > RAD way to hack bundles. Maybe folks could have some integration junit tests > automatically rerun whenever the bundle is redeployed? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-365) Merge .kar files in features-maven-plugin during "add-features-to-repo" goal
[
https://issues.apache.org/jira/browse/KARAF-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-365:
---
Fix Version/s: (was: 3.0.3)
3.0.4
> Merge .kar files in features-maven-plugin during "add-features-to-repo" goal
>
>
> Key: KARAF-365
> URL: https://issues.apache.org/jira/browse/KARAF-365
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-tooling
>Reporter: Andreas Pieber
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.0.0, 3.0.4
>
>
> What I can think of there is to extend the add-feature-to-repo goal to
> something like:
> {code}
>
> org.apache.karaf.tooling
> features-maven-plugin
> ${karaf.version}
>
>
> add-features-to-repo
> generate-resources
>
> add-features-to-repo
>
>
>
> DESCRIPTORS
>
>
> FEATURES
>
>
> KARS
>
> target/features-repo
>
> true
>
>
>
>
> {code}
> .kar files could be installed via maven but basically nothing more than
> merging them into the "repository" happens. This should do it for now, should
> be simple to implement but allow an additional abstraction layer since entire
> packages could be used without looking at the features file at this place at
> all.
> I'm not sure by now how useful this will be since you can do the same via the
> feature file (which is anyhow required to build a kar file). But at least it
> would assist to make .kar to the default packaging for karaf features.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2511) Review and update documentation
[ https://issues.apache.org/jira/browse/KARAF-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2511: Fix Version/s: (was: 3.0.3) 3.0.4 > Review and update documentation > --- > > Key: KARAF-2511 > URL: https://issues.apache.org/jira/browse/KARAF-2511 > Project: Karaf > Issue Type: Task > Components: karaf-documentation >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > > The documentation (manual) should be reviewed: > - The subshell part should be described (usage and configuration). > - The "code samples"/screenshots have to be updated with Karaf 3.0.0 use cases > - a global polishing, double read -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2522) Boot feature bundle failure forces other bundles to start regardless 'start' flag
[ https://issues.apache.org/jira/browse/KARAF-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2522: Fix Version/s: (was: 3.0.3) 3.0.4 > Boot feature bundle failure forces other bundles to start regardless 'start' > flag > - > > Key: KARAF-2522 > URL: https://issues.apache.org/jira/browse/KARAF-2522 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 2.3.2, 2.3.3 >Reporter: Alexey Gavrilov >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.3.10, 2.4.2, 3.0.4 > > > If a bundle under a boot feature fails to start, then all the bundles marked > as 'start="false"' will be forced to start during handling an error. > Steps to reproduce: > - create a boot feature containing two bundles. > - make the first bundle fail on startup (due to missing dependency, for > example) > - mark the second bundle as 'start=false' > - start the Karaf container > - the first bundle will fail to start > - the second bundle will be started regardless the 'start=false' flag. > I think the problem is around the start bundle loop at > FeaturesServiceImpl.java:525 (in Karaf 2.3.2) which doesn't respect the > bunlde startup flag when starting the installed bundles when > 'Option.NoCleanIfFailure' is set. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2538) Per user command history
[ https://issues.apache.org/jira/browse/KARAF-2538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2538: Fix Version/s: (was: 3.0.3) 3.0.4 > Per user command history > > > Key: KARAF-2538 > URL: https://issues.apache.org/jira/browse/KARAF-2538 > Project: Karaf > Issue Type: Improvement > Components: karaf-shell >Reporter: Jonathan Anstey > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > As mentioned in KARAF-2503, it would be nice to have command history per > user. This is what folks used to a shell environment would expect I think. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2600) Failed to get the session when running client.bat to connect karaf instance
[ https://issues.apache.org/jira/browse/KARAF-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2600: Fix Version/s: (was: 3.0.3) 3.0.4 > Failed to get the session when running client.bat to connect karaf instance > --- > > Key: KARAF-2600 > URL: https://issues.apache.org/jira/browse/KARAF-2600 > Project: Karaf > Issue Type: Bug >Affects Versions: 3.0.0 > Environment: windows >Reporter: ChengRen >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > > After building the latest source code, when I execute the karaf.bat under > assemblies\apache-karaf\target\assembly\bin to get a karaf instance, > everything is ok. But, > 1) when I run client.bat to connect the karaf instance, I get this output > from console : "Failed to get the session." > 2) when I run shell.bat, I get this output: > Exception in thread "main" java.lang.NoClassDefFoundError: > org/osgi/util/tracker/ServiceTracker > at > org.apache.karaf.shell.console.impl.jline.ConsoleImpl.createSecuredCommandProcessor(ConsoleImpl.java:227) > at > org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:181) > at org.apache.karaf.shell.console.impl.Main.run(Main.java:214) > at org.apache.karaf.shell.console.impl.Main.run(Main.java:158) > at org.apache.karaf.shell.console.impl.Main.run(Main.java:73) > at org.apache.karaf.shell.console.impl.Main.main(Main.java:54) > Caused by: java.lang.ClassNotFoundException: > org.osgi.util.tracker.ServiceTracker > at java.net.URLClassLoader$1.run(URLClassLoader.java:366) > at java.net.URLClassLoader$1.run(URLClassLoader.java:355) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:354) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 6 more -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2612) jaas:group-* and jaas:group-role-* commands have not effect
[
https://issues.apache.org/jira/browse/KARAF-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2612:
Fix Version/s: (was: 3.0.3)
3.0.4
> jaas:group-* and jaas:group-role-* commands have not effect
> ---
>
> Key: KARAF-2612
> URL: https://issues.apache.org/jira/browse/KARAF-2612
> Project: Karaf
> Issue Type: Bug
> Components: karaf-security
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.4
>
>
> When doing:
> karaf@root()> jaas:realm-manage --index 1
> karaf@root()> jaas:group-add karaf mygroup
> karaf@root()> jaas:update
> the group doesn't appear with the jaas:user-list.
> More over the {{etc/users.properties}} file is not updated.
> Same thing when using the {{jaas:group-role-add}}.
> I set fix version as 3.0.0 for now, but depending to the time frame, it may
> be postponed to 3.0.1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2614) Add new operations in the SecurityMBean
[
https://issues.apache.org/jira/browse/KARAF-2614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2614:
Fix Version/s: (was: 3.0.3)
3.0.4
> Add new operations in the SecurityMBean
> ---
>
> Key: KARAF-2614
> URL: https://issues.apache.org/jira/browse/KARAF-2614
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-security
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.4
>
>
> With the new RBAC and groups features that we added, we also added a MBean
> where we find the canInvoke() operation to know if an user/role can perform
> an operation.
> This MBean object name is org.apache.karaf:type=security,area=jmx.
> It would make sense to provide another area where we can administrate the
> realms, users, groups, roles, as we can do with the {{jaas:*}} commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2613) Add group/role supports in LDAPLoginModule and JDBCLoginModule
[ https://issues.apache.org/jira/browse/KARAF-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2613: Fix Version/s: (was: 3.0.3) 3.0.4 > Add group/role supports in LDAPLoginModule and JDBCLoginModule > -- > > Key: KARAF-2613 > URL: https://issues.apache.org/jira/browse/KARAF-2613 > Project: Karaf > Issue Type: Bug > Components: karaf-security >Reporter: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > > Currently, on the PropertiesLoginModule fully supports users groups. > The other login modules (JDBCLoginModule and LDAPLoginModule) "only" supports > roles. > As now, Karaf uses roles in OSGi services, commands, and JMX MBeans ACL > definition, it makes sense to support roles and groups in all login modules. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2651) Minimal distribution should really be minimal
[ https://issues.apache.org/jira/browse/KARAF-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2651: Fix Version/s: (was: 3.0.3) 3.0.4 > Minimal distribution should really be minimal > - > > Key: KARAF-2651 > URL: https://issues.apache.org/jira/browse/KARAF-2651 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.4 > > > The Apache Karaf minimal distribution is like a Unix distribution: it > downloads most of the features/bundles during bootstrap. > However: > - the featuresBoot should really be minimal (for instance, the ssh feature > should not be a boot feature) > - it doesn't make sense that the system folder is so large. The system > repository should be "minimal" as most of the bundles are downloaded from > Internet. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2630) GenerateDescriptorMojo does not resolve conflicts
[
https://issues.apache.org/jira/browse/KARAF-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2630:
Fix Version/s: (was: 3.0.3)
3.0.4
> GenerateDescriptorMojo does not resolve conflicts
> -
>
> Key: KARAF-2630
> URL: https://issues.apache.org/jira/browse/KARAF-2630
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-tooling
>Affects Versions: 3.0.0.RC1
>Reporter: Maarten Winkels
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.4
>
> Attachments: karaf-2630.patch
>
>
> When a feature project has two different versions of a dependency in its
> graph, both versions are included in the generated feature.xml
> e.g.:
> DependencyTree:
> {code}...
> | +- org.activiti:activiti-engine:jar:5.15-SNAPSHOT:compile
> | | +- org.activiti:activiti-bpmn-converter:jar:5.15-SNAPSHOT:compile
> | | | +- org.activiti:activiti-bpmn-model:jar:5.15-SNAPSHOT:compile
> | | | | +- (org.apache.commons:commons-lang3:jar:3.1:compile -
> omitted for duplicate)
> | | | | \- (org.codehaus.jackson:jackson-core-asl:jar:1.9.13:compile
> - version managed from 1.9.9; omitted for duplicate)
> | | | +- (org.slf4j:slf4j-api:jar:1.7.5:provided - version managed
> from 1.7.2; scope managed from compile; omitted for duplicate)
> | | | +- (org.slf4j:jcl-over-slf4j:jar:1.7.2:compile - omitted for
> duplicate)
> | | | \- (org.apache.commons:commons-lang3:jar:3.1:compile - omitted
> for duplicate)
> | | +- org.apache.commons:commons-email:jar:1.2:compile
> | | | +- javax.mail:mail:jar:1.4.1:provided (scope managed from
> compile)
> | | | | \- (javax.activation:activation:jar:1.1.1:provided - version
> managed from 1.1; scope managed from compile; omitted for duplicate)
> | | | \- javax.activation:activation:jar:1.1.1:provided
> | | +- org.apache.commons:commons-lang3:jar:3.1:compile
> | | +- org.mybatis:mybatis:jar:3.2.2:compile
> | | +- (org.springframework:spring-beans:jar:3.2.4.RELEASE:provided -
> version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
> duplicate)
> | | +- joda-time:joda-time:jar:2.1:compile
> | | +- org.slf4j:slf4j-api:jar:1.7.5:provided
> | | \- org.slf4j:jcl-over-slf4j:jar:1.7.2:compile
> | | \- (org.slf4j:slf4j-api:jar:1.7.5:provided - version managed
> from 1.7.2; scope managed from compile; omitted for duplicate)
> | \- org.activiti:activiti-spring:jar:5.14:compile
> |+- (org.activiti:activiti-engine:jar:5.14:compile - omitted for
> conflict with 5.15-SNAPSHOT)
> |+- (org.springframework:spring-context:jar:3.2.4.RELEASE:provided -
> version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
> duplicate)
> |+- (org.springframework:spring-jdbc:jar:3.2.4.RELEASE:provided -
> version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
> duplicate)
> |+- (org.springframework:spring-tx:jar:3.2.4.RELEASE:provided -
> version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
> duplicate)
> |+- (org.apache.commons:commons-lang3:jar:3.1:compile - omitted for
> duplicate)
> |+- org.springframework:spring-orm:jar:3.2.4.RELEASE:provided
> (version managed from 3.1.2.RELEASE; scope managed from compile)
> || +- (aopalliance:aopalliance:jar:1.0:provided - scope managed
> from compile; omitted for duplicate)
> || +- (org.springframework:spring-beans:jar:3.2.4.RELEASE:provided
> - version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
> duplicate)
> || +- (org.springframework:spring-core:jar:3.2.4.RELEASE:provided -
> version managed from 3.0.7.RELEASE; scope managed from compile; omitted for
> duplicate)
> || +- (org.springframework:spring-jdbc:jar:3.2.4.RELEASE:provided -
> version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
> duplicate)
> || \- (org.springframework:spring-tx:jar:3.2.4.RELEASE:provided -
> version managed from 3.1.2.RELEASE; scope managed from compile; omitted for
> duplicate)
> |+- commons-dbcp:commons-dbcp:jar:1.4:compile
> || \- commons-pool:commons-pool:jar:1.5.4:compile
> |+- (org.slf4j:slf4j-api:jar:1.7.5:provided - version managed from
> 1.7.2; scope managed from compile; omitted for duplicate)
> |\- (org.slf4j:jcl-over-slf4j:jar:1.7.2:compile - omitted for
> duplicate)
> ...{code}
> generated feature.xml:
> {code}...
> mvn:org.activiti/activiti-engine/5.15-SNAPSHOT
>
> mvn:org.activiti/activiti-bpmn-converter/5.15-SNAPSHOT
> mvn:org.activiti/activiti-bpmn-model/5.15-SNAPSH
[jira] [Updated] (KARAF-2652) Create net distribution
[ https://issues.apache.org/jira/browse/KARAF-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2652: Fix Version/s: (was: 3.0.3) 3.0.4 > Create net distribution > --- > > Key: KARAF-2652 > URL: https://issues.apache.org/jira/browse/KARAF-2652 > Project: Karaf > Issue Type: New Feature > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.4 > > > In addition of the minimal distribution, I propose to add a net distribution > which downloads most of bundles/features from Internet at bootstrap. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2678) txlog files locked during admin clone on windows
[
https://issues.apache.org/jira/browse/KARAF-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2678:
Fix Version/s: (was: 3.0.3)
3.0.4
> txlog files locked during admin clone on windows
>
>
> Key: KARAF-2678
> URL: https://issues.apache.org/jira/browse/KARAF-2678
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 2.3.3
>Reporter: Jonathan Anstey
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 2.3.10, 2.4.2, 3.0.4
>
>
> For example:
> {code}
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (2.3.3)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'osgi:shutdown' or 'logout' to shutdown Karaf.
> karaf@root> features:install transaction
> karaf@root> admin:clone root backup
> Error executing command: java.io.IOException: The process cannot access the
> file
> because another process has locked a portion of the file
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2684) Create tests for Hibernate and OpenJPA features
[ https://issues.apache.org/jira/browse/KARAF-2684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2684: Fix Version/s: (was: 3.0.3) 3.0.4 > Create tests for Hibernate and OpenJPA features > --- > > Key: KARAF-2684 > URL: https://issues.apache.org/jira/browse/KARAF-2684 > Project: Karaf > Issue Type: Task > Components: karaf-test >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > A couple of users reported issues with both OpenJPA and Hibernate features. > If our itests currently test the right installation of the features, they > don't actually test the right behaviour of the features. > It would make sense to use Aries examples (ariestrader and blog) or our own > simple examples to test the right behaviour. > These examples should be part of the Karaf distribution including a section > in the developers guide. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2698) Add -l (level) option to log:display/log:tail in order to filter messages only for a given log level (and higher)
[ https://issues.apache.org/jira/browse/KARAF-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2698: Fix Version/s: (was: 3.0.3) 3.0.4 > Add -l (level) option to log:display/log:tail in order to filter messages > only for a given log level (and higher) > - > > Key: KARAF-2698 > URL: https://issues.apache.org/jira/browse/KARAF-2698 > Project: Karaf > Issue Type: Improvement > Components: karaf-documentation >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2688) Karaf info - Add memory details about perm gen pool
[
https://issues.apache.org/jira/browse/KARAF-2688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2688:
Fix Version/s: (was: 3.0.3)
3.0.4
> Karaf info - Add memory details about perm gen pool
> ---
>
> Key: KARAF-2688
> URL: https://issues.apache.org/jira/browse/KARAF-2688
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-core, karaf-shell
>Affects Versions: 2.3.3
>Reporter: Claus Ibsen
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.0.0, 2.4.2, 3.0.4
>
> Attachments: Screen Shot 2014-01-16 at 3.05.16 PM.png
>
>
> When running the info command you get some JVM details
> For memory you get
> {code}
> Memory
> Current heap size 90,407 kbytes
> Maximum heap size 521,216 kbytes
> Committed heap size 106,496 kbytes
> {code}
> It would be good to have the perm-gen pool as well. As if you are running out
> of perm gen you are fucked. The GC cannot reclaim perm gen memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2712) Bundles cache corrupted
[ https://issues.apache.org/jira/browse/KARAF-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2712: Fix Version/s: (was: 3.0.3) 3.0.4 > Bundles cache corrupted > --- > > Key: KARAF-2712 > URL: https://issues.apache.org/jira/browse/KARAF-2712 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > It seems that we have an issue with Felix framework: the bundles cache (in > the data folder) gets corrupted, pushing Karaf in a complete toasted state. > A possible scenario to reproduce it is: > - install a couple of bundles using bundles:install command > - kill the Karaf java process > - try to start Karaf again, it should failed. > This scenario has to be tested: > - with Equinox as framework (it should work) > - with Karaf 2.3.x (it should work with Felix framework 4.0.2) > - depending if the bundles is in the system repository or not (to see if > pax-url-aether may have an impact) > - with Karaf 3.0.0 (it should fail with Felix framework 4.2.1) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-2712) Bundles cache corrupted
[ https://issues.apache.org/jira/browse/KARAF-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292382#comment-14292382 ] Jean-Baptiste Onofré commented on KARAF-2712: - I need more time to implement a complete fix (I have some stuff already ready). I postpone to 3.0.4. > Bundles cache corrupted > --- > > Key: KARAF-2712 > URL: https://issues.apache.org/jira/browse/KARAF-2712 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > It seems that we have an issue with Felix framework: the bundles cache (in > the data folder) gets corrupted, pushing Karaf in a complete toasted state. > A possible scenario to reproduce it is: > - install a couple of bundles using bundles:install command > - kill the Karaf java process > - try to start Karaf again, it should failed. > This scenario has to be tested: > - with Equinox as framework (it should work) > - with Karaf 2.3.x (it should work with Felix framework 4.0.2) > - depending if the bundles is in the system repository or not (to see if > pax-url-aether may have an impact) > - with Karaf 3.0.0 (it should fail with Felix framework 4.2.1) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2735) Add samples in distribution
[ https://issues.apache.org/jira/browse/KARAF-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2735: Fix Version/s: (was: 3.0.3) 3.0.4 > Add samples in distribution > --- > > Key: KARAF-2735 > URL: https://issues.apache.org/jira/browse/KARAF-2735 > Project: Karaf > Issue Type: Improvement > Components: karaf-demo, karaf-documentation >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > I would like to replace the demos folder (as it's not really demo) by a > samples modules. > The purpose is to provide examples with README about the different features > (one per sub-module) provided by Karaf. > I will bootstrap this module on master later today including the skeleton for > the different sub-module. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2784) Add -p (--persist) to the bundle:install and feature:install commands
[ https://issues.apache.org/jira/browse/KARAF-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2784: Fix Version/s: (was: 3.0.3) 3.0.4 > Add -p (--persist) to the bundle:install and feature:install commands > - > > Key: KARAF-2784 > URL: https://issues.apache.org/jira/browse/KARAF-2784 > Project: Karaf > Issue Type: Improvement > Components: karaf-core, karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > > In addition of populating the bundle cache, it would be great to add a -p > (--persist) option to bundle:install and feature:install commands (and > corresponding operations in the MBeans). > The purpose is: > - to store the artifacts in the system repository (or any repository defined > in etc/org.ops4j.pax.url.mvn.cfg file) > - in the case of features, eventually update the featuresBoot property in > etc/org.apache.karaf.features.cfg file -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2810) Add feature installation date and a flag indicating if it's a boot feature
[ https://issues.apache.org/jira/browse/KARAF-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2810: Fix Version/s: (was: 3.0.3) 3.0.4 > Add feature installation date and a flag indicating if it's a boot feature > -- > > Key: KARAF-2810 > URL: https://issues.apache.org/jira/browse/KARAF-2810 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > > Now, there is no way to know when a feature has been installed. And so, it's > not easy to find if the feature has been installed as a boot features, or by > an user. > It would be great to add some metadata like the feature installation date, > displayed in feature:list/feature:info commands output. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2836) Be able to define multiple keys per user in etc/keys.properties
[
https://issues.apache.org/jira/browse/KARAF-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2836:
Fix Version/s: (was: 3.0.3)
3.0.4
> Be able to define multiple keys per user in etc/keys.properties
> ---
>
> Key: KARAF-2836
> URL: https://issues.apache.org/jira/browse/KARAF-2836
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 2.4.2, 3.0.4
>
>
> Currently, if we define multiple keys in etc/keys.properties like this:
> {code}
> karaf=key,admin
> karaf=other,admin
> {code}
> only the latest one is used/loaded (for instance other here).
> It would be great to be able to load multiple keys for one given user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-2814) Add jmx:* commands and feature
[ https://issues.apache.org/jira/browse/KARAF-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2814: Fix Version/s: (was: 3.0.3) 3.0.4 > Add jmx:* commands and feature > -- > > Key: KARAF-2814 > URL: https://issues.apache.org/jira/browse/KARAF-2814 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > I prepared a new feature on a local branch: the jmx feature. > This feature contains: > - jmx-jolokia to easily install jolokia in Karaf > - jmx-commands providing new jmx:* commands to manipulate MBeans directly > (jmx:query, jmx:set, etc). It could be a local action (using the local MBean > server) or remote (providing the JMX service URL). > I will submit the proposal on the mailing list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2843) Add Spring Security 3.2.3.RELEASE, Spring LDAP, and Spring Batch features
[ https://issues.apache.org/jira/browse/KARAF-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2843: Fix Version/s: (was: 3.0.3) 3.0.4 > Add Spring Security 3.2.3.RELEASE, Spring LDAP, and Spring Batch features > - > > Key: KARAF-2843 > URL: https://issues.apache.org/jira/browse/KARAF-2843 > Project: Karaf > Issue Type: New Feature > Components: karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2882) using OBR resolver in feature files causes timeout to be hit
[ https://issues.apache.org/jira/browse/KARAF-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2882: Fix Version/s: (was: 3.0.3) 3.0.4 > using OBR resolver in feature files causes timeout to be hit > > > Key: KARAF-2882 > URL: https://issues.apache.org/jira/browse/KARAF-2882 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.0 >Reporter: Phillip Balli >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.3.10, 2.4.2, 3.0.4 > > > When the features service installs a bundle resolved via OBR whose source is > an "http" url (like when pointing to a karaf-cave server), it > (karaf.features.internal.BundleManager) will wait for a service with the > property url.handler.protocol=http to become available. Because there is no > such service, a 30s timeout will hit for every obr-sourced bundle. > > I believe this is because url handlers for http, https, etc. are provided by > default by felix. I'm not sure if these handlers were intended to be > discoverable via properties in karaf. > I have made a change to waitForUrlHandler to not wait for "default" protocols. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2925) Add JMXMP support
[ https://issues.apache.org/jira/browse/KARAF-2925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2925: Fix Version/s: (was: 3.0.3) 3.0.4 > Add JMXMP support > - > > Key: KARAF-2925 > URL: https://issues.apache.org/jira/browse/KARAF-2925 > Project: Karaf > Issue Type: New Feature > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > > In addition of our JMX RMI standard connector, it would be great to provide > support for JMXMP protocol. > The JMX Messaging Protocol (JMXMP) connector is a configuration of the > generic connector where the transport protocol is based on TCP and the object > wrapping is native Java serialization. Security is more advanced than for the > RMI connector. Security is based on the Java Secure Socket Extension (JSSE), > the Java Authentication and Authorization Service (JAAS), and the Simple > Authentication and Security Layer (SASL). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2969) Provide a script to install wrapper/service without starting Karaf
[ https://issues.apache.org/jira/browse/KARAF-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2969: Fix Version/s: (was: 3.0.3) 3.0.4 > Provide a script to install wrapper/service without starting Karaf > -- > > Key: KARAF-2969 > URL: https://issues.apache.org/jira/browse/KARAF-2969 > Project: Karaf > Issue Type: New Feature > Components: karaf-os-integration >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > Right now, the wrapper/service installation requires to start karaf, install > the wrapper feature, and finally execute the wrapper:install command. > It would be great to have a script to create the wrapper resource without > starting Karaf and installing the wrapper feature. > The script can do the same as the wrapper:install command: detect the OS, > generate the wrapper files, and provide a description message to integrate in > the OS boot service (runlevel/init.d, or windows service). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-2960) Optional KAR feature installation
[ https://issues.apache.org/jira/browse/KARAF-2960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2960: Fix Version/s: (was: 3.0.3) 3.0.4 > Optional KAR feature installation > - > > Key: KARAF-2960 > URL: https://issues.apache.org/jira/browse/KARAF-2960 > Project: Karaf > Issue Type: Improvement > Components: karaf-kar >Affects Versions: 3.0.1 >Reporter: Simon Watson >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.0.0, 3.0.4 > > > I find the KAR feature of Karaf very useful, and a great way to manage server > deployments. I notice that when a KAR is installed (via console, or from > deploy dir), that all features are automatically installed. > Is it possible to only install the KAR's feature-repos and leave the features > to be installed manually? > This would help where we have feature A and feature B, both depending on > feature C. It's easy to include all three in one features XML but we might > not want both A and B installing on every server. As things stand, we have to > manually uninstall the ones we don't want. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3074) Provide mbeans for statistics of hibernate session factories
[ https://issues.apache.org/jira/browse/KARAF-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3074: Fix Version/s: (was: 3.0.3) 3.0.4 > Provide mbeans for statistics of hibernate session factories > > > Key: KARAF-3074 > URL: https://issues.apache.org/jira/browse/KARAF-3074 > Project: Karaf > Issue Type: New Feature >Affects Versions: 2.3.5 >Reporter: Christian Schneider > Fix For: 4.0.0, 3.0.4 > > > Hibernate session factories provides JMX Beans for its statistics. > We could create a bundle that looks for all EntityManagerFactories, retrieves > the hibernate session factories and publishes a jmx bean for each. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3035) Use aries transaction jdbc / jms for pooling
[ https://issues.apache.org/jira/browse/KARAF-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3035: Fix Version/s: (was: 3.0.3) 3.0.4 > Use aries transaction jdbc / jms for pooling > > > Key: KARAF-3035 > URL: https://issues.apache.org/jira/browse/KARAF-3035 > Project: Karaf > Issue Type: Improvement >Affects Versions: 4.0.0 >Reporter: Guillaume Nodet >Assignee: Guillaume Nodet > Fix For: 4.0.0, 2.4.2, 3.0.4 > > Attachments: templates.zip, vcs-diff1271163984438294153.patch, > vcs-diff458849033395514.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3100) Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin
[ https://issues.apache.org/jira/browse/KARAF-3100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3100: Fix Version/s: (was: 3.0.3) 3.0.4 > Add Option To Create Config Files For Feature Configs Instead Of Importing > Directly Into Config Admin > - > > Key: KARAF-3100 > URL: https://issues.apache.org/jira/browse/KARAF-3100 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Affects Versions: 3.0.1 >Reporter: Gareth Collins >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > I have created a pull request for this here: > https://github.com/apache/karaf/pull/43 > As the title says, this allows karaf to be configured to output feature > configurations to config file...which I believe are easier to manage. Let me > know what you think. If it looks OK, would it be possible to merge soon (e.g. > karaf 3.0.2 :))? The changes are very localized. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3095) itests randomly fail to get the JMXConnector
[
https://issues.apache.org/jira/browse/KARAF-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3095:
Fix Version/s: (was: 3.0.3)
3.0.4
> itests randomly fail to get the JMXConnector
>
>
> Key: KARAF-3095
> URL: https://issues.apache.org/jira/browse/KARAF-3095
> Project: Karaf
> Issue Type: Bug
> Components: karaf-test
>Affects Versions: 4.0.0, 3.0.2
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.4
>
>
> When doing to global build, and executing all itests in a row, the itests
> randomly fail:
> {code}
> ---
> Test set: org.apache.karaf.itests.ServiceTest
> ---
> Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.325 sec <<<
> FAILURE! - in org.apache.karaf.itests.ServiceTest
> listViaMBean(org.apache.karaf.itests.ServiceTest) Time elapsed: 0.03 sec
> <<< ERROR!
> java.rmi.NoSuchObjectException: no such object in table
> at
> sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:275)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:252)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:161)
> at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown
> Source)
> at
> javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2404)
> at
> javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:308)
> at
> javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:268)
> at
> org.apache.karaf.itests.KarafTestSupport.getJMXConnector(KarafTestSupport.java:350)
> at
> org.apache.karaf.itests.KarafTestSupport.getJMXConnector(KarafTestSupport.java:342)
> at
> org.apache.karaf.itests.ServiceTest.listViaMBean(ServiceTest.java:45)
> {code}
> It seems that the KarafTestSupport is not able to get the JMX connector:
> {code}
> KarafTestSupport.getJMXConnector
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3136) Karaf can't start if you have whitespaces in brackets in JAVA_OPTS
[ https://issues.apache.org/jira/browse/KARAF-3136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3136: Fix Version/s: (was: 3.0.3) 3.0.4 > Karaf can't start if you have whitespaces in brackets in JAVA_OPTS > -- > > Key: KARAF-3136 > URL: https://issues.apache.org/jira/browse/KARAF-3136 > Project: Karaf > Issue Type: Bug > Components: karaf-config >Affects Versions: 2.3.1, 3.0.1 > Environment: Windows 7 >Reporter: Abakumov Konstantin >Assignee: Jean-Baptiste Onofré >Priority: Trivial > Fix For: 4.0.0, 2.3.10, 2.4.2, 3.0.4 > > Original Estimate: 1h > Remaining Estimate: 1h > > If you set java option in setenv.bat with whitespaces, inserted between > double-quotation symobols like this: > *set JAVA_OPTS=%JAVA_OPTS% -Dlog4j.configuration="C:\programm > files\karaf\etc\log4j.properties"* > You'll get error on startup > *files\karaf\etc\log4j.properties" " was unexpected at this time.* > This goes from karaf.bat line: > *if "%JAVA_OPTS%" == "" set JAVA_OPTS=%DEFAULT_JAVA_OPTS%* > quote symbols wrongly associated in "%JAVA_OPTS%" during script execution -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3160) Kar installer/deployer should use the feature install attribute
[ https://issues.apache.org/jira/browse/KARAF-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3160: Fix Version/s: (was: 3.0.3) 3.0.4 > Kar installer/deployer should use the feature install attribute > --- > > Key: KARAF-3160 > URL: https://issues.apache.org/jira/browse/KARAF-3160 > Project: Karaf > Issue Type: Improvement > Components: karaf-kar >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 4.0.0, 3.0.4 > > > By default, when installing a kar file (by directly dropping the kar file > into the deploy folder, or using kar:* commands), all features contained in > the kar file will be installed by default. > Karaf doesn't check the feature install attribute. > The feature install attribute can contains "auto" indicating that this > feature should be automatically installed. > The kar deployer should check the feature install attribute to determine if > the feature should be installed automatically or not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3193) Add diag webconsole plugin
[ https://issues.apache.org/jira/browse/KARAF-3193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3193: Fix Version/s: (was: 3.0.3) 3.0.4 > Add diag webconsole plugin > -- > > Key: KARAF-3193 > URL: https://issues.apache.org/jira/browse/KARAF-3193 > Project: Karaf > Issue Type: New Feature > Components: karaf-webconsole >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > The bundle:diag command (and other diag:* commands) is helpful for end user > to get some details about the current bundle state. > It would be helpful to provide a "Diagnostic" view on the Karaf WebConsole, > providing the same information as in the commands. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3194) Add feature-generate-doc mojo
[ https://issues.apache.org/jira/browse/KARAF-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3194: Fix Version/s: (was: 3.0.3) 3.0.4 > Add feature-generate-doc mojo > - > > Key: KARAF-3194 > URL: https://issues.apache.org/jira/browse/KARAF-3194 > Project: Karaf > Issue Type: New Feature > Components: karaf-tooling >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > > In order to generate a documentation on the resources containing: > - the feature description > - the feature transitive features > - the feature bundles > - the feature configs > it would be great to have karaf:feature-generate-doc as we have > karaf:commands-generate-doc mojo. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3235) Extend karaf-test jar
[ https://issues.apache.org/jira/browse/KARAF-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3235: Fix Version/s: (was: 3.0.3) 3.0.4 > Extend karaf-test jar > - > > Key: KARAF-3235 > URL: https://issues.apache.org/jira/browse/KARAF-3235 > Project: Karaf > Issue Type: Improvement > Components: karaf-test >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > End userscan easily implement itest by extending the KarafTestSupport > provided in the karaf-test jar. > In that case, the KarafTestSupport should provide most of the methods as > public to be able to directly use executeCommand(), etc. > It would simplify writing utest/itest for end users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3216) Improve the SyncopeLoginModule using HttpURLConnection instead of httpclient
[ https://issues.apache.org/jira/browse/KARAF-3216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3216: Fix Version/s: (was: 3.0.3) 3.0.4 > Improve the SyncopeLoginModule using HttpURLConnection instead of httpclient > > > Key: KARAF-3216 > URL: https://issues.apache.org/jira/browse/KARAF-3216 > Project: Karaf > Issue Type: Improvement > Components: karaf-security >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.3.10, 2.4.2, 3.0.4 > > > The jaas modules bundle embeds httpclient to use the Syncope REST API. > In order to trim down this bundle, we should use the HttpURLConnection > (provided by the JDK). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3241) WAR fails to deploy due to duplicate package import
[
https://issues.apache.org/jira/browse/KARAF-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3241:
Fix Version/s: (was: 3.0.3)
3.0.4
> WAR fails to deploy due to duplicate package import
> ---
>
> Key: KARAF-3241
> URL: https://issues.apache.org/jira/browse/KARAF-3241
> Project: Karaf
> Issue Type: Bug
> Components: karaf-webcontainer
>Affects Versions: 3.0.1, 3.0.2
>Reporter: Harald Wellmann
> Fix For: 3.0.4
>
>
> With the {{war}} feature installed, a plain old WAR copied to the {{deploy}}
> directory may fail to deploy due to duplicate package imports in the
> on-the-fly manifest.
> The same problem occurs when installing the bundle interactively using the
> war: protocol, e.g.
> {code}
> bundle:install war:mvn:org.apache.wicket/wicket-examples/1.5.3/war
> {code}
> Stacktrace:
> {noformat}
> 2014-09-18 15:33:04,031 | ERROR | Local user karaf | ShellUtil
> | 37 - org.apache.karaf.shell.console - 3.0.1 | Exception caught
> while executing command
> org.apache.karaf.shell.console.MultiException: Error installing bundles:
> Unable to install bundle
> war:mvn:org.apache.wicket/wicket-examples/1.5.3/war
> at
> org.apache.karaf.shell.console.MultiException.throwIf(MultiException.java:92)
> at org.apache.karaf.bundle.command.Install.doExecute(Install.java:69)
> at
> org.apache.karaf.shell.console.AbstractAction.execute(AbstractAction.java:33)
> at
> org.apache.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:39)
> at
> org.apache.karaf.shell.commands.basic.AbstractCommand.execute(AbstractCommand.java:33)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)[:1.7.0_67]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_67]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_67]
> at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_67]
> at
> org.apache.aries.proxy.impl.ProxyHandler$1.invoke(ProxyHandler.java:54)
> at
> org.apache.aries.proxy.impl.ProxyHandler.invoke(ProxyHandler.java:119)
> at
> org.apache.karaf.shell.console.commands.$BlueprintCommand2053417194.execute(Unknown
> Source)[37:org.apache.karaf.shell.console:3.0.1]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)[:1.7.0_67]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_67]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_67]
> at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_67]
> at
> org.apache.aries.proxy.impl.ProxyHandler$1.invoke(ProxyHandler.java:54)
> at
> org.apache.aries.proxy.impl.ProxyHandler.invoke(ProxyHandler.java:119)
> at
> org.apache.karaf.shell.console.commands.$BlueprintCommand2053417194.execute(Unknown
> Source)[37:org.apache.karaf.shell.console:3.0.1]
> at
> org.apache.felix.gogo.runtime.CommandProxy.execute(CommandProxy.java:78)[37:org.apache.karaf.shell.console:3.0.1]
> at
> org.apache.felix.gogo.runtime.Closure.executeCmd(Closure.java:477)[37:org.apache.karaf.shell.console:3.0.1]
> at
> org.apache.felix.gogo.runtime.Closure.executeStatement(Closure.java:403)[37:org.apache.karaf.shell.console:3.0.1]
> at
> org.apache.felix.gogo.runtime.Pipe.run(Pipe.java:108)[37:org.apache.karaf.shell.console:3.0.1]
> at
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:183)[37:org.apache.karaf.shell.console:3.0.1]
> at
> org.apache.felix.gogo.runtime.Closure.execute(Closure.java:120)[37:org.apache.karaf.shell.console:3.0.1]
> at
> org.apache.felix.gogo.runtime.CommandSessionImpl.execute(CommandSessionImpl.java:89)
> at
> org.apache.karaf.shell.console.impl.jline.ConsoleImpl$DelegateSession.execute(ConsoleImpl.java:521)
> at
> org.apache.karaf.shell.console.impl.jline.ConsoleImpl.run(ConsoleImpl.java:212)
> at java.lang.Thread.run(Thread.java:745)[:1.7.0_67]
> at
> org.apache.karaf.shell.console.impl.jline.ConsoleFactoryService$3.doRun(ConsoleFactoryService.java:126)[37:org.apache.karaf.shell.console:3.0.1]
> at
> org.apache.karaf.shell.console.impl.jline.ConsoleFactoryService$3$1.run(ConsoleFactoryService.java:117)
> at java.security.AccessController.doPrivileged(Native Method)[:1.7.0_67]
> at
> org.apache.karaf.jaas.modules.JaasHelper.doAs(JaasHelper.java:47)[38:org.apache.karaf.jaas.modules:3.0.1]
> at
> org.apache.karaf.shell.console.impl.jline.ConsoleFactoryService$3.run(ConsoleFactoryService.java:115)[37:org.apache.karaf.shell.console:3.0.1
[jira] [Updated] (KARAF-3236) Unable to use character @ in Karaf console
[ https://issues.apache.org/jira/browse/KARAF-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3236: Fix Version/s: (was: 3.0.3) 3.0.4 > Unable to use character @ in Karaf console > -- > > Key: KARAF-3236 > URL: https://issues.apache.org/jira/browse/KARAF-3236 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.2 > Environment: Windows >Reporter: Nicolas Dutertry >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > > On Windows, it is not possible to use character '@' in Karaf console. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3262) Being able to use ${karaf.etc} in feature element
[
https://issues.apache.org/jira/browse/KARAF-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3262:
Fix Version/s: (was: 3.0.3)
3.0.4
> Being able to use ${karaf.etc} in feature element
> ---
>
> Key: KARAF-3262
> URL: https://issues.apache.org/jira/browse/KARAF-3262
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-feature
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 2.4.2, 3.0.4
>
>
> The element in a feature accepts a finalname attribute to
> define where the configfile has to be copied.
> However, finalname is relative to ${karaf.base}, whereas it should be able to
> use ${karaf.etc} (and so relative to ${karaf.etc}).
> In order to be backward compatible, if finalname starts with /etc/ it will be
> relative to ${karaf.base}, else it will be related to ${karaf.etc}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3263) karaf-maven-plugin install=auto support for aggregate features
[
https://issues.apache.org/jira/browse/KARAF-3263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3263:
Fix Version/s: (was: 3.0.3)
3.0.4
> karaf-maven-plugin install=auto support for aggregate features
> --
>
> Key: KARAF-3263
> URL: https://issues.apache.org/jira/browse/KARAF-3263
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
>Affects Versions: 3.0.1
>Reporter: Gary Kennedy
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.0.0, 3.0.4
>
>
> When using karaf-maven-plugin:features-generate-descriptor, the generated
> tags for xml/feature dependencies are not merged with the
> feature.xml template so I cannot add install="auto" to the feature tag.
> eg,
> POM:
> {code}
> ...
> feature
> ...
>
>
>
> featureA
> xml
> features
>
>
> ...
>
>
>
> org.apache.karaf.tooling
> karaf-maven-plugin
> 3.0.1
> true
>
> true
>
>
>
>
> {code}
> feature.xml template (src/main/feature/feature.xml):
> {code}
>
>
>
>
> {code}
> results in:
> {code}
>
>
>
>
>
>
>
> {code}
> Since this is for generating an "application" feature from individual
> "component" features, and none of the "component" features are auto-install
> in one "application" and no-auto-install in another, I can work around this
> by specifying the install attribute in the "component" feature.xml.
> So, would it be possible to merge aggregated features with the feature
> template? (eg, matching on name and only overriding the feature tag
> attributes except for version, so only
> install/description/resolver/start-level. Contents to be replaced with
> dependency feature content - we don't want to mess with those)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3270) Add command/MBean operation to give current user and his roles
[ https://issues.apache.org/jira/browse/KARAF-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3270: Fix Version/s: (was: 3.0.3) 3.0.4 > Add command/MBean operation to give current user and his roles > -- > > Key: KARAF-3270 > URL: https://issues.apache.org/jira/browse/KARAF-3270 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > > When logged on with an user (on the local console, ssh, MBean), it would be > great to get the current username (even if we have in the prompt and in the > console session), but also with current user roles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3272) gemini-blueprint feature doesn't work
[
https://issues.apache.org/jira/browse/KARAF-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3272:
Fix Version/s: (was: 3.0.3)
3.0.4
> gemini-blueprint feature doesn't work
> -
>
> Key: KARAF-3272
> URL: https://issues.apache.org/jira/browse/KARAF-3272
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 3.0.2
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.4
>
>
> If the installation of the gemini-blueprint feature works fine, at startup,
> the germini bundles fail:
> {code}
> Exception in thread "EclipseGeminiBlueprintExtenderThread-18"
> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
> 22 in XML document from URL
> [bundle://51.0:0/OSGI-INF/blueprint/kar-deployer.xml] is invalid; nested
> exception is org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The
> matching wildcard is strict, but no declaration can be found for element
> 'ext:property-placeholder'.
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)
> at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:174)
> at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:209)
> at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:180)
> at
> org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:170)
> at
> org.eclipse.gemini.blueprint.context.support.OsgiBundleXmlApplicationContext.loadBeanDefinitions(OsgiBundleXmlApplicationContext.java:140)
> at
> org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:130)
> at
> org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:539)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:451)
> at
> org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.access$301(AbstractDelegatedExecutionApplicationContext.java:60)
> at
> org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$1.run(AbstractDelegatedExecutionApplicationContext.java:168)
> at
> org.eclipse.gemini.blueprint.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
> at
> org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.normalRefresh(AbstractDelegatedExecutionApplicationContext.java:164)
> at
> org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext$NoDependenciesWaitRefreshExecutor.refresh(AbstractDelegatedExecutionApplicationContext.java:78)
> at
> org.eclipse.gemini.blueprint.context.support.AbstractDelegatedExecutionApplicationContext.refresh(AbstractDelegatedExecutionApplicationContext.java:157)
> at
> org.eclipse.gemini.blueprint.extender.internal.activator.LifecycleManager$1.run(LifecycleManager.java:222)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.c: The
> matching wildcard is strict, but no declaration can be found for element
> 'ext:property-placeholder'.
> at
> org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
> Source)
> at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> at
> org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown
> Source)
> at
> org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
> at
> org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown
> Source)
> at org.apache.xerces.impl.xs.XMLSchemaValidator.emptyElement(Unknown
> Source)
>
[jira] [Updated] (KARAF-3274) MBean itests randomly fail
[
https://issues.apache.org/jira/browse/KARAF-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3274:
Fix Version/s: (was: 3.0.3)
3.0.4
> MBean itests randomly fail
> --
>
> Key: KARAF-3274
> URL: https://issues.apache.org/jira/browse/KARAF-3274
> Project: Karaf
> Issue Type: Bug
> Components: karaf-test
>Affects Versions: 4.0.0, 3.0.2
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.4
>
>
> Locally or on Jenkins, MBean itests randomly fail with:
> {code}
> java.rmi.NoSuchObjectException: no such object in table
> {code}
> I think it's due to the MBean RMIServer cleaned by the GC (related to
> http://java.sun.com/j2se/1.5.0/docs/guide/rmi/spec/rmi-arch4.html).
> To avoid this, it should be static.
> I will create a itest (explicitily calling the GC to "force" the error) and
> fix that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3278) Display warning message with trying to install an already installed bundle
[ https://issues.apache.org/jira/browse/KARAF-3278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3278: Fix Version/s: (was: 3.0.3) 3.0.4 > Display warning message with trying to install an already installed bundle > -- > > Key: KARAF-3278 > URL: https://issues.apache.org/jira/browse/KARAF-3278 > Project: Karaf > Issue Type: Improvement > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > > Using bundle:install command (or install() operation on the BundleMBean) with > an already installed bundle (same location or symbolic name/version) just do > nothing. > It would be helpful to display a warning message to the user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (KARAF-3282) highlight local classes/resources in "bundle:classes" command
[ https://issues.apache.org/jira/browse/KARAF-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-3282 started by Jean-Baptiste Onofré. --- > highlight local classes/resources in "bundle:classes" command > - > > Key: KARAF-3282 > URL: https://issues.apache.org/jira/browse/KARAF-3282 > Project: Karaf > Issue Type: Improvement > Components: karaf-core >Affects Versions: 3.0.2 >Reporter: Frank Diebolt >Assignee: Jean-Baptiste Onofré >Priority: Trivial > Labels: command, console > Fix For: 4.0.0, 3.0.3 > > Original Estimate: 5m > Remaining Estimate: 5m > > It would be nice to distinguish between "local" and imported resources when > issuing a "bundle:classes" command. > I suggest to highlight "local" resources as it is done in the "headers" > command. > see my pull request: https://github.com/apache/karaf/pull/48 > Thanks in advance. > Best regards, > Frank -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3323) Upgrade Maven dependencies (aether, plugin, etc)
[ https://issues.apache.org/jira/browse/KARAF-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3323: Fix Version/s: (was: 3.0.3) 3.0.4 > Upgrade Maven dependencies (aether, plugin, etc) > > > Key: KARAF-3323 > URL: https://issues.apache.org/jira/browse/KARAF-3323 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-tooling >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 2.4.2, 3.0.4 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3324) Document prod/dev mode of etc/org.ops4j.pax.url.mvn.cfg file
[ https://issues.apache.org/jira/browse/KARAF-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3324: Fix Version/s: (was: 3.0.3) 3.0.4 > Document prod/dev mode of etc/org.ops4j.pax.url.mvn.cfg file > > > Key: KARAF-3324 > URL: https://issues.apache.org/jira/browse/KARAF-3324 > Project: Karaf > Issue Type: Improvement > Components: karaf-core, karaf-documentation >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > > http://karaf.922171.n3.nabble.com/Best-practice-question-development-cycle-for-a-bundle-td4036017.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3334) Change Karaf to (from) dev mode
[ https://issues.apache.org/jira/browse/KARAF-3334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3334: Fix Version/s: (was: 3.0.3) 3.0.4 > Change Karaf to (from) dev mode > --- > > Key: KARAF-3334 > URL: https://issues.apache.org/jira/browse/KARAF-3334 > Project: Karaf > Issue Type: Improvement >Affects Versions: 3.0.2 >Reporter: Jean-Philippe CLEMENT >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > > Karaf assembly plugin creates a configuration which first looks for artifacts > from its internal repository. > A side effect is that assembled bundles would not be updated from user Maven > repositories. This is ennoying in dev phase where updating bundles is a daily > job :) > Two solutions can be done. Either change the configuration (3 lines must be > modified), or remove bundles from the system sub-directory. At present time > we are using the second solution as it is more simple. > We would suggest to add a Karaf command line to go to dev mode without > manually affect the configuration. > PS: A simple flag inside configuration could also be welcome -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3360) karaf-maven-plugin expects '$' as bundle URL argument separator
[ https://issues.apache.org/jira/browse/KARAF-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3360: Fix Version/s: (was: 3.0.3) 3.0.4 > karaf-maven-plugin expects '$' as bundle URL argument separator > --- > > Key: KARAF-3360 > URL: https://issues.apache.org/jira/browse/KARAF-3360 > Project: Karaf > Issue Type: Bug > Components: karaf-tooling >Affects Versions: 3.0.2, 4.0.0.M1 >Reporter: Maciej Mraczek > Labels: feature > Fix For: 4.0.0, 3.0.4 > > > karaf-maven-plugin -> InstallKarsMojo -> installBundle exptects '$' as URL > arguments separator. > The '$' is not properly recognized by Karaf core, so it is not possible to > install feature which contains bundle (i.e. webbundle) with URL with '$' used > as argument separator. > The symbol should be "?" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (KARAF-3475) No refresh of bundles during feature install
[
https://issues.apache.org/jira/browse/KARAF-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292317#comment-14292317
]
Jean-Baptiste Onofré commented on KARAF-3475:
-
The change produces a bunch of itests failures. I need more time to investigate
(after 3.0.3 release).
> No refresh of bundles during feature install
>
>
> Key: KARAF-3475
> URL: https://issues.apache.org/jira/browse/KARAF-3475
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 3.0.2
>Reporter: Frank Diebolt
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.4
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> Hi,
> I successfully tested the fix below :
> In the source file
> features/core/src/main/java/org/apache/karaf/features/internal/BundleManager.java
> protected void refreshPackages(Collection bundles) {
> final Object refreshLock = new Object();
> -FrameworkWiring wiring =
> bundleContext.getBundle().adapt(FrameworkWiring.class);
> +FrameworkWiring wiring =
> bundleContext.getBundle(0).adapt(FrameworkWiring.class);
> Currently wiring is always null, FrameworkWiring can be obtained on bundle 0
> only.
> BR
> Frank
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3475) No refresh of bundles during feature install
[
https://issues.apache.org/jira/browse/KARAF-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3475:
Fix Version/s: (was: 3.0.3)
3.0.4
> No refresh of bundles during feature install
>
>
> Key: KARAF-3475
> URL: https://issues.apache.org/jira/browse/KARAF-3475
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 3.0.2
>Reporter: Frank Diebolt
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.4
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> Hi,
> I successfully tested the fix below :
> In the source file
> features/core/src/main/java/org/apache/karaf/features/internal/BundleManager.java
> protected void refreshPackages(Collection bundles) {
> final Object refreshLock = new Object();
> -FrameworkWiring wiring =
> bundleContext.getBundle().adapt(FrameworkWiring.class);
> +FrameworkWiring wiring =
> bundleContext.getBundle(0).adapt(FrameworkWiring.class);
> Currently wiring is always null, FrameworkWiring can be obtained on bundle 0
> only.
> BR
> Frank
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-3416) AutoEncryptionSupport randomly raises NullPointerException at startup
[
https://issues.apache.org/jira/browse/KARAF-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-3416.
-
Resolution: Duplicate
> AutoEncryptionSupport randomly raises NullPointerException at startup
> -
>
> Key: KARAF-3416
> URL: https://issues.apache.org/jira/browse/KARAF-3416
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core, karaf-security
>Affects Versions: 4.0.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.0.0, 4.0.0.M2
>
>
> Sometime (not always), at startup, we can see:
> {code}
> Exception in thread "AutoEncryptionSupport" java.lang.NullPointerException
> at sun.nio.fs.UnixPath.register(UnixPath.java:893)
> at sun.nio.fs.AbstractPath.register(AbstractPath.java:104)
> at
> org.apache.karaf.jaas.modules.properties.AutoEncryptionSupport.run(AutoEncryptionSupport.java:79)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-3475) No refresh of bundles during feature install
[
https://issues.apache.org/jira/browse/KARAF-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-3475.
-
Resolution: Fixed
> No refresh of bundles during feature install
>
>
> Key: KARAF-3475
> URL: https://issues.apache.org/jira/browse/KARAF-3475
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 3.0.2
>Reporter: Frank Diebolt
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.3
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> Hi,
> I successfully tested the fix below :
> In the source file
> features/core/src/main/java/org/apache/karaf/features/internal/BundleManager.java
> protected void refreshPackages(Collection bundles) {
> final Object refreshLock = new Object();
> -FrameworkWiring wiring =
> bundleContext.getBundle().adapt(FrameworkWiring.class);
> +FrameworkWiring wiring =
> bundleContext.getBundle(0).adapt(FrameworkWiring.class);
> Currently wiring is always null, FrameworkWiring can be obtained on bundle 0
> only.
> BR
> Frank
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3366) Generate a non-default password on first startup
[ https://issues.apache.org/jira/browse/KARAF-3366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3366: Fix Version/s: (was: 3.0.3) 3.0.4 > Generate a non-default password on first startup > > > Key: KARAF-3366 > URL: https://issues.apache.org/jira/browse/KARAF-3366 > Project: Karaf > Issue Type: Wish > Components: karaf-security >Affects Versions: 3.0.2 >Reporter: Robert Varga >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.4 > > > In OpenDaylight we rely on Karaf as our pre-packaged download, which has the > slight caveat that non-customized downloads can easily be vulnerable if users > enable ssh with the default password. > It would be nice if the startup script could generate a random password for > root, so the installation is secure by default. Not sure what the impact will > be on usability, though. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3416) AutoEncryptionSupport randomly raises NullPointerException at startup
[
https://issues.apache.org/jira/browse/KARAF-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3416:
Affects Version/s: (was: 3.0.2)
> AutoEncryptionSupport randomly raises NullPointerException at startup
> -
>
> Key: KARAF-3416
> URL: https://issues.apache.org/jira/browse/KARAF-3416
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core, karaf-security
>Affects Versions: 4.0.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.0.0, 4.0.0.M2
>
>
> Sometime (not always), at startup, we can see:
> {code}
> Exception in thread "AutoEncryptionSupport" java.lang.NullPointerException
> at sun.nio.fs.UnixPath.register(UnixPath.java:893)
> at sun.nio.fs.AbstractPath.register(AbstractPath.java:104)
> at
> org.apache.karaf.jaas.modules.properties.AutoEncryptionSupport.run(AutoEncryptionSupport.java:79)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3416) AutoEncryptionSupport randomly raises NullPointerException at startup
[
https://issues.apache.org/jira/browse/KARAF-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3416:
Fix Version/s: (was: 3.0.3)
4.0.0.M2
> AutoEncryptionSupport randomly raises NullPointerException at startup
> -
>
> Key: KARAF-3416
> URL: https://issues.apache.org/jira/browse/KARAF-3416
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core, karaf-security
>Affects Versions: 4.0.0
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
>Priority: Minor
> Fix For: 4.0.0, 4.0.0.M2
>
>
> Sometime (not always), at startup, we can see:
> {code}
> Exception in thread "AutoEncryptionSupport" java.lang.NullPointerException
> at sun.nio.fs.UnixPath.register(UnixPath.java:893)
> at sun.nio.fs.AbstractPath.register(AbstractPath.java:104)
> at
> org.apache.karaf.jaas.modules.properties.AutoEncryptionSupport.run(AutoEncryptionSupport.java:79)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (KARAF-3432) Be able to log console err/out
[ https://issues.apache.org/jira/browse/KARAF-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-3432. - Resolution: Fixed > Be able to log console err/out > -- > > Key: KARAF-3432 > URL: https://issues.apache.org/jira/browse/KARAF-3432 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.3 > > > When used especially in the cloud (or docker.io), it would be great to enable > logging of console (local and/or ssh). > Actually, I already have something working, by implementing a stream > interceptor. > I'm adding some properties (in etc/org.apache.karaf.shell.cfg) allowing: > - to enable it or not (to use the interceptor or not) for local and/or ssh > console > - to define the logger name > - to define the log level -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3426) Deploy Kar Snapshots
[ https://issues.apache.org/jira/browse/KARAF-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3426: Fix Version/s: (was: 3.0.3) 3.0.4 > Deploy Kar Snapshots > > > Key: KARAF-3426 > URL: https://issues.apache.org/jira/browse/KARAF-3426 > Project: Karaf > Issue Type: Improvement > Components: karaf-kar >Affects Versions: 3.0.2 >Reporter: Brad Hoffman >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.4 > > > I'd like to be able to re-deploy a kar file containing bundles with snapshot > versions. > The kar extraction seems to work properly however the local maven repository > that resolves the extracted bundles from the kar do not contain > maven-metadata.xml files and therefore local maven repository will only ever > contain the first snapshot bundles. > As a workaround my current process involves removing snapshot entries from my > local maven repository so that subsequent kar deployments install the > intended bundles. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (KARAF-3475) No refresh of bundles during feature install
[
https://issues.apache.org/jira/browse/KARAF-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reopened KARAF-3475:
-
> No refresh of bundles during feature install
>
>
> Key: KARAF-3475
> URL: https://issues.apache.org/jira/browse/KARAF-3475
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 3.0.2
>Reporter: Frank Diebolt
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.3
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> Hi,
> I successfully tested the fix below :
> In the source file
> features/core/src/main/java/org/apache/karaf/features/internal/BundleManager.java
> protected void refreshPackages(Collection bundles) {
> final Object refreshLock = new Object();
> -FrameworkWiring wiring =
> bundleContext.getBundle().adapt(FrameworkWiring.class);
> +FrameworkWiring wiring =
> bundleContext.getBundle(0).adapt(FrameworkWiring.class);
> Currently wiring is always null, FrameworkWiring can be obtained on bundle 0
> only.
> BR
> Frank
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3432) Be able to log console err/out
[ https://issues.apache.org/jira/browse/KARAF-3432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3432: Fix Version/s: (was: 4.0.0) > Be able to log console err/out > -- > > Key: KARAF-3432 > URL: https://issues.apache.org/jira/browse/KARAF-3432 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 3.0.3 > > > When used especially in the cloud (or docker.io), it would be great to enable > logging of console (local and/or ssh). > Actually, I already have something working, by implementing a stream > interceptor. > I'm adding some properties (in etc/org.apache.karaf.shell.cfg) allowing: > - to enable it or not (to use the interceptor or not) for local and/or ssh > console > - to define the logger name > - to define the log level -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3475) No refresh of bundles during feature install
[
https://issues.apache.org/jira/browse/KARAF-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3475:
Fix Version/s: 4.0.0
> No refresh of bundles during feature install
>
>
> Key: KARAF-3475
> URL: https://issues.apache.org/jira/browse/KARAF-3475
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 3.0.2
>Reporter: Frank Diebolt
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.3
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> Hi,
> I successfully tested the fix below :
> In the source file
> features/core/src/main/java/org/apache/karaf/features/internal/BundleManager.java
> protected void refreshPackages(Collection bundles) {
> final Object refreshLock = new Object();
> -FrameworkWiring wiring =
> bundleContext.getBundle().adapt(FrameworkWiring.class);
> +FrameworkWiring wiring =
> bundleContext.getBundle(0).adapt(FrameworkWiring.class);
> Currently wiring is always null, FrameworkWiring can be obtained on bundle 0
> only.
> BR
> Frank
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (KARAF-3475) No refresh of bundles during feature install
[
https://issues.apache.org/jira/browse/KARAF-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-3475:
Fix Version/s: (was: 4.0.0)
> No refresh of bundles during feature install
>
>
> Key: KARAF-3475
> URL: https://issues.apache.org/jira/browse/KARAF-3475
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
>Affects Versions: 3.0.2
>Reporter: Frank Diebolt
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.3
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> Hi,
> I successfully tested the fix below :
> In the source file
> features/core/src/main/java/org/apache/karaf/features/internal/BundleManager.java
> protected void refreshPackages(Collection bundles) {
> final Object refreshLock = new Object();
> -FrameworkWiring wiring =
> bundleContext.getBundle().adapt(FrameworkWiring.class);
> +FrameworkWiring wiring =
> bundleContext.getBundle(0).adapt(FrameworkWiring.class);
> Currently wiring is always null, FrameworkWiring can be obtained on bundle 0
> only.
> BR
> Frank
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (KARAF-3479) CLONE - Be able to log console err/out
Jean-Baptiste Onofré created KARAF-3479: --- Summary: CLONE - Be able to log console err/out Key: KARAF-3479 URL: https://issues.apache.org/jira/browse/KARAF-3479 Project: Karaf Issue Type: New Feature Components: karaf-shell Reporter: Jean-Baptiste Onofré Assignee: Jean-Baptiste Onofré Fix For: 4.0.0, 3.0.3 When used especially in the cloud (or docker.io), it would be great to enable logging of console (local and/or ssh). Actually, I already have something working, by implementing a stream interceptor. I'm adding some properties (in etc/org.apache.karaf.shell.cfg) allowing: - to enable it or not (to use the interceptor or not) for local and/or ssh console - to define the logger name - to define the log level -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KARAF-3479) CLONE - Be able to log console err/out
[ https://issues.apache.org/jira/browse/KARAF-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-3479: Fix Version/s: (was: 3.0.3) > CLONE - Be able to log console err/out > -- > > Key: KARAF-3479 > URL: https://issues.apache.org/jira/browse/KARAF-3479 > Project: Karaf > Issue Type: New Feature > Components: karaf-shell >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0 > > > When used especially in the cloud (or docker.io), it would be great to enable > logging of console (local and/or ssh). > Actually, I already have something working, by implementing a stream > interceptor. > I'm adding some properties (in etc/org.apache.karaf.shell.cfg) allowing: > - to enable it or not (to use the interceptor or not) for local and/or ssh > console > - to define the logger name > - to define the log level -- This message was sent by Atlassian JIRA (v6.3.4#6332)
