[
https://issues.apache.org/jira/browse/SLING-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594197#action_12594197
]
fmeschbe edited comment on SLING-267 at 5/5/08 2:39 AM:
-----------------------------------------------------------------
I still think, we should not rename the jcr/base module to include the name
jackrabbit, simply because the node type loader uses the Jackrabbit API.
Rather we might want to separate node type definition out into a separate, yet
very small, bundle. This bundle we might name jackrabbit-nodetype-loader (or
so) to indicate the Jackrabbit dependency.
Of course, when doing this, triggering node type loading is different ....
After all, this issue is neglectable as JSR-283 will (finally) bring
standardized and better node type management. So we might just as well leave
what we have today and move to JSR-283 node type management as soon as the API
is published and implemented by Jackrabbit.
was (Author: fmeschbe):
I still think, we should not rename the jcr/base module to include the name
jackrabbit, simply because the node type loader uses the Jackrabbit API.
Rather we might want to separate node type definition out into a separate, yet
very small, bundle. This bundle we might name jackrabbit-nodetype-loader (or
so) to indicate the Jackrabbit dependency.
> Need a better name for the jcr/base module
> ------------------------------------------
>
> Key: SLING-267
> URL: https://issues.apache.org/jira/browse/SLING-267
> Project: Sling
> Issue Type: Improvement
> Components: Repository
> Reporter: Bertrand Delacretaz
> Priority: Minor
> Fix For: 2.0.0
>
>
> Currently being discussed on list,
> http://markmail.org/message/jln65ifegh3pi5qm
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
