You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "David Savage (JIRA)" <ji...@apache.org> on 2009/09/13 12:38:57 UTC
[jira] Created: (FELIX-1586) Framework reports
org.osgi.framework.version as 1.3
Framework reports org.osgi.framework.version as 1.3
---------------------------------------------------
Key: FELIX-1586
URL: https://issues.apache.org/jira/browse/FELIX-1586
Project: Felix
Issue Type: Bug
Components: Framework
Affects Versions: felix-2.0.0
Reporter: David Savage
Framework version is tested in ServiceTracker line 248 to check if the framework supports ServiceEvent#MODIFIED_ENDMATCH which is needed in some dosgi scenarios to support ListenerHooks. For this to work the version needs to be 1.5.0 or greater, but the constant appears to be hard coded to 1.3 in FelixConstants?
A quick hack to change the version to 1.5 enabled the ListenerHook behaviour but unsure if this has wider consequences?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-1586) Framework reports
org.osgi.framework.version as 1.3
Posted by "David Savage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Savage reassigned FELIX-1586:
-----------------------------------
Assignee: David Savage
> Framework reports org.osgi.framework.version as 1.3
> ---------------------------------------------------
>
> Key: FELIX-1586
> URL: https://issues.apache.org/jira/browse/FELIX-1586
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: felix-2.0.0
> Reporter: David Savage
> Assignee: David Savage
> Fix For: felix-2.2.0
>
>
> Framework version is tested in ServiceTracker line 248 to check if the framework supports ServiceEvent#MODIFIED_ENDMATCH which is needed in some dosgi scenarios to support ListenerHooks. For this to work the version needs to be 1.5.0 or greater, but the constant appears to be hard coded to 1.3 in FelixConstants?
> A quick hack to change the version to 1.5 enabled the ListenerHook behaviour but unsure if this has wider consequences?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-1586) Framework reports
org.osgi.framework.version as 1.3
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard S. Hall updated FELIX-1586:
-----------------------------------
Fix Version/s: felix-2.2.0
> Framework reports org.osgi.framework.version as 1.3
> ---------------------------------------------------
>
> Key: FELIX-1586
> URL: https://issues.apache.org/jira/browse/FELIX-1586
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: felix-2.0.0
> Reporter: David Savage
> Fix For: felix-2.2.0
>
>
> Framework version is tested in ServiceTracker line 248 to check if the framework supports ServiceEvent#MODIFIED_ENDMATCH which is needed in some dosgi scenarios to support ListenerHooks. For this to work the version needs to be 1.5.0 or greater, but the constant appears to be hard coded to 1.3 in FelixConstants?
> A quick hack to change the version to 1.5 enabled the ListenerHook behaviour but unsure if this has wider consequences?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1586) Framework reports
org.osgi.framework.version as 1.3
Posted by "David Savage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Savage closed FELIX-1586.
-------------------------------
Resolution: Fixed
> Framework reports org.osgi.framework.version as 1.3
> ---------------------------------------------------
>
> Key: FELIX-1586
> URL: https://issues.apache.org/jira/browse/FELIX-1586
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: felix-2.0.0
> Reporter: David Savage
> Assignee: David Savage
> Fix For: felix-2.2.0
>
>
> Framework version is tested in ServiceTracker line 248 to check if the framework supports ServiceEvent#MODIFIED_ENDMATCH which is needed in some dosgi scenarios to support ListenerHooks. For this to work the version needs to be 1.5.0 or greater, but the constant appears to be hard coded to 1.3 in FelixConstants?
> A quick hack to change the version to 1.5 enabled the ListenerHook behaviour but unsure if this has wider consequences?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1586) Framework reports
org.osgi.framework.version as 1.3
Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754710#action_12754710 ]
Richard S. Hall commented on FELIX-1586:
----------------------------------------
There are no consequences for changing that property value, it was just a miss on my part. We will change it in the next maintenance release. Thanks.
> Framework reports org.osgi.framework.version as 1.3
> ---------------------------------------------------
>
> Key: FELIX-1586
> URL: https://issues.apache.org/jira/browse/FELIX-1586
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: felix-2.0.0
> Reporter: David Savage
> Fix For: felix-2.2.0
>
>
> Framework version is tested in ServiceTracker line 248 to check if the framework supports ServiceEvent#MODIFIED_ENDMATCH which is needed in some dosgi scenarios to support ListenerHooks. For this to work the version needs to be 1.5.0 or greater, but the constant appears to be hard coded to 1.3 in FelixConstants?
> A quick hack to change the version to 1.5 enabled the ListenerHook behaviour but unsure if this has wider consequences?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.