You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2009/04/07 13:41:13 UTC

[jira] Commented: (SLING-916) Consistently place non-exported classes into packages containing impl or internal

    [ https://issues.apache.org/jira/browse/SLING-916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12696487#action_12696487 ] 

Felix Meschberger commented on SLING-916:
-----------------------------------------

Rev. 762681: commons/log
Rev. 762683: extensions/threaddump
Rev. 762685: extensions/fsresource
Rev. 762686: extensions/i18n (just remove javadoc plugin config which will be inherited from parent)
Rev. 762699: servlets/resolver
Rev. 762703: servlets/get
Rev. 762707: parent: defaults for JavaDoc generation and preparation for site generation

> Consistently place non-exported classes into packages containing impl or internal
> ---------------------------------------------------------------------------------
>
>                 Key: SLING-916
>                 URL: https://issues.apache.org/jira/browse/SLING-916
>             Project: Sling
>          Issue Type: Improvement
>          Components: General
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> To simplify generation of JavaDocs as well as for consistency, internal classes should always be located in packages whose name contains
> either impl or internal. All Sling bundles, which contain a mix of exported and private packages are currently already implemented like this.
> Sling bundles, which do not export anything, for example the commons/log or the extensions/fsresource bundle, are not implemented in this way.
> This issue is about aligning these bundles with the consistent setup.

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