[jira] [Created] (KARAF-2890) The env variables can't be read while running karaf as a Linux service
Xilai Dai created KARAF-2890:
Summary: The env variables can't be read while running karaf as a
Linux service
Key: KARAF-2890
URL: https://issues.apache.org/jira/browse/KARAF-2890
Project: Karaf
Issue Type: Bug
Affects Versions: 2.3.3
Reporter: Xilai Dai
Install karaf as a Linux service following steps:
1. features:install wrapper
2. wrapper:install -s AUTO_START -n talend-runtime -d talend-runtime -D "Talend
Runtime Service"
$ ln -s /Talend/runtime/bin/talend-runtime-service /etc/init.d/talend-runtime
the fragment from generated script:
{code}
# Still want to change users, recurse. This means that the user will only be
# prompted for a password once.
su -m $RUN_AS_USER -s /bin/sh -c "$REALPATH $1"
{code}
it should be:
{code}
# Still want to change users, recurse. This means that the user will only be
# prompted for a password once.
su - -m $RUN_AS_USER -c "$REALPATH $1"
{code}
Because the user login script (.bash_profile) can't be executed without '-'
after 'su'; and '-s /bin/sh' is not standard, the default shell of the run_as
user (e.g. bash) should be used.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[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: 2.3.5)
(was: 3.0.1)
2.3.6
3.0.2
> 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: 2.4.0, 4.0.0, 3.0.2, 2.3.6
>
>
> 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.2#6252)
[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.1)
3.0.2
4.0.0
> 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.2
>
>
> 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.2#6252)
[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.1)
3.0.2
4.0.0
> 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.2
>
>
> 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.2#6252)
[jira] [Resolved] (KARAF-2592) Keystrokes messed up after exiting log:tail with many exceptions being thrown
[ https://issues.apache.org/jira/browse/KARAF-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-2592. - Resolution: Cannot Reproduce I close this Jira for now. Please re-open it if you encounter the issue again. > Keystrokes messed up after exiting log:tail with many exceptions being thrown > - > > Key: KARAF-2592 > URL: https://issues.apache.org/jira/browse/KARAF-2592 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 3.0.0.RC1 > Environment: Linux / Java 1.7 >Reporter: Steven Whyte >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 3.0.1 > > > When I go into the shell and tail the log karaf@root()>log:tail and if there > are many exceptions, once I return out of the command, my keystrokes are > messed up where as I have to hit each key twice to get a single character. > Once I exit (if running the client) and come back in it works fine unless > tail the log again. -- This message was sent by Atlassian JIRA (v6.2#6252)
[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: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 4.0.0 > 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: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > > 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.2#6252)
[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: 4.0.0 > 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.2 > > > 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.2#6252)
[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.1) 3.0.2 > 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é >Priority: Blocker > Fix For: 3.0.2 > > > 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.2#6252)
[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: Priority: Major (was: Blocker) > 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: 3.0.2 > > > 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.2#6252)
[jira] [Resolved] (KARAF-2506) MBeans attributes are "unavailable"
[ https://issues.apache.org/jira/browse/KARAF-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-2506. - Resolution: Not a Problem Now the documentation specifies to use the JMX service URL to connect to Karaf (even locally, instead of use the Process ID). > MBeans attributes are "unavailable" > --- > > Key: KARAF-2506 > URL: https://issues.apache.org/jira/browse/KARAF-2506 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 3.0.1, 4.0.0 > > > Running Karaf 3.0.0-SNAPSHOT (trunk), and connecting jconsole, all Karaf > MBeans attributes are displayed as "unavailable" in red. > It's the case for: > - bundles in org.apache.karaf:type=bundle > - configs in org.apache.karaf:type=config > - features and repositories in org.apache.karaf:type=feature > - instances in org.apache.karaf:type=instances > - kars in org.apache.karaf:type=kar > - level in org.apache.karaf:type=log > - exports and imports in org.apache.karaf:type=package > - services in org.apache.karaf:type=service > - all attributes in org.apache.karaf:type=system > I'm checking if it's not some ACLs missing (as the JMX ACL check attributes > using some operations name like get/set/is). -- This message was sent by Atlassian JIRA (v6.2#6252)
[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: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 4.0.0 > 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: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > > 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.2#6252)
[jira] [Updated] (KARAF-2506) MBeans attributes are "unavailable"
[ https://issues.apache.org/jira/browse/KARAF-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2506: Fix Version/s: 4.0.0 > MBeans attributes are "unavailable" > --- > > Key: KARAF-2506 > URL: https://issues.apache.org/jira/browse/KARAF-2506 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Critical > Fix For: 3.0.1, 4.0.0 > > > Running Karaf 3.0.0-SNAPSHOT (trunk), and connecting jconsole, all Karaf > MBeans attributes are displayed as "unavailable" in red. > It's the case for: > - bundles in org.apache.karaf:type=bundle > - configs in org.apache.karaf:type=config > - features and repositories in org.apache.karaf:type=feature > - instances in org.apache.karaf:type=instances > - kars in org.apache.karaf:type=kar > - level in org.apache.karaf:type=log > - exports and imports in org.apache.karaf:type=package > - services in org.apache.karaf:type=service > - all attributes in org.apache.karaf:type=system > I'm checking if it's not some ACLs missing (as the JMX ACL check attributes > using some operations name like get/set/is). -- This message was sent by Atlassian JIRA (v6.2#6252)
[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: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 4.0.0 > 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: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > > 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.2#6252)
[jira] [Updated] (KARAF-2481) LogService WebConsole view doesn't work with Equinox
[ https://issues.apache.org/jira/browse/KARAF-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2481: Fix Version/s: (was: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > LogService WebConsole view doesn't work with Equinox > > > Key: KARAF-2481 > URL: https://issues.apache.org/jira/browse/KARAF-2481 > Project: Karaf > Issue Type: Bug > Components: karaf-webconsole >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.2, 2.3.6 > > > Using Felix OSGi framework, the WebConsole Log Service page displays the log > messages. > However, when using Equinox OSGi framework, nothing is displayed in the Log > Service page. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2453) Using features to extend existing configuration
[ https://issues.apache.org/jira/browse/KARAF-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2453: Fix Version/s: (was: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > Using features to extend existing configuration > --- > > Key: KARAF-2453 > URL: https://issues.apache.org/jira/browse/KARAF-2453 > Project: Karaf > Issue Type: Improvement > Components: karaf-config, karaf-feature >Reporter: Jan Bernhardt >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 2.4.0, 3.0.2, 2.3.6 > > > for me it looks like that there is currently no way to extend an existing > configuration file by installing a feature. But this is, what I would need > for my use case and what would be great IMHO for other users as well. > Here is my idea. > If a property already exists within a configuration file this property should > not be changed. But if a configuration file does not contain a certain key, > this key=value should be added at the end of the configuration file. > Example: > > myProperty = myValue > > If com.foo.bar.cfg does not contain myProperty before the feature containing > this example was installed, then myProperty=myValue should be added to > com.foo.bar.cfg file. > This would make it possible to extend existing configuration files for custom > needs. A general use-case could be logging. My application would like to add > a logger configuration in case this logger is not configured already. > 2. Example > > log4j.logger.org.apache.activemq.broker.util.LoggingBrokerPlugin=INFO, > stdout, osgi:VmLogAppender > -- This message was sent by Atlassian JIRA (v6.2#6252)
[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: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > 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: 2.4.0, 3.0.2, 2.3.6 > > > 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.2#6252)
[jira] [Updated] (KARAF-2315) The check for jvm.dll happens to early in the bat file
[ https://issues.apache.org/jira/browse/KARAF-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2315: Fix Version/s: (was: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > The check for jvm.dll happens to early in the bat file > -- > > Key: KARAF-2315 > URL: https://issues.apache.org/jira/browse/KARAF-2315 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.3.2, 2.4.0, 3.0.0 >Reporter: Heath Kesler >Assignee: Jean-Baptiste Onofré >Priority: Minor > Fix For: 2.4.0, 3.0.2, 2.3.6 > > > When running karaf without JAVA_HOME set, but having the JDK installed > returns the following warning: > WARNING: Running karaf on a Java HotSpot Client VM because server-mode is not > av > ailable. > Install Java Developer Kit to fix this. > For more details see > http://java.sun.com/products/hotspot/whitepaper.html#client > But since the JDK is installed and found via a reg query, karaf will still > startup. I think this check should be moved to after the JAVA_HOME > validation is done to avoid this warning. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2367) Config Not Released When Declarative Services Bundle Stopped
[ https://issues.apache.org/jira/browse/KARAF-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2367: Fix Version/s: (was: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > Config Not Released When Declarative Services Bundle Stopped > > > Key: KARAF-2367 > URL: https://issues.apache.org/jira/browse/KARAF-2367 > Project: Karaf > Issue Type: Bug > Components: karaf-config >Affects Versions: 2.3.1 >Reporter: Gareth Collins >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.2, 2.3.6 > > > If I have a declarative services bundle which has config associated with it. > i.e.: > karaf@root> list -t 0 -s | grep myservice > [ 234] [Active ] [] [ 80] com.mycompany.myservice > (1.0.0.20130530-jenkins-383) > karaf@root> config:list "(service.pid=com.mycompany.myservice)" > > Pid:com.mycompany.myservice > BundleLocation: mvn:com.mycompany/myservice/1.0.0-SNAPSHOT > Properties: > . > . > If I stop or uninstall this bundle, the config does not get released: > karaf@root> stop 234 > karaf@root> config:list "(service.pid=com.mycompany.myservice)" > > Pid:com.mycompany.myservice > BundleLocation: mvn:com.mycompany/myservice/1.0.0-SNAPSHOT > Properties: > . > . > This is problematic because it stops you from uninstalling the bundle and > installing a new bundle at a new location which will reuse the config. To get > around this issue I currently must delete the old config and recreate it. > This problem persists across karaf restarts. > I know I can also do this: > karaf@root> update 234 > But that doesn't always work (once I can reproduce this "update" failure > consistently, I will open another defect) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2295) features deployer is useless for dynamic updates
[ https://issues.apache.org/jira/browse/KARAF-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2295: Fix Version/s: (was: 3.0.1) 3.0.2 4.0.0 > features deployer is useless for dynamic updates > > > Key: KARAF-2295 > URL: https://issues.apache.org/jira/browse/KARAF-2295 > Project: Karaf > Issue Type: Bug > Components: karaf-feature >Affects Versions: 3.0.0.RC1 >Reporter: Andrei Pozolotin >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.2 > > > use cases which do not work: > suppose old and new repository contain overlapping set of bundles. > 1) same name, new version: > a) install > * drop repo-1.0-features.xml > b) update > * kill repo-1.0-features.xml > * drop repo-1.1-features.xml > 2) same name, no version: > a) install > * drop repo-features.xml > b) update > * drop repo-features.xml > result: total corruption of repository, feature, bundle install state > workaround: clean bundle cache, restart karaf. > description why it does not work: > https://github.com/barchart/barchart-service/wiki/Features-Problems > re-implementation of features deployer > https://github.com/barchart/barchart-karaf-deployer-features -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2301) Improve shell syntax documentation
[
https://issues.apache.org/jira/browse/KARAF-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2301:
Fix Version/s: (was: 2.4.0)
> Improve shell syntax documentation
> --
>
> Key: KARAF-2301
> URL: https://issues.apache.org/jira/browse/KARAF-2301
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-documentation
>Reporter: Alan Foster
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.1, 4.0.0
>
>
> It would be nice if there were more examples within the karaf documentation
> for using the shell language.
> This documentation should be available within the 'help' command too if
> possible
> For instance, there is currently no example of how the 'each' command works.
> {code}
> karaf@root> list = [1 2 3]; each ($list) { echo $it }
> 1
> 2
> 3
> {code}
> There is no mention of whether there support for returning/breaking early in
> the each command either. After checking the source it doesn't appear to be
> possible, but it would be nice to mention such a thing.
> It would also be nice to show that the '[]' notation used will actually
> create an instance of java ArrayList, and as such you can perform 'get' on it
> to access values
> {code}
> karaf@root> list = ["Hello" world]; echo ($list get 0) ($list get 1)
> Hello world
> {code}
> And that you can actually see the class implementation details with '[] class'
> It would be nice to show if there is a way to access primitive array types
> too. And if this isn't possible, it might be nice to add that information
> {code}
> karaf@root> ("hello world" toCharArray)[0]
> Error executing command: [C cannot be cast to [Ljava.lang.Object;
> {code}
> It would nice to stress the importance of spaces in the shell language too,
> as I imagine that would be a very common gotcha
> ie happy path if statement working as expected
> {code:title=script.txt}
> foo = "foo"
> if { $foo equals "foo" } {
> echo "True!"
> }
> {code}
> {code}
> karaf@root> shell:source script.txt
> True!
> {code}
> But without a space between the 'if' ie {code}if{ $foo equals "foo" } {'{code}
> Then you get the following error, and it's very hard to tell what has gone
> wrong
> {code}
> karaf@root> shell:source script.txt
> Error executing command: Cannot coerce echo "true!"() to any of []
> {code}
> I am happy to help with this documentation update, as I've currently got a
> small amount of knowledge on the subject
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (KARAF-2301) Improve shell syntax documentation
[
https://issues.apache.org/jira/browse/KARAF-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-2301.
-
Resolution: Fixed
> Improve shell syntax documentation
> --
>
> Key: KARAF-2301
> URL: https://issues.apache.org/jira/browse/KARAF-2301
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-documentation
>Reporter: Alan Foster
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.2
>
>
> It would be nice if there were more examples within the karaf documentation
> for using the shell language.
> This documentation should be available within the 'help' command too if
> possible
> For instance, there is currently no example of how the 'each' command works.
> {code}
> karaf@root> list = [1 2 3]; each ($list) { echo $it }
> 1
> 2
> 3
> {code}
> There is no mention of whether there support for returning/breaking early in
> the each command either. After checking the source it doesn't appear to be
> possible, but it would be nice to mention such a thing.
> It would also be nice to show that the '[]' notation used will actually
> create an instance of java ArrayList, and as such you can perform 'get' on it
> to access values
> {code}
> karaf@root> list = ["Hello" world]; echo ($list get 0) ($list get 1)
> Hello world
> {code}
> And that you can actually see the class implementation details with '[] class'
> It would be nice to show if there is a way to access primitive array types
> too. And if this isn't possible, it might be nice to add that information
> {code}
> karaf@root> ("hello world" toCharArray)[0]
> Error executing command: [C cannot be cast to [Ljava.lang.Object;
> {code}
> It would nice to stress the importance of spaces in the shell language too,
> as I imagine that would be a very common gotcha
> ie happy path if statement working as expected
> {code:title=script.txt}
> foo = "foo"
> if { $foo equals "foo" } {
> echo "True!"
> }
> {code}
> {code}
> karaf@root> shell:source script.txt
> True!
> {code}
> But without a space between the 'if' ie {code}if{ $foo equals "foo" } {'{code}
> Then you get the following error, and it's very hard to tell what has gone
> wrong
> {code}
> karaf@root> shell:source script.txt
> Error executing command: Cannot coerce echo "true!"() to any of []
> {code}
> I am happy to help with this documentation update, as I've currently got a
> small amount of knowledge on the subject
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (KARAF-2301) Improve shell syntax documentation
[
https://issues.apache.org/jira/browse/KARAF-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2301:
Fix Version/s: (was: 3.0.2)
3.0.1
> Improve shell syntax documentation
> --
>
> Key: KARAF-2301
> URL: https://issues.apache.org/jira/browse/KARAF-2301
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-documentation
>Reporter: Alan Foster
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.1, 4.0.0
>
>
> It would be nice if there were more examples within the karaf documentation
> for using the shell language.
> This documentation should be available within the 'help' command too if
> possible
> For instance, there is currently no example of how the 'each' command works.
> {code}
> karaf@root> list = [1 2 3]; each ($list) { echo $it }
> 1
> 2
> 3
> {code}
> There is no mention of whether there support for returning/breaking early in
> the each command either. After checking the source it doesn't appear to be
> possible, but it would be nice to mention such a thing.
> It would also be nice to show that the '[]' notation used will actually
> create an instance of java ArrayList, and as such you can perform 'get' on it
> to access values
> {code}
> karaf@root> list = ["Hello" world]; echo ($list get 0) ($list get 1)
> Hello world
> {code}
> And that you can actually see the class implementation details with '[] class'
> It would be nice to show if there is a way to access primitive array types
> too. And if this isn't possible, it might be nice to add that information
> {code}
> karaf@root> ("hello world" toCharArray)[0]
> Error executing command: [C cannot be cast to [Ljava.lang.Object;
> {code}
> It would nice to stress the importance of spaces in the shell language too,
> as I imagine that would be a very common gotcha
> ie happy path if statement working as expected
> {code:title=script.txt}
> foo = "foo"
> if { $foo equals "foo" } {
> echo "True!"
> }
> {code}
> {code}
> karaf@root> shell:source script.txt
> True!
> {code}
> But without a space between the 'if' ie {code}if{ $foo equals "foo" } {'{code}
> Then you get the following error, and it's very hard to tell what has gone
> wrong
> {code}
> karaf@root> shell:source script.txt
> Error executing command: Cannot coerce echo "true!"() to any of []
> {code}
> I am happy to help with this documentation update, as I've currently got a
> small amount of knowledge on the subject
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (KARAF-2260) Overloaded put methord with List comment parameter in InstallKarMojo$CommentProperties
[
https://issues.apache.org/jira/browse/KARAF-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2260:
Fix Version/s: (was: 3.0.2)
3.0.1
> Overloaded put methord with List comment parameter in
> InstallKarMojo$CommentProperties
> --
>
> Key: KARAF-2260
> URL: https://issues.apache.org/jira/browse/KARAF-2260
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Affects Versions: 3.0.0
>Reporter: ChengRen
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.1, 4.0.0
>
>
> Caused by: java.lang.NoSuchMethodError:
> org.apache.karaf.tooling.features.InstallKarsMojo$CommentProperties.put(Ljava/lang/String;Ljava/util/List;Ljava/lang/String;)Ljava/lang/String;
> at
> org.apache.karaf.tooling.features.InstallKarsMojo$OfflineFeaturesService.installFeature(InstallKarsMojo.java:545)
> at
> org.apache.karaf.tooling.features.InstallKarsMojo$OfflineFeaturesService.addRepository(InstallKarsMojo.java:445)
> at
> org.apache.karaf.tooling.features.InstallKarsMojo.execute(InstallKarsMojo.java:224)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> ... 21 more
> **
> -public String put(String key, List commentLines, String
> value) {
> -commentLines = new ArrayList(commentLines);
> -layout.put(key, new Layout(commentLines, null));
> -return storage.put(key, value);
> -}
> **
> these code was removed from 3d9fefbba68e9c24795238b9d38c20b93b308d82
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (KARAF-2260) Overloaded put methord with List comment parameter in InstallKarMojo$CommentProperties
[
https://issues.apache.org/jira/browse/KARAF-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved KARAF-2260.
-
Resolution: Fixed
> Overloaded put methord with List comment parameter in
> InstallKarMojo$CommentProperties
> --
>
> Key: KARAF-2260
> URL: https://issues.apache.org/jira/browse/KARAF-2260
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Affects Versions: 3.0.0
>Reporter: ChengRen
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.1, 4.0.0
>
>
> Caused by: java.lang.NoSuchMethodError:
> org.apache.karaf.tooling.features.InstallKarsMojo$CommentProperties.put(Ljava/lang/String;Ljava/util/List;Ljava/lang/String;)Ljava/lang/String;
> at
> org.apache.karaf.tooling.features.InstallKarsMojo$OfflineFeaturesService.installFeature(InstallKarsMojo.java:545)
> at
> org.apache.karaf.tooling.features.InstallKarsMojo$OfflineFeaturesService.addRepository(InstallKarsMojo.java:445)
> at
> org.apache.karaf.tooling.features.InstallKarsMojo.execute(InstallKarsMojo.java:224)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> ... 21 more
> **
> -public String put(String key, List commentLines, String
> value) {
> -commentLines = new ArrayList(commentLines);
> -layout.put(key, new Layout(commentLines, null));
> -return storage.put(key, value);
> -}
> **
> these code was removed from 3d9fefbba68e9c24795238b9d38c20b93b308d82
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (KARAF-2301) Improve shell syntax documentation
[
https://issues.apache.org/jira/browse/KARAF-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2301:
Fix Version/s: (was: 3.0.1)
3.0.2
4.0.0
> Improve shell syntax documentation
> --
>
> Key: KARAF-2301
> URL: https://issues.apache.org/jira/browse/KARAF-2301
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-documentation
>Reporter: Alan Foster
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.1, 4.0.0
>
>
> It would be nice if there were more examples within the karaf documentation
> for using the shell language.
> This documentation should be available within the 'help' command too if
> possible
> For instance, there is currently no example of how the 'each' command works.
> {code}
> karaf@root> list = [1 2 3]; each ($list) { echo $it }
> 1
> 2
> 3
> {code}
> There is no mention of whether there support for returning/breaking early in
> the each command either. After checking the source it doesn't appear to be
> possible, but it would be nice to mention such a thing.
> It would also be nice to show that the '[]' notation used will actually
> create an instance of java ArrayList, and as such you can perform 'get' on it
> to access values
> {code}
> karaf@root> list = ["Hello" world]; echo ($list get 0) ($list get 1)
> Hello world
> {code}
> And that you can actually see the class implementation details with '[] class'
> It would be nice to show if there is a way to access primitive array types
> too. And if this isn't possible, it might be nice to add that information
> {code}
> karaf@root> ("hello world" toCharArray)[0]
> Error executing command: [C cannot be cast to [Ljava.lang.Object;
> {code}
> It would nice to stress the importance of spaces in the shell language too,
> as I imagine that would be a very common gotcha
> ie happy path if statement working as expected
> {code:title=script.txt}
> foo = "foo"
> if { $foo equals "foo" } {
> echo "True!"
> }
> {code}
> {code}
> karaf@root> shell:source script.txt
> True!
> {code}
> But without a space between the 'if' ie {code}if{ $foo equals "foo" } {'{code}
> Then you get the following error, and it's very hard to tell what has gone
> wrong
> {code}
> karaf@root> shell:source script.txt
> Error executing command: Cannot coerce echo "true!"() to any of []
> {code}
> I am happy to help with this documentation update, as I've currently got a
> small amount of knowledge on the subject
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[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.1)
3.0.2
> 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.2
>
> 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.2#6252)
[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: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > 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: 2.2.12, 2.4.0, 3.0.2, 2.3.6 > > > 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.2#6252)
[jira] [Updated] (KARAF-1894) Framework's active start level is set to org.osgi.framework.startlevel.beginning too early when launching Karaf with empty bundle cache
[ https://issues.apache.org/jira/browse/KARAF-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1894: Fix Version/s: (was: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > Framework's active start level is set to > org.osgi.framework.startlevel.beginning too early when launching Karaf with > empty bundle cache > --- > > Key: KARAF-1894 > URL: https://issues.apache.org/jira/browse/KARAF-1894 > Project: Karaf > Issue Type: Bug >Affects Versions: 2.2.9, 3.0.0 > Environment: Mac 10.8.2/Oracle JDK 1.6.0_35 >Reporter: Jason Montojo >Assignee: Jean-Baptiste Onofré > Fix For: 2.2.12, 2.4.0, 3.0.2, 2.3.6 > > Attachments: slbug.tar-3.0.gz, slbug.tar.gz > > > When launching Karaf 2.2.9 with an empty bundle cache, the framework's active > start level is already set to org.osgi.framework.startlevel.beginning before > all the boot features have been started. The impact is that bundles can be > loaded in the wrong order, and File Install ends up scanning the deploy > folder when it's not supposed to. > This is problematic because we're using boot features to load up our core > infrastructure and the deploy folder to host plugins. If we prepackage any > plugins with our product with an empty bundle cache, the plugins get > installed and started before the core. > The attached tarball contains a set of 3 bundles that reproduce the symptoms. > Simply untar within the apache-karaf-2.2.9 directory. > In the test tarball, there are 3 bundles that do the same thing. When > start() is called, they print out their name and the framework's current > start level, then wait for 1 second. > bundle1 (start-level=60) and bundle2 (start-level=80) are part of a boot > feature. However, bundle2 is listed first in the XML. bundle3 is in the > deploy directory. File Install is configured so that it doesn't scan until > start level 81 (via felix.fileinstall.active.level). > I'm expecting that the bundles are loaded in this order: bundle1, bundle2, > bundle3. > If I clear the bundle cache and start Karaf, I get the following output: > [bundle2] 100 > [bundle3] 100 > [bundle1] 100 > This indicates that when bundle2's start() is called, the framework's start > level is already set to org.osgi.framework.startlevel.beginning (in this > case, 100) before the boot features have started. > If I run Karaf again without clearing the bundle cache, I get the following: > [bundle1] 60 > [bundle2] 80 > [bundle3] 80 > This is better, but felix.fileinstall.active.level is set to 81, so bundle3 > should not be starting at start level 80. This is probably a separate issue. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2260) Overloaded put methord with List comment parameter in InstallKarMojo$CommentProperties
[
https://issues.apache.org/jira/browse/KARAF-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2260:
Fix Version/s: (was: 3.0.1)
3.0.2
> Overloaded put methord with List comment parameter in
> InstallKarMojo$CommentProperties
> --
>
> Key: KARAF-2260
> URL: https://issues.apache.org/jira/browse/KARAF-2260
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Affects Versions: 3.0.0
>Reporter: ChengRen
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.2
>
>
> Caused by: java.lang.NoSuchMethodError:
> org.apache.karaf.tooling.features.InstallKarsMojo$CommentProperties.put(Ljava/lang/String;Ljava/util/List;Ljava/lang/String;)Ljava/lang/String;
> at
> org.apache.karaf.tooling.features.InstallKarsMojo$OfflineFeaturesService.installFeature(InstallKarsMojo.java:545)
> at
> org.apache.karaf.tooling.features.InstallKarsMojo$OfflineFeaturesService.addRepository(InstallKarsMojo.java:445)
> at
> org.apache.karaf.tooling.features.InstallKarsMojo.execute(InstallKarsMojo.java:224)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> ... 21 more
> **
> -public String put(String key, List commentLines, String
> value) {
> -commentLines = new ArrayList(commentLines);
> -layout.put(key, new Layout(commentLines, null));
> -return storage.put(key, value);
> -}
> **
> these code was removed from 3d9fefbba68e9c24795238b9d38c20b93b308d82
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[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: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > 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.0, 3.0.2, 2.3.6 > > 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.2#6252)
[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.1)
3.0.2
4.0.0
> 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.2
>
>
> 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.2#6252)
[jira] [Updated] (KARAF-1553) Command service references should be AUTO_EXPORT_INTERFACES
[ https://issues.apache.org/jira/browse/KARAF-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1553: Fix Version/s: 4.0.0 > Command service references should be AUTO_EXPORT_INTERFACES > --- > > Key: KARAF-1553 > URL: https://issues.apache.org/jira/browse/KARAF-1553 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Reporter: Daniel Kulp >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.2 > > Attachments: patch.txt > > > When the command NamespaceHandler parses commands, it currently sets the > MutableServiceMetadata commandService to have > ServiceMetadata.AUTO_EXPORT_ALL_CLASSES. This causes the proxying to use > the ASM based subclass proxies. > Most likely, it should use either: > commandService.setAutoExport(ServiceMetadata.AUTO_EXPORT_INTERFACES); > or specifically set the interface names to proxy on the > MutableServiceMetadata via addInterface. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-1553) Command service references should be AUTO_EXPORT_INTERFACES
[ https://issues.apache.org/jira/browse/KARAF-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1553: Fix Version/s: (was: 3.0.1) 3.0.2 > Command service references should be AUTO_EXPORT_INTERFACES > --- > > Key: KARAF-1553 > URL: https://issues.apache.org/jira/browse/KARAF-1553 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Reporter: Daniel Kulp >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.2 > > Attachments: patch.txt > > > When the command NamespaceHandler parses commands, it currently sets the > MutableServiceMetadata commandService to have > ServiceMetadata.AUTO_EXPORT_ALL_CLASSES. This causes the proxying to use > the ASM based subclass proxies. > Most likely, it should use either: > commandService.setAutoExport(ServiceMetadata.AUTO_EXPORT_INTERFACES); > or specifically set the interface names to proxy on the > MutableServiceMetadata via addInterface. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-1545) Jar files in lib directory require "karaf-" prefix in order to be loaded
[ https://issues.apache.org/jira/browse/KARAF-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1545: Fix Version/s: (was: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > Jar files in lib directory require "karaf-" prefix in order to be loaded > > > Key: KARAF-1545 > URL: https://issues.apache.org/jira/browse/KARAF-1545 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 2.2.2 > Environment: Java version: 1.6.0_32, vendor: Sun Microsystems Inc. > Java home: /home/jcarman/Programs/jdk1.6.0_32/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "3.2.0-24-generic", arch: "amd64", family: "unix" >Reporter: James Carman >Assignee: Jean-Baptiste Onofré > Fix For: 2.2.12, 2.4.0, 3.0.2, 2.3.6 > > Attachments: karaf-3.0_1545.diff > > > I was trying to configure JDBC fail-over, so I put my mysql driver jar in the > KARAF_HOME/lib directory. I kept getting ClassNotFoundExceptions. On the > advice of someone on IRC, I changed the name to > "karaf-mysql-connector-java.jar" and it started working. Why the karaf- > prefix requirement? If that's the intended behavior, then please update the > README file in the lib directory. It says: > "Any jar in this folder will be part of the main classloader used to load > Karaf." -- This message was sent by Atlassian JIRA (v6.2#6252)
[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.1)
3.0.2
4.0.0
> 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.2
>
>
> 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_ba3
[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.1)
3.0.2
> 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.2
>
> 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.2#6252)
[jira] [Updated] (KARAF-1246) add a version checker for karaf start script
[ https://issues.apache.org/jira/browse/KARAF-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1246: Fix Version/s: (was: 3.0.1) 3.0.2 > add a version checker for karaf start script > > > Key: KARAF-1246 > URL: https://issues.apache.org/jira/browse/KARAF-1246 > Project: Karaf > Issue Type: Bug > Components: karaf-core >Affects Versions: 3.0.0 >Reporter: Andreas Pieber >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.2 > > Attachments: 0001-Fix-checkJvmVersion-egrep-pattern.patch > > > Since the upcoming 3.0 release of Karaf is designed to consume JRE6 as > minimum version we should make it possible to give a user who's still using > JRE5 a proper message. > This issue is similar to SM-2135 (which also has a possible solution attached) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-1250) Cleanup karaf-maven-plugin
[ https://issues.apache.org/jira/browse/KARAF-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1250: Fix Version/s: (was: 3.0.1) 3.0.2 > Cleanup karaf-maven-plugin > -- > > Key: KARAF-1250 > URL: https://issues.apache.org/jira/browse/KARAF-1250 > Project: Karaf > Issue Type: Improvement > Components: karaf-tooling >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.2 > > > Some refactoring and cleanup should be performed in the karaf-maven-plugin > (and assemblies) and some documentation should be provided about the exact > behavior of the different goals. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-1018) using auto-complete (TAB key) on commands that don't take Arguments/Options throws IndexOutOfBoundsException.
[ https://issues.apache.org/jira/browse/KARAF-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-1018: Fix Version/s: (was: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > using auto-complete (TAB key) on commands that don't take Arguments/Options > throws IndexOutOfBoundsException. > -- > > Key: KARAF-1018 > URL: https://issues.apache.org/jira/browse/KARAF-1018 > Project: Karaf > Issue Type: Bug > Components: karaf-shell >Affects Versions: 2.2.4 > Environment: Java 1.6.029 on a Windows environment. >Reporter: Adam Lavie >Assignee: Jean-Baptiste Onofré >Priority: Minor > Labels: CompleterValues, TAB, autocomplete, completer > Fix For: 3.0.2, 2.3.6 > > Attachments: Shell.jpg, doSomething.java > > > When using the TAB auto-complete key after commands that do not take any > Arguments/Options, > a message is printed saying "Error executing command: -1". > The shell then becomes unresponsive and the TAB auto-complete option is > inactive. -- This message was sent by Atlassian JIRA (v6.2#6252)
[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.1)
3.0.2
> 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.2
>
>
> 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.2#6252)
[jira] [Updated] (KARAF-526) add-features-to-repo: descriptor with file contains spaces on unix
[
https://issues.apache.org/jira/browse/KARAF-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-526:
---
Fix Version/s: (was: 3.0.1)
3.0.2
> add-features-to-repo: descriptor with file contains spaces on unix
> --
>
> Key: KARAF-526
> URL: https://issues.apache.org/jira/browse/KARAF-526
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature, karaf-tooling
>Affects Versions: 2.1.4
> Environment: unix
>Reporter: Alexey Markevich
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.2
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Configuration:
> org.apache.karaf.tooling
> features-maven-plugin
>
>
>
> add-features-to-repo
>
>
>
>
> file:${basedir}/target/classes/activemq-features.xml
> ${basedir} contains spaces at target PC. Result:
> Caused by: java.lang.IllegalArgumentException
> at java.net.URI.create(URI.java:842)
> at
> org.apache.karaf.tooling.features.AddFeaturesToRepoMojo.execute(AddFeaturesToRepoMojo.java:130)
> Looking into sources I found
> org.apache.karaf.tooling.features.MojoSupport.translateFromMaven()
> There is a check for windows and replacement spaces with %20.
> Simple fix:
> } else if (uri.startsWith("file:")) {
> if (System.getProperty("os.name").startsWith("Windows")) {
> String baseDir = uri.substring(5).replace('\\',
> '/').replaceAll(" ", "%20");
> String result = baseDir;
> if (baseDir.indexOf(":") > 0) {
> result = "file:///" + baseDir;
> }
> return result;
> } else {
> return uri.replaceAll(" ", "%20");
> }
> }
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[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: 2.3.5) 2.3.6 3.0.2 > 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: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > 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.2#6252)
[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.1) 3.0.2 > 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, 3.0.2 > > 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.2#6252)
[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: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > 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: 2.4.0, 3.0.2, 2.3.6 > > > 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.2#6252)
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13963128#comment-13963128 ] Jean-Baptiste Onofré commented on KARAF-222: As I have some conflicts to fix to merge my branches, and avoid to block the planned release, I will complete the merge just after 2.3.5 and 3.0.1. > 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: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > 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.2#6252)
[jira] [Updated] (KARAF-132) The user name for the main console session is always "karaf"
[
https://issues.apache.org/jira/browse/KARAF-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-132:
---
Fix Version/s: (was: 3.0.1)
3.0.2
> The user name for the main console session is always "karaf"
>
>
> Key: KARAF-132
> URL: https://issues.apache.org/jira/browse/KARAF-132
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 2.2.4
>Reporter: Guillaume Nodet
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.2
>
> Attachments: patchfile.txt
>
>
> See org.apache.karaf.shell.console.jline.ConsoleFactory#start
> {code}
> CommandSession session = console.getSession();
> session.put("USER", "karaf");
> session.put("APPLICATION", System.getProperty("karaf.name",
> "root"));
> session.put("LINES",
> Integer.toString(terminal.getTerminalHeight()));
> session.put("COLUMNS",
> Integer.toString(terminal.getTerminalWidth()));
> session.put(".jline.terminal", terminal);
> new Thread(console, "Karaf Shell Console Thread").start();
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[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.1)
3.0.2
> GenerateDescriptorMojo does not resolve conflicts
> -
>
> Key: KARAF-2630
> URL: https://issues.apache.org/jira/browse/KARAF-2630
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
>Affects Versions: 3.0.0.RC1
>Reporter: Maarten Winkels
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.2
>
> 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-SNAPSHOT
>
[jira] [Updated] (KARAF-2728) feature:install fails with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/KARAF-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2728:
Fix Version/s: (was: 3.0.1)
3.0.2
4.0.0
> feature:install fails with ArrayIndexOutOfBoundsException
> --
>
> Key: KARAF-2728
> URL: https://issues.apache.org/jira/browse/KARAF-2728
> Project: Karaf
> Issue Type: Bug
>Affects Versions: 3.0.0
>Reporter: Stefan Fussenegger
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.0.0, 3.0.2
>
>
> I can't install a feature generated by karaf-maven-plugin 3.0.0:
> {code}
> $ bin/karaf clean
> __ __
>/ //_/ __ _/ __/
> / ,< / __ `/ ___/ __ `/ /_
> / /| |/ /_/ / / / /_/ / __/
> /_/ |_|\__,_/_/ \__,_/_/
> Apache Karaf (3.0.0)
> Hit '' for a list of available commands
> and '[cmd] --help' for help on a specific command.
> Hit '' or type 'system:shutdown' or 'logout' to shutdown Karaf.
> karaf@root()> feature:repo-add
> mvn:at.molindo/some-feature/1.0.0-SNAPSHOT/xml/features
> Adding feature url mvn:at.molindo/some-feature/1.0.0-SNAPSHOT/xml/features
> karaf@root()> feature:install some-feature
> Error executing command: -1
> {code}
> The feature discriptor is pretty simple, containing a couple of Maven
> artifacts (one of which has the wrap: prefix)
> log:display shows this error:
> {code}
> 2014-01-23 17:25:48,181 | INFO | Local user karaf | FeaturesServiceImpl
> | 1 - org.apache.karaf.features.core - 3.0.0 | Installing feature
> some-feature 1.0.0-SNAPSHOT
> 2014-01-23 17:25:48,325 | ERROR | Local user karaf | ShellUtil
> | 47 - org.apache.karaf.shell.console - 3.0.0 | Exception caught
> while executing command
> java.lang.ArrayIndexOutOfBoundsException: -1
> at java.util.ArrayList.elementData(ArrayList.java:371)[:1.7.0_25]
> at java.util.ArrayList.remove(ArrayList.java:448)[:1.7.0_25]
> at
> org.apache.felix.framework.resolver.Candidates.prepare(Candidates.java:767)
> at
> org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:122)
> at
> org.apache.felix.framework.StatefulResolver.resolve(StatefulResolver.java:403)
> at
> org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3967)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:2037)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:955)
> at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:942)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:469)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(FeaturesServiceImpl.java:428)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:363)
> at
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeature(FeaturesServiceImpl.java:352)
> at Proxy870d27d9_70ea_4eb1_be8d_696af5256b1c.installFeature(Unknown
> Source)
> at
> org.apache.karaf.features.command.InstallFeatureCommand.doExecute(InstallFeatureCommand.java:62)
> at
> org.apache.karaf.features.command.FeaturesCommandSupport.doExecute(FeaturesCommandSupport.java:38)
> 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_25]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_25]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_25]
> 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.$BlueprintCommand1805556267.execute(Unknown
> Source)[47:org.apache.karaf.shell.console:3.0.0]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)[:1.7.0_25]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)[:1.7.0_25]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[:1.7.0_25]
> at java.lang.reflect.Method.invoke(Method.java:606)[:1.7.0_25]
> at
> org.apache.aries.proxy.impl.ProxyHandler$1.invoke(ProxyHandler
[jira] [Updated] (KARAF-2749) BundleSelector should be more "selective"
[ https://issues.apache.org/jira/browse/KARAF-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2749: Fix Version/s: 4.0.0 > BundleSelector should be more "selective" > - > > Key: KARAF-2749 > URL: https://issues.apache.org/jira/browse/KARAF-2749 > Project: Karaf > Issue Type: Improvement > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.1, 4.0.0, 2.3.5 > > > The bundle:* (or osgi:*) commands and the BundlesMBean/BundleMBean use a > BundleSelector. > It allows user to select a bundle: > - with the bundle ID > - with the bundle name or symbolic name > - with the bundle location > In the case of name/symbolic name or location, the BundleSelector supports > regex. Unfortunately, it uses Matcher.find() method which is "open" in the > selected bundles. > Matcher.match() is probably better. > I will check if we can always use match() or if an option would be better. -- This message was sent by Atlassian JIRA (v6.2#6252)
[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: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > 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: 2.4.0, 3.0.2, 2.3.6 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[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: 2.3.5)
(was: 3.0.1)
2.3.6
3.0.2
4.0.0
> 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: 2.4.0, 4.0.0, 3.0.2, 2.3.6
>
> 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.2#6252)
[jira] [Resolved] (KARAF-2680) Add new itests
[ https://issues.apache.org/jira/browse/KARAF-2680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-2680. - Resolution: Fixed > Add new itests > -- > > Key: KARAF-2680 > URL: https://issues.apache.org/jira/browse/KARAF-2680 > Project: Karaf > Issue Type: Test > Components: karaf-test >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.1 > > > We added a set of new features (especially enterprises), and commands (jndi, > jms, jdbc, etc), etc. > It would be great to improve our utests/itests coverage for all these new > features. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2656) Config service doesn't create a file in etc if it doesn't exist
[ https://issues.apache.org/jira/browse/KARAF-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2656: Fix Version/s: 4.0.0 > Config service doesn't create a file in etc if it doesn't exist > --- > > Key: KARAF-2656 > URL: https://issues.apache.org/jira/browse/KARAF-2656 > Project: Karaf > Issue Type: Bug > Components: karaf-config >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré >Priority: Blocker > Fix For: 2.4.0, 3.0.1, 4.0.0 > > > The config service doesn't create a file in etc if the file already exists. > Previously (in Karaf 2.x) we explicitely created the config file. Now we > delegate to ConfigAdmin persistence, but we don't provide any persistence > adapter. -- This message was sent by Atlassian JIRA (v6.2#6252)
[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: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 4.0.0 > 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: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > > 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.2#6252)
[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: Description: 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. was: A couple of users reported issues with noth 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. > 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: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > > 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.2#6252)
[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: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > Add samples in distribution > --- > > Key: KARAF-2735 > URL: https://issues.apache.org/jira/browse/KARAF-2735 > Project: Karaf > Issue Type: Improvement >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.2, 2.3.6 > > > 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.2#6252)
[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.1) 3.0.2 4.0.0 > 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, 3.0.2 > > > 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.2#6252)
[jira] [Updated] (KARAF-2725) jpa feature should install org.osgi.enterprise 5.0.0 bundle
[ https://issues.apache.org/jira/browse/KARAF-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2725: Fix Version/s: (was: 3.0.1) 3.0.2 4.0.0 > jpa feature should install org.osgi.enterprise 5.0.0 bundle > --- > > Key: KARAF-2725 > URL: https://issues.apache.org/jira/browse/KARAF-2725 > Project: Karaf > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 4.0.0, 3.0.2 > > > The aries-jpa-container requires the org.osgi.service.jdbc package. > With OSGi 4.3.0, the org.osgi.service.jdbc package is in compendium. > But with OSGi 5.0.0, it's now in enterprise. > So, the jpa feature should install the org.osgi.enterprise 5.0.0 bundle in > order to get the org.osgi.service.jdbc package. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2810) Add feature installation date
[ 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.1) 3.0.2 > Add feature installation date > - > > 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.2 > > > 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.2#6252)
[jira] [Updated] (KARAF-2809) Add an option to uninstall transitive features
[ https://issues.apache.org/jira/browse/KARAF-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2809: Fix Version/s: (was: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > Add an option to uninstall transitive features > -- > > Key: KARAF-2809 > URL: https://issues.apache.org/jira/browse/KARAF-2809 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > > Using feature:uninstall uninstalls only the provided features: the transitive > features are not uninstall. > If it makes sense in most of the case, it would be great to provide an option > to uninstall transitive features (for instance, using EnumSet). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2755) Encrypt password mechanism pollutes the group
[
https://issues.apache.org/jira/browse/KARAF-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2755:
Fix Version/s: (was: 3.0.1)
3.0.2
4.0.0
> Encrypt password mechanism pollutes the group
> -
>
> Key: KARAF-2755
> URL: https://issues.apache.org/jira/browse/KARAF-2755
> Project: Karaf
> Issue Type: Bug
> Components: karaf-security
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 2.4.0, 4.0.0, 3.0.2
>
>
> By enabling the encryption (in etc/org.apache.karaf.jaas.cfg), Karaf ignores
> if we talk about users or groups, and so encrypts the groups, resulting to
> something like this in etc/users.properties:
> {code}
> karaf = {CRYPT}e7ebf747769e8522b52d1bf47f718788{CRYPT},_g_:admingroup
> _g_\:admingroup =
> {CRYPT}db0f6f37ebeb6ea09489124345af2a45{CRYPT},admin,manager,viewer
> {code}
> The encryption service should check if the considered line is an user or a
> group, and just crypts the user passwords.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (KARAF-2869) Upgrade to Pax CDI 0.7.0
[ https://issues.apache.org/jira/browse/KARAF-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-2869. - Resolution: Duplicate > Upgrade to Pax CDI 0.7.0 > > > Key: KARAF-2869 > URL: https://issues.apache.org/jira/browse/KARAF-2869 > Project: Karaf > Issue Type: Dependency upgrade > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.1, 4.0.0, 2.3.5 > > > I fixed some issues in Pax CDI, especially in the Karaf feature (about scr > version range, etc). > I will release Pax CDI 0.7.0 soon. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2786) Warn user about security issue with default key and document how to change it
[ https://issues.apache.org/jira/browse/KARAF-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2786: Fix Version/s: (was: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > Warn user about security issue with default key and document how to change it > - > > Key: KARAF-2786 > URL: https://issues.apache.org/jira/browse/KARAF-2786 > Project: Karaf > Issue Type: Bug > Components: karaf-documentation, karaf-security >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > > Default Karaf distribution provides a self signed key used by the SSHd server. > We should warn the users that the default distribution is potentially > "vulnerable" and document how to use keytool, etc to change the key. > In addition of the etc/keys.properties, we should document the > etc/users.properties to change property and add a note about encryption. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2787) Add a way to specify the client key
[ https://issues.apache.org/jira/browse/KARAF-2787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2787: Fix Version/s: (was: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > Add a way to specify the client key > --- > > Key: KARAF-2787 > URL: https://issues.apache.org/jira/browse/KARAF-2787 > Project: Karaf > Issue Type: Bug > Components: karaf-core, karaf-security >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > > Right now, the key is embedded in the client jar. It's not possible to > override the key and the client falls back to user/password instead of key > agent. > It would be great to be able to provide an overrided key in the client. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2803) Set org.apache.aries.blueprint.preemptiveShutdown to false by default
[ https://issues.apache.org/jira/browse/KARAF-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2803: Fix Version/s: (was: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > Set org.apache.aries.blueprint.preemptiveShutdown to false by default > - > > Key: KARAF-2803 > URL: https://issues.apache.org/jira/browse/KARAF-2803 > Project: Karaf > Issue Type: Improvement > Components: karaf-core >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > > In order to shutdown blueprint containers in a more "logic" order, the > org.apache.aries.blueprint.preemptiveShutdown attribute (in > etc/config.properties) should be set to false by default. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Work started] (KARAF-2807) Unable to have multiple subshells in one bundle
[
https://issues.apache.org/jira/browse/KARAF-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on KARAF-2807 started by Jean-Baptiste Onofré.
> Unable to have multiple subshells in one bundle
> ---
>
> Key: KARAF-2807
> URL: https://issues.apache.org/jira/browse/KARAF-2807
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
>Affects Versions: 3.0.0
> Environment: JDK7, Aries Blueprint, karaf shell schema v1.1.0
>Reporter: Rebecca Chan
>Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.1, 4.0.0
>
> Attachments: fixSubshell.patch
>
>
> *PROBLEM:*
> According to Karaf 3.0.0 release note, Karaf "groups" the commands by scope.
> Each scope form a subshell. Users should be able to enter subshell directly
> by typing the subshell name.
> However, if commands with different scopes are packaged in one OSGI bundle,
> only the scope of the first command in the blueprint xml file will be
> registered as subshell.
> For example, I have the following three commands in a OSGI bundle
> {quote}
> @Command(scope = "children", name = "boy", description = "boy's command")
> public class BoyCommand extends OsgiCommandSupport {
> }
> @Command(scope = "children", name = "girl", description = "girl's command")
> public class GirlCommand extends OsgiCommandSupport {
> }
> @Command(scope = "pet", name = "dog", description = "dog's command")
> public class DogCommand extends OsgiCommandSupport {
> }
> {quote}
> And they are in blueprint xml file.
> {quote}
> http://www.osgi.org/xmlns/blueprint/v1.0.0";
> default-activation="lazy">
> http://karaf.apache.org/xmlns/shell/v1.1.0";>
>
>
>
>
>
>
>
>
>
>
>
> {quote}
> I can access children subshell directly by type "children" but I cannot acess
> pet subshell by typing "pet"
> *SUGGESTION:*
> After looking into the source code of karaf 3.0.0, there is a bug around line
> 188 in org.apache.karaf.shell.console.commands.NamespaceHandler. If the
> schema is not SHELL_NAMESPACE_1_0_0 or the action name does not contain the
> scope name, the variable "scope" will be null and the subShellName will
> always be ".subshell.null". Therefore, if schema is not 1.0.0, only the
> scope of the first defined command in the OSGI bundle will be registered as
> subshell in the if statement.
> A patch is attached. Please review if it is a proper fix to the bug
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (KARAF-2830) Karaf scripts java version check should be more "flexible"
[
https://issues.apache.org/jira/browse/KARAF-2830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated KARAF-2830:
Fix Version/s: (was: 3.0.1)
3.0.2
> Karaf scripts java version check should be more "flexible"
> --
>
> Key: KARAF-2830
> URL: https://issues.apache.org/jira/browse/KARAF-2830
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Environment: Java8
>Reporter: Jean-Baptiste Onofré
>Assignee: Jean-Baptiste Onofré
> Fix For: 2.4.0, 4.0.0, 3.0.2
>
>
> If the java -version output returns something different from x.x.x (like
> 1.7.0, which is the case with Java8), the Karaf script fails with:
> {code}
> ./karaf: line 242: [: : integer expression expected
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[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: 2.3.5) (was: 3.0.1) 2.3.6 3.0.2 > 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: 2.4.0, 4.0.0, 3.0.2, 2.3.6 > > > 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.2#6252)
[jira] [Updated] (KARAF-2815) Better management of RMI/JMX ports for pax-exam integration tests
[ https://issues.apache.org/jira/browse/KARAF-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2815: Fix Version/s: 2.3.5 > Better management of RMI/JMX ports for pax-exam integration tests > - > > Key: KARAF-2815 > URL: https://issues.apache.org/jira/browse/KARAF-2815 > Project: Karaf > Issue Type: Bug > Components: karaf-exam >Affects Versions: 2.3.4 >Reporter: Grzegorz Grzybek >Assignee: Jean-Baptiste Onofré > Fix For: 2.3.5 > > > Integration tests of Karaf alway use default (hardcoded) ports for RMI > Registry and JMX Server Connector (1099 and 4 respectively). > The ports should be generated before tests. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Work started] (KARAF-2815) Better management of RMI/JMX ports for pax-exam integration tests
[ https://issues.apache.org/jira/browse/KARAF-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KARAF-2815 started by Jean-Baptiste Onofré. > Better management of RMI/JMX ports for pax-exam integration tests > - > > Key: KARAF-2815 > URL: https://issues.apache.org/jira/browse/KARAF-2815 > Project: Karaf > Issue Type: Bug > Components: karaf-exam >Affects Versions: 2.3.4 >Reporter: Grzegorz Grzybek >Assignee: Jean-Baptiste Onofré > Fix For: 2.3.5 > > > Integration tests of Karaf alway use default (hardcoded) ports for RMI > Registry and JMX Server Connector (1099 and 4 respectively). > The ports should be generated before tests. -- This message was sent by Atlassian JIRA (v6.2#6252)
[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.1) 3.0.2 > 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: 2.4.0, 4.0.0, 3.0.2 > > > 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.2#6252)
[jira] [Resolved] (KARAF-2842) Add an option to feature:install to install the bundles without starting it
[ https://issues.apache.org/jira/browse/KARAF-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré resolved KARAF-2842. - Resolution: Fixed > Add an option to feature:install to install the bundles without starting it > --- > > Key: KARAF-2842 > URL: https://issues.apache.org/jira/browse/KARAF-2842 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.1, 4.0.0, 2.3.5 > > > In order to let the users prepare an installation without starting the > process, it would be interesting to add an option to feature:install (like > -s) to install the bundles in the feature without starting them. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KARAF-2842) Add an option to feature:install to install the bundles without starting it
[ https://issues.apache.org/jira/browse/KARAF-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962986#comment-13962986 ] Jean-Baptiste Onofré commented on KARAF-2842: - Fixed on karaf-2.3.x: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=45e7f3cee3d5ae99d002c2b441baeecc7d95293a > Add an option to feature:install to install the bundles without starting it > --- > > Key: KARAF-2842 > URL: https://issues.apache.org/jira/browse/KARAF-2842 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.1, 4.0.0, 2.3.5 > > > In order to let the users prepare an installation without starting the > process, it would be interesting to add an option to feature:install (like > -s) to install the bundles in the feature without starting them. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KARAF-2842) Add an option to feature:install to install the bundles without starting it
[ https://issues.apache.org/jira/browse/KARAF-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962956#comment-13962956 ] Jean-Baptiste Onofré commented on KARAF-2842: - Fixed on karaf-2.x: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=22cb49b9eb8db35915d4ad5156865a1ebdaca27d > Add an option to feature:install to install the bundles without starting it > --- > > Key: KARAF-2842 > URL: https://issues.apache.org/jira/browse/KARAF-2842 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.1, 4.0.0, 2.3.5 > > > In order to let the users prepare an installation without starting the > process, it would be interesting to add an option to feature:install (like > -s) to install the bundles in the feature without starting them. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KARAF-2842) Add an option to feature:install to install the bundles without starting it
[ https://issues.apache.org/jira/browse/KARAF-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962928#comment-13962928 ] Jean-Baptiste Onofré commented on KARAF-2842: - Fixed on karaf-3.0.x: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=059c755ac328672ceaaefd2c7b996c1e3cbf962d > Add an option to feature:install to install the bundles without starting it > --- > > Key: KARAF-2842 > URL: https://issues.apache.org/jira/browse/KARAF-2842 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.1, 4.0.0, 2.3.5 > > > In order to let the users prepare an installation without starting the > process, it would be interesting to add an option to feature:install (like > -s) to install the bundles in the feature without starting them. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (KARAF-2842) Add an option to feature:install to install the bundles without starting it
[ https://issues.apache.org/jira/browse/KARAF-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962806#comment-13962806 ] Jean-Baptiste Onofré commented on KARAF-2842: - Fixed on master: https://git-wip-us.apache.org/repos/asf?p=karaf.git;a=commitdiff;h=18c31df228c542c42079bb71e84b2e35220e5791 > Add an option to feature:install to install the bundles without starting it > --- > > Key: KARAF-2842 > URL: https://issues.apache.org/jira/browse/KARAF-2842 > Project: Karaf > Issue Type: Improvement > Components: karaf-feature >Reporter: Jean-Baptiste Onofré >Assignee: Jean-Baptiste Onofré > Fix For: 2.4.0, 3.0.1, 4.0.0, 2.3.5 > > > In order to let the users prepare an installation without starting the > process, it would be interesting to add an option to feature:install (like > -s) to install the bundles in the feature without starting them. -- This message was sent by Atlassian JIRA (v6.2#6252)
[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: Summary: Add Spring Security 3.2.3.RELEASE, Spring LDAP, and Spring Batch features (was: Add Spring Security 3.2.3.RELEASE feature) > 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: 2.4.0, 4.0.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2843) Add Spring Security 3.2.3.RELEASE feature
[ 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: 2.3.5) (was: 3.0.1) > Add Spring Security 3.2.3.RELEASE feature > - > > 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: 2.4.0, 4.0.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (KARAF-2843) Add Spring Security 3.2.3.RELEASE feature
[ https://issues.apache.org/jira/browse/KARAF-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated KARAF-2843: Summary: Add Spring Security 3.2.3.RELEASE feature (was: Add Spring Security 4.x features) > Add Spring Security 3.2.3.RELEASE feature > - > > 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: 2.4.0, 3.0.1, 4.0.0, 2.3.5 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
