You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2011/07/13 16:21:00 UTC
[jira] [Commented] (SLING-2008) Move properties support to own
class
[ https://issues.apache.org/jira/browse/SLING-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064582#comment-13064582 ]
Justin Edelson commented on SLING-2008:
---------------------------------------
Is there a new location for OsgiUtil.createEvent? If not than the whole class shouldn't be deprecated, just the moved methods.
> Move properties support to own class
> ------------------------------------
>
> Key: SLING-2008
> URL: https://issues.apache.org/jira/browse/SLING-2008
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: Commons OSGi 2.0.6
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Commons OSGi 2.1.0
>
>
> Currently the OsgiUtil class has two purposes : support for property/configuration handling and support for event creation.
> When embedding this class in another bundle, this bundle requires an import to the event package although it is never really used.
> Therefore we should split the OsgiUtil class in several classes - each with a specific purpose. The OsgiUtil implementation will then just call the methods from the new classes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira