You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2018/02/26 21:07:02 UTC
[jira] [Updated] (SLING-4017) Maintain a mapping of full coverage
aggregates
[ https://issues.apache.org/jira/browse/SLING-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu updated SLING-4017:
-----------------------------------
Fix Version/s: (was: Sling Eclipse IDE 1.2.2)
Sling Eclipse IDE 1.2.4
> Maintain a mapping of full coverage aggregates
> ----------------------------------------------
>
> Key: SLING-4017
> URL: https://issues.apache.org/jira/browse/SLING-4017
> Project: Sling
> Issue Type: Improvement
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.0.2
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: Sling Eclipse IDE 1.2.4
>
>
> When deleting it's impossible to know whether an something.xml file was a full coverage aggregate or an actual XML file. In most places we assume that it was a full coverage aggregate, but that's not always correct.
> We should maintain a mapping of such files as we encounter them and use that information when a file is deleted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)