karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Pieber (JIRA)" <j...@apache.org>
Subject [jira] Work started: (KARAF-350) Add KARAF_OPTS param to startup scripts
Date Fri, 31 Dec 2010 19:04:45 GMT

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

Work on KARAF-350 started by Andreas Pieber.

> Add KARAF_OPTS param to startup scripts
> ---------------------------------------
>
>                 Key: KARAF-350
>                 URL: https://issues.apache.org/jira/browse/KARAF-350
>             Project: Karaf
>          Issue Type: New Feature
>            Reporter: Andreas Pieber
>            Assignee: Andreas Pieber
>             Fix For: 2.2.0
>
>
> There are use cases where the static configuration of system properties via e.g. the
etc/system.properties file is not enough. Examples are additional debug-options, flags in
your bundles you use to add/test additional functionality, ...
> This could (and should be done; as discussed on the mailinglist) by adding a KARAF_OPTS
param to the startup scripts. This will not change the behavior in current karaf usage, but
allows to do something like
> export KARAF_OPTS=-Dwicket.configuration=development
> ./karaf

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message