[
https://issues.apache.org/jira/browse/SLING-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-3089:
-----------------------------------
Fix Version/s: (was: Sling Eclipse IDE 1.2.2)
Sling Eclipse IDE 1.2.4
> Investigate using the same model between the repository sync and the Sling
> (JCR) content provider
> -------------------------------------------------------------------------------------------------
>
> Key: SLING-3089
> URL: https://issues.apache.org/jira/browse/SLING-3089
> Project: Sling
> Issue Type: Improvement
> Components: IDE
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: Sling Eclipse IDE 1.2.4
>
>
> If we use the same data model we can benefit from the same code base. Right
> now there's some duplication and we potentially miss fixes from one area from
> another. For instance, the content provider does not yet support properties
> stored in $(nodeName).dir/.content.xml files.
> Also, it would help in formalizing the SerializationManager API even more.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
