[
https://issues.apache.org/jira/browse/SLING-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12912571#action_12912571
]
Carsten Ziegeler commented on SLING-1787:
-----------------------------------------
Renamed the two providers to org.apache.sling.installer.provider.jcr and
org.apache.sling.installer.provider.file and moved the impl into the
corresponding impl packages
> Unify symbolic names and check package names
> --------------------------------------------
>
> Key: SLING-1787
> URL: https://issues.apache.org/jira/browse/SLING-1787
> Project: Sling
> Issue Type: Task
> Components: Installer
> Affects Versions: OSGi Installer 3.0.0, JCR Installer 3.0.0, File
> Installer 1.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: OSGi Installer 3.0.0, JCR Installer 3.0.0, File
> Installer 1.0.0
>
>
> The used symbolic names by the various parts of the installer (osgi
> installer, jcr installer, file installer) do not really have something in
> common, it would rather make sense to use a unified scheme, like
> org.apache.sling.installer.core (today: ...osgi.installer)
> org.apache.sling.installer.provider.jcr (today: ...jcr.jcrinstall)
> org.apache.sling.installer.provider.file (today: ...install.fileinstall)
> In addition, the package names should match these symbolic names:
> - the api goes to org.apache.sling.installer.core
> - the osgi impl moves to org.apache.sling.installer.core.impl.*
> - the providers use org.apache.sling.installer.provider.XYZ.impl.*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
