[
https://issues.jboss.org/browse/AS7-5925?page=com.atlassian.jira.plugin.s...
]
Guillaume Nodet commented on AS7-5925:
--------------------------------------
The {{karaf.startRemoveShell}} and {{karaf.startLocalConsole}} already have default values
of {{true}}. I think it would make sense to change the {{startLocalConsole}} default
value to false to ease embedding Karaf console.
For {{karaf.home}} and {{karaf.base}}, we can't really use Config Admin for that as
it's really not supposed to be changed at any time. Those two properties are used
throughout Karaf code base when there is a need to access the file system for
configuration files which are not manageable through ConfigAdmin.
In the SSH console, those are used as default values for the location of the ssh server
hostKey and for authorizedKeys, but those properties are configurable through ConfigAdmin,
the system properties are only used as default values. The CA configuration also contains
additional properties such as the port, host, etc...
Karaf configuration through ConfigAdmin
---------------------------------------
Key: AS7-5925
URL:
https://issues.jboss.org/browse/AS7-5925
Project: Application Server 7
Issue Type: Feature Request
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.CR1
Currently we add these props to standalone.conf
{code}
-Dkaraf.home=.../jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT/standalone/data/karaf
-Dkaraf.base=.../jboss-as-karaf-7.2.0.Alpha1-SNAPSHOT/standalone/data/karaf
-Dkaraf.startRemoteShell=true -Dkaraf.startLocalConsole=false
{code}
For this we should have sensible defaults as well as make the SSH port (and possibly
other options) configurable through ConfigAdmin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira