Konrad Windszus created SLING-6344:
--------------------------------------
Summary: Support filter.xmls being generated by the
content-package-maven-plugin
Key: SLING-6344
URL: https://issues.apache.org/jira/browse/SLING-6344
Project: Sling
Issue Type: Bug
Components: IDE
Affects Versions: Sling Eclipse IDE 1.1.0
Reporter: Konrad Windszus
Priority: Critical
The content-package-maven plugin can not only consume a filter.xml from the
source directory, but also generate or merge filter.xmls. Therefore Sling IDE
should consider only the filter.xml in the generated artifacts (package). The
problem with that is, that content-package-maven-plugin does only generate that
filter.xml when it generates the real package.
There is one other related issue: In case a filter file is not found, the
method {{ResourceChangeCommandFactory#getFilterResult}} returns {{ALLOW}} while
it should return {{PREREQUISITE}} to not overwrite already existing nodes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
