You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Rob Walker (JIRA)" <ji...@apache.org> on 2008/10/21 11:11:44 UTC
[jira] Created: (FELIX-784) Create "felix" property name as
alternatives to old style Oscar property names
Create "felix" property name as alternatives to old style Oscar property names
------------------------------------------------------------------------------
Key: FELIX-784
URL: https://issues.apache.org/jira/browse/FELIX-784
Project: Felix
Issue Type: Improvement
Components: HTTP Service
Reporter: Rob Walker
Priority: Trivial
Some of the Http properties still use the old Oscar prefix.
The following set is proposed for the old and new equivalent names:
Current New
======= ===
org.ungoverned.osgi.bundle.https.enable org.apache.felix.https.enable
org.ungoverned.osgi.bundle.https.provider org.apache.felix.https.provider
org.ungoverned.osgi.bundle.https.keystore org.apache.felix.https.keystore
org.ungoverned.osgi.bundle.https.password org.apache.felix.https.password
org.ungoverned.osgi.bundle.https.key.password org.apache.felix.https.key.password
org.apache.felix.http.jetty.debug org.apache.felix.http.debug
Whilst the latter already has a "felix" name, if Felix adds a later lightweight/non-jetty it will make for simpler migration to have a non-jetty specific property name
For backwards compatibility it is probably best to create newer "felix" alternatives in parallel to the older style name, so either name may be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-784) Create "felix" property name as
alternatives to old style Oscar property names
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans resolved FELIX-784.
------------------------------------
Resolution: Fixed
Implemented as documented in the svn commit. New properties take precedence over old ones if both are specified.
> Create "felix" property name as alternatives to old style Oscar property names
> ------------------------------------------------------------------------------
>
> Key: FELIX-784
> URL: https://issues.apache.org/jira/browse/FELIX-784
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Reporter: Rob Walker
> Assignee: Marcel Offermans
> Priority: Trivial
>
> Some of the Http properties still use the old Oscar prefix.
> The following set is proposed for the old and new equivalent names:
> org.ungoverned.osgi.bundle.https.enable -----> org.apache.felix.https.enable
> org.ungoverned.osgi.bundle.https.provider -----> org.apache.felix.https.provider
> org.ungoverned.osgi.bundle.https.keystore -----> org.apache.felix.https.keystore
> org.ungoverned.osgi.bundle.https.password -----> org.apache.felix.https.password
> org.ungoverned.osgi.bundle.https.key.password -----> org.apache.felix.https.key.password
> org.apache.felix.http.jetty.debug -----> org.apache.felix.http.debug
> Whilst the latter already has a "felix" name, if Felix adds a later lightweight/non-jetty it will make for simpler migration to have a non-jetty specific property name
> For backwards compatibility it is probably best to create newer "felix" alternatives in parallel to the older style name, so either name may be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-784) Create "felix" property name as
alternatives to old style Oscar property names
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641411#action_12641411 ]
Richard S. Hall commented on FELIX-784:
---------------------------------------
Your call, but it was obviously an oversight when moving the code to Apache.
> Create "felix" property name as alternatives to old style Oscar property names
> ------------------------------------------------------------------------------
>
> Key: FELIX-784
> URL: https://issues.apache.org/jira/browse/FELIX-784
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Reporter: Rob Walker
> Priority: Trivial
>
> Some of the Http properties still use the old Oscar prefix.
> The following set is proposed for the old and new equivalent names:
> org.ungoverned.osgi.bundle.https.enable -----> org.apache.felix.https.enable
> org.ungoverned.osgi.bundle.https.provider -----> org.apache.felix.https.provider
> org.ungoverned.osgi.bundle.https.keystore -----> org.apache.felix.https.keystore
> org.ungoverned.osgi.bundle.https.password -----> org.apache.felix.https.password
> org.ungoverned.osgi.bundle.https.key.password -----> org.apache.felix.https.key.password
> org.apache.felix.http.jetty.debug -----> org.apache.felix.http.debug
> Whilst the latter already has a "felix" name, if Felix adds a later lightweight/non-jetty it will make for simpler migration to have a non-jetty specific property name
> For backwards compatibility it is probably best to create newer "felix" alternatives in parallel to the older style name, so either name may be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-784) Create "felix" property name as
alternatives to old style Oscar property names
Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Offermans reassigned FELIX-784:
--------------------------------------
Assignee: Marcel Offermans
> Create "felix" property name as alternatives to old style Oscar property names
> ------------------------------------------------------------------------------
>
> Key: FELIX-784
> URL: https://issues.apache.org/jira/browse/FELIX-784
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Reporter: Rob Walker
> Assignee: Marcel Offermans
> Priority: Trivial
>
> Some of the Http properties still use the old Oscar prefix.
> The following set is proposed for the old and new equivalent names:
> org.ungoverned.osgi.bundle.https.enable -----> org.apache.felix.https.enable
> org.ungoverned.osgi.bundle.https.provider -----> org.apache.felix.https.provider
> org.ungoverned.osgi.bundle.https.keystore -----> org.apache.felix.https.keystore
> org.ungoverned.osgi.bundle.https.password -----> org.apache.felix.https.password
> org.ungoverned.osgi.bundle.https.key.password -----> org.apache.felix.https.key.password
> org.apache.felix.http.jetty.debug -----> org.apache.felix.http.debug
> Whilst the latter already has a "felix" name, if Felix adds a later lightweight/non-jetty it will make for simpler migration to have a non-jetty specific property name
> For backwards compatibility it is probably best to create newer "felix" alternatives in parallel to the older style name, so either name may be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-784) Create "felix" property name as
alternatives to old style Oscar property names
Posted by "Rob Walker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Walker updated FELIX-784:
-----------------------------
Description:
Some of the Http properties still use the old Oscar prefix.
The following set is proposed for the old and new equivalent names:
org.ungoverned.osgi.bundle.https.enable -----> org.apache.felix.https.enable
org.ungoverned.osgi.bundle.https.provider -----> org.apache.felix.https.provider
org.ungoverned.osgi.bundle.https.keystore -----> org.apache.felix.https.keystore
org.ungoverned.osgi.bundle.https.password -----> org.apache.felix.https.password
org.ungoverned.osgi.bundle.https.key.password -----> org.apache.felix.https.key.password
org.apache.felix.http.jetty.debug -----> org.apache.felix.http.debug
Whilst the latter already has a "felix" name, if Felix adds a later lightweight/non-jetty it will make for simpler migration to have a non-jetty specific property name
For backwards compatibility it is probably best to create newer "felix" alternatives in parallel to the older style name, so either name may be used.
was:
Some of the Http properties still use the old Oscar prefix.
The following set is proposed for the old and new equivalent names:
Current New
======= ===
org.ungoverned.osgi.bundle.https.enable org.apache.felix.https.enable
org.ungoverned.osgi.bundle.https.provider org.apache.felix.https.provider
org.ungoverned.osgi.bundle.https.keystore org.apache.felix.https.keystore
org.ungoverned.osgi.bundle.https.password org.apache.felix.https.password
org.ungoverned.osgi.bundle.https.key.password org.apache.felix.https.key.password
org.apache.felix.http.jetty.debug org.apache.felix.http.debug
Whilst the latter already has a "felix" name, if Felix adds a later lightweight/non-jetty it will make for simpler migration to have a non-jetty specific property name
For backwards compatibility it is probably best to create newer "felix" alternatives in parallel to the older style name, so either name may be used.
> Create "felix" property name as alternatives to old style Oscar property names
> ------------------------------------------------------------------------------
>
> Key: FELIX-784
> URL: https://issues.apache.org/jira/browse/FELIX-784
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Reporter: Rob Walker
> Priority: Trivial
>
> Some of the Http properties still use the old Oscar prefix.
> The following set is proposed for the old and new equivalent names:
> org.ungoverned.osgi.bundle.https.enable -----> org.apache.felix.https.enable
> org.ungoverned.osgi.bundle.https.provider -----> org.apache.felix.https.provider
> org.ungoverned.osgi.bundle.https.keystore -----> org.apache.felix.https.keystore
> org.ungoverned.osgi.bundle.https.password -----> org.apache.felix.https.password
> org.ungoverned.osgi.bundle.https.key.password -----> org.apache.felix.https.key.password
> org.apache.felix.http.jetty.debug -----> org.apache.felix.http.debug
> Whilst the latter already has a "felix" name, if Felix adds a later lightweight/non-jetty it will make for simpler migration to have a non-jetty specific property name
> For backwards compatibility it is probably best to create newer "felix" alternatives in parallel to the older style name, so either name may be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-784) Create "felix" property name as
alternatives to old style Oscar property names
Posted by "Rob Walker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641413#action_12641413 ]
Rob Walker commented on FELIX-784:
----------------------------------
That's definitely true - I had a bit of a "duh" moment when I noticed them today.
> Create "felix" property name as alternatives to old style Oscar property names
> ------------------------------------------------------------------------------
>
> Key: FELIX-784
> URL: https://issues.apache.org/jira/browse/FELIX-784
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Reporter: Rob Walker
> Priority: Trivial
>
> Some of the Http properties still use the old Oscar prefix.
> The following set is proposed for the old and new equivalent names:
> org.ungoverned.osgi.bundle.https.enable -----> org.apache.felix.https.enable
> org.ungoverned.osgi.bundle.https.provider -----> org.apache.felix.https.provider
> org.ungoverned.osgi.bundle.https.keystore -----> org.apache.felix.https.keystore
> org.ungoverned.osgi.bundle.https.password -----> org.apache.felix.https.password
> org.ungoverned.osgi.bundle.https.key.password -----> org.apache.felix.https.key.password
> org.apache.felix.http.jetty.debug -----> org.apache.felix.http.debug
> Whilst the latter already has a "felix" name, if Felix adds a later lightweight/non-jetty it will make for simpler migration to have a non-jetty specific property name
> For backwards compatibility it is probably best to create newer "felix" alternatives in parallel to the older style name, so either name may be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-784) Create "felix" property name as
alternatives to old style Oscar property names
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641395#action_12641395 ]
Richard S. Hall commented on FELIX-784:
---------------------------------------
Sounds reasonable to me. I would just get rid of the old names, no reason to keep them around.
> Create "felix" property name as alternatives to old style Oscar property names
> ------------------------------------------------------------------------------
>
> Key: FELIX-784
> URL: https://issues.apache.org/jira/browse/FELIX-784
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Reporter: Rob Walker
> Priority: Trivial
>
> Some of the Http properties still use the old Oscar prefix.
> The following set is proposed for the old and new equivalent names:
> org.ungoverned.osgi.bundle.https.enable -----> org.apache.felix.https.enable
> org.ungoverned.osgi.bundle.https.provider -----> org.apache.felix.https.provider
> org.ungoverned.osgi.bundle.https.keystore -----> org.apache.felix.https.keystore
> org.ungoverned.osgi.bundle.https.password -----> org.apache.felix.https.password
> org.ungoverned.osgi.bundle.https.key.password -----> org.apache.felix.https.key.password
> org.apache.felix.http.jetty.debug -----> org.apache.felix.http.debug
> Whilst the latter already has a "felix" name, if Felix adds a later lightweight/non-jetty it will make for simpler migration to have a non-jetty specific property name
> For backwards compatibility it is probably best to create newer "felix" alternatives in parallel to the older style name, so either name may be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-784) Create "felix" property name as
alternatives to old style Oscar property names
Posted by "Rob Walker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641409#action_12641409 ]
Rob Walker commented on FELIX-784:
----------------------------------
Main reason for keeping them was for Apps like ours, with users out in the field with existing config files.
Keeping backwards compatibility means lower rollout effort of new versions, and doesn't create much extra dev work my side.
> Create "felix" property name as alternatives to old style Oscar property names
> ------------------------------------------------------------------------------
>
> Key: FELIX-784
> URL: https://issues.apache.org/jira/browse/FELIX-784
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Reporter: Rob Walker
> Priority: Trivial
>
> Some of the Http properties still use the old Oscar prefix.
> The following set is proposed for the old and new equivalent names:
> org.ungoverned.osgi.bundle.https.enable -----> org.apache.felix.https.enable
> org.ungoverned.osgi.bundle.https.provider -----> org.apache.felix.https.provider
> org.ungoverned.osgi.bundle.https.keystore -----> org.apache.felix.https.keystore
> org.ungoverned.osgi.bundle.https.password -----> org.apache.felix.https.password
> org.ungoverned.osgi.bundle.https.key.password -----> org.apache.felix.https.key.password
> org.apache.felix.http.jetty.debug -----> org.apache.felix.http.debug
> Whilst the latter already has a "felix" name, if Felix adds a later lightweight/non-jetty it will make for simpler migration to have a non-jetty specific property name
> For backwards compatibility it is probably best to create newer "felix" alternatives in parallel to the older style name, so either name may be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.