[jira] [Updated] (KARAF-2466) make it easy to access environment variables inside karaf configuration properties files

[ https://issues.apache.org/jira/browse/KARAF-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated KARAF-2466: -- Description: when using karaf in clouds & PaaS infrastructures like OpenShift, Docker, OpenSta

[jira] [Updated] (KARAF-2466) make it easy to access environment variables inside karaf configuration properties files - via ${ENV.foo}?

[ https://issues.apache.org/jira/browse/KARAF-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated KARAF-2466: -- Summary: make it easy to access environment variables inside karaf configuration properties fil

[jira] [Created] (KARAF-2466) make it easy to access environment variables inside karaf configuration properties files

james strachan created KARAF-2466: - Summary: make it easy to access environment variables inside karaf configuration properties files Key: KARAF-2466 URL: https://issues.apache.org/jira/browse/KARAF-2466

[jira] [Created] (KARAF-1501) provide MBean access to the spring, blueprint (& one day CDI) status of bundles

james strachan created KARAF-1501: - Summary: provide MBean access to the spring, blueprint (& one day CDI) status of bundles Key: KARAF-1501 URL: https://issues.apache.org/jira/browse/KARAF-1501 Proje

[jira] [Created] (KARAF-736) parse a "~/.karafrc" type file on startup of the shell so users can define aliases in one place which work with any karaf installation

parse a "~/.karafrc" type file on startup of the shell so users can define aliases in one place which work with any karaf installation -- Key: KARAF

[jira] [Created] (KARAF-636) admin:destroy to take wildcards

admin:destroy to take wildcards --- Key: KARAF-636 URL: https://issues.apache.org/jira/browse/KARAF-636 Project: Karaf Issue Type: Improvement Reporter: james strachan When testing its handy to start

[jira] [Commented] (KARAF-222) mvn karaf:run plugin, like jetty:run

[ https://issues.apache.org/jira/browse/KARAF-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011407#comment-13011407 ] james strachan commented on KARAF-222: -- Hey David, long time no speak! :) Sounds lik

[jira] [Commented] (KARAF-222) mvn karaf:run plugin, like jetty:run

[ https://issues.apache.org/jira/browse/KARAF-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13011190#comment-13011190 ] james strachan commented on KARAF-222: -- I still love the idea of the 'mvn karaf:run' g

[jira] Commented: (KARAF-223) Support Pomegranate web apps?

[ https://issues.apache.org/jira/browse/KARAF-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918855#action_12918855 ] james strachan commented on KARAF-223: -- here's another link to Pomegranate http://www

[jira] Created: (KARAF-223) Support Pomegranate web apps?

Support Pomegranate web apps? - Key: KARAF-223 URL: https://issues.apache.org/jira/browse/KARAF-223 Project: Karaf Issue Type: New Feature Reporter: james strachan Priority: Trivial This

[jira] Created: (KARAF-222) mvn karaf:run plugin, like jetty:run

mvn karaf:run plugin, like jetty:run Key: KARAF-222 URL: https://issues.apache.org/jira/browse/KARAF-222 Project: Karaf Issue Type: New Feature Reporter: james strachan Did a quick google &

[jira] Created: (KARAF-220) provide a text entry option with remembered default values for 'wizard' like commands

provide a text entry option with remembered default values for 'wizard' like commands - Key: KARAF-220 URL: https://issues.apache.org/jira/browse/KARAF-220 Project: K

[jira] Commented: (KARAF-214) Print a nice error when a command is not found

[ https://issues.apache.org/jira/browse/KARAF-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913460#action_12913460 ] james strachan commented on KARAF-214: -- Great stuff, thanks! > Print a nice error when

[jira] Resolved: (KARAF-213) create an automatic completer if an @Argument is a File by using the current working directory and completing on files. I wonder if we could provide an optional filter met

[ https://issues.apache.org/jira/browse/KARAF-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan resolved KARAF-213. -- Fix Version/s: 2.2.0 Resolution: Fixed > create an automatic completer if an @Argument is

[jira] Commented: (KARAF-154) allow @Command objects to implement Runnable - or have a @Run annotation on the method so that they don't have to extend Action to avoid runtime Karaf dependency

[ https://issues.apache.org/jira/browse/KARAF-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910511#action_12910511 ] james strachan commented on KARAF-154: -- turns out this is a fairly big refactor with no

[jira] Updated: (KARAF-154) allow @Command objects to implement Runnable - or have a @Run annotation on the method so that they don't have to extend Action to avoid runtime Karaf dependency

[ https://issues.apache.org/jira/browse/KARAF-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated KARAF-154: - Fix Version/s: (was: 2.2.0) Priority: Trivial (was: Minor) > allow @Command objects

[jira] Created: (KARAF-214) felix.gogo should throw a CommandNotFoundException for easier reporting outside of OSGi; and allow "*.:" prefix in errors to be configurable to support single-scope stand a

felix.gogo should throw a CommandNotFoundException for easier reporting outside of OSGi; and allow "*.:" prefix in errors to be configurable to support single-scope stand alone shells better --

[jira] Resolved: (KARAF-208) when reusing the karaf shell outside of OSGi where there's only one shell scope, it would be nice to avoid prefixing the command names with the scope or with "*:" which is

[ https://issues.apache.org/jira/browse/KARAF-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan resolved KARAF-208. -- Resolution: Fixed I'm going to mark this one as fixed as pretty much all the issues are resolved

[jira] Resolved: (KARAF-212) provide a simple annotation, say,@CompleterValues which can be used on methods on an action to provide a list of available values for an argument for tab completion

[ https://issues.apache.org/jira/browse/KARAF-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan resolved KARAF-212. -- Resolution: Fixed see CompleterValuesTest for test case showing it in action > provide a simple

[jira] Created: (KARAF-213) create an automatic completer if an @Argument is a File by using the current working directory and completing on files. I wonder if we could provide an optional filter meth

create an automatic completer if an @Argument is a File by using the current working directory and completing on files. I wonder if we could provide an optional filter method maybe to restrict available files? ---

[jira] Created: (KARAF-212) provide a simple annotation, say,@CompleterValues which can be used on methods on an action to provide a list of available values for an argument for tab completion

provide a simple annotation, say,@CompleterValues which can be used on methods on an action to provide a list of available values for an argument for tab completion

[jira] Commented: (KARAF-208) when reusing the karaf shell outside of OSGi where there's only one shell scope, it would be nice to avoid prefixing the command names with the scope or with "*:" which i

[ https://issues.apache.org/jira/browse/KARAF-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910073#action_12910073 ] james strachan commented on KARAF-208: -- Just committed another fix which fixes tab comp

[jira] Commented: (KARAF-208) when reusing the karaf shell outside of OSGi where there's only one shell scope, it would be nice to avoid prefixing the command names with the scope or with "*:" which i

[ https://issues.apache.org/jira/browse/KARAF-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909786#action_12909786 ] james strachan commented on KARAF-208: -- just committed a partial fix for the help comma

[jira] Created: (KARAF-208) when reusing the karaf shell outside of OSGi where there's only one shell scope, it would be nice to avoid prefixing the command names with the scope or with "*:" which is

when reusing the karaf shell outside of OSGi where there's only one shell scope, it would be nice to avoid prefixing the command names with the scope or with "*:" which is confusing ---

[jira] Updated: (KARAF-153) support injection of other kinds of collections for arguments / options

[ https://issues.apache.org/jira/browse/KARAF-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated KARAF-153: - Fix Version/s: 2.2.0 (was: 2.1.0) its a nice to have - lets defer > suppor

[jira] Resolved: (KARAF-161) provide an easy implementation of "public static void main(String[] args)" for a single command (i.e. for non-shells)

[ https://issues.apache.org/jira/browse/KARAF-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan resolved KARAF-161. -- Resolution: Fixed its now pretty straightforward for folks to derive from org.apache.karaf.shel

[jira] Updated: (KARAF-160) document how users should write commands with the OSGI or META-INF/services way to discover them

[ https://issues.apache.org/jira/browse/KARAF-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated KARAF-160: - Fix Version/s: 2.2.0 (was: 2.1.0) lets defer to get 2.1.0 out > document h

[jira] Updated: (KARAF-154) allow @Command objects to implement Runnable - or have a @Run annotation on the method so that they don't have to extend Action to avoid runtime Karaf dependency

[ https://issues.apache.org/jira/browse/KARAF-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated KARAF-154: - Fix Version/s: 2.2.0 (was: 2.1.0) Priority: Minor (was: Major) mo

[jira] Resolved: (KARAF-170) Main --help should behave like Main someCommand --help and list all the possible sub commands when outside of OSGi

[ https://issues.apache.org/jira/browse/KARAF-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan resolved KARAF-170. -- Resolution: Won't Fix not required now KARAF-171 has a patch for it > Main --help should behave

[jira] Commented: (KARAF-170) Main --help should behave like Main someCommand --help and list all the possible sub commands when outside of OSGi

[ https://issues.apache.org/jira/browse/KARAF-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903013#action_12903013 ] james strachan commented on KARAF-170: -- I guess this isn't such a big deal - now we've

[jira] Commented: (KARAF-171) provide a default "help" sub command in shells used outside of OSGi

[ https://issues.apache.org/jira/browse/KARAF-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903012#action_12903012 ] james strachan commented on KARAF-171: -- for simplicity I added a new "help" command by

[jira] Commented: (KARAF-174) tab completion of sub commands not working in the non-osgi shell

[ https://issues.apache.org/jira/browse/KARAF-174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902900#action_12902900 ] james strachan commented on KARAF-174: -- Here's the patch http://github.com/jstrachan/ka

[jira] Created: (KARAF-174) tab completion of sub commands not working in the non-osgi shell

tab completion of sub commands not working in the non-osgi shell Key: KARAF-174 URL: https://issues.apache.org/jira/browse/KARAF-174 Project: Karaf Issue Type: Improvement

[jira] Created: (KARAF-171) provide a default "help" sub command in shells used outside of OSGi

provide a default "help" sub command in shells used outside of OSGi --- Key: KARAF-171 URL: https://issues.apache.org/jira/browse/KARAF-171 Project: Karaf Issue Type: Improvemen

[jira] Created: (KARAF-170) Main --help should behave like Main someCommand --help and list all the possible sub commands when outside of OSGi

Main --help should behave like Main someCommand --help and list all the possible sub commands when outside of OSGi -- Key: KARAF-170 URL: https://issue

[jira] Created: (KARAF-161) provide an easy implementation of "public static void main(String[] args)" for a single command (i.e. for non-shells)

provide an easy implementation of "public static void main(String[] args)" for a single command (i.e. for non-shells) - Key: KARAF-161 URL: https:/

[jira] Created: (KARAF-160) document how users should write commands with the OSGI or META-INF/services way to discover them

document how users should write commands with the OSGI or META-INF/services way to discover them Key: KARAF-160 URL: https://issues.apache.org/jira/browse/KARAF-160

[jira] Created: (KARAF-159) when a bad command is typed (e.g. invalid command, argument, option) we should use some kind of syntax highlighting for the name of the command/argument/option in the error

when a bad command is typed (e.g. invalid command, argument, option) we should use some kind of syntax highlighting for the name of the command/argument/option in the error message

[jira] Created: (KARAF-158) better display of errors when running a non-osgi command line outside of the shell

better display of errors when running a non-osgi command line outside of the shell -- Key: KARAF-158 URL: https://issues.apache.org/jira/browse/KARAF-158 Project: Karaf

[jira] Updated: (KARAF-157) [PATH] minor patch to make it easier to reuse the Karaf command line console from outside Karaf specialising the user and application

[ https://issues.apache.org/jira/browse/KARAF-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated KARAF-157: - Attachment: minor-refactor.patch > [PATH] minor patch to make it easier to reuse the Karaf command

[jira] Created: (KARAF-157) [PATH] minor patch to make it easier to reuse the Karaf command line console from outside Karaf specialising the user and application

[PATH] minor patch to make it easier to reuse the Karaf command line console from outside Karaf specialising the user and application - Key: KARAF-1

[jira] Created: (KARAF-155) optional @Argument values (and I guess @Option values) can have default values which could be displayed in the help screen by reflecting into the value and finding non-zero

optional @Argument values (and I guess @Option values) can have default values which could be displayed in the help screen by reflecting into the value and finding non-zero/null values

[jira] Updated: (KARAF-155) optional @Argument values (and I guess @Option values) can have default values which could be displayed in the help screen by reflecting into the value and finding non-zero

[ https://issues.apache.org/jira/browse/KARAF-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james strachan updated KARAF-155: - Priority: Trivial (was: Major) > optional @Argument values (and I guess @Option values) can have

[jira] Created: (KARAF-154) allow @Command objects to implement Runnable - or have a @Run annotation on the method so that they don't have to extend Action to avoid runtime Karaf dependency

allow @Command objects to implement Runnable - or have a @Run annotation on the method so that they don't have to extend Action to avoid runtime Karaf dependency ---

[jira] Created: (KARAF-153) support injection of other kinds of collections for arguments / options

support injection of other kinds of collections for arguments / options --- Key: KARAF-153 URL: https://issues.apache.org/jira/browse/KARAF-153 Project: Karaf Issue Type: Im

[jira] Created: (KARAF-152) when using the @Argument annotation, if there is no name specified it would be nice to reuse the name of the field, rather than use VAL

when using the @Argument annotation, if there is no name specified it would be nice to reuse the name of the field, rather than use VAL --- Key: KAR