You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Andreas Pieber (JIRA)" <ji...@apache.org> on 2010/12/31 20:02:46 UTC
[jira] Created: (KARAF-350) Add KARAF_OPTS param to startup scripts
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.
[jira] Resolved: (KARAF-350) Add KARAF_OPTS param to startup
scripts
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Pieber resolved KARAF-350.
----------------------------------
Resolution: Fixed
Committed r1054162
> 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.
[jira] Work started: (KARAF-350) Add KARAF_OPTS param to startup
scripts
Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
[ 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.
[jira] [Closed] (KARAF-350) Add KARAF_OPTS param to startup scripts
Posted by "Jamie goodyear (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear closed KARAF-350.
--------------------------------
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira