[
https://issues.apache.org/jira/browse/SLING-12955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-12955:
------------------------------------
Description: With SLING-9117 an error marker is added to the pom whenever
there could be no jcr_root directory found. However sometimes the package is
rather being populated through embeds of the filevault-package-maven-plugin
itself (e.g. in this module being generated by the AEM archtype:
https://github.com/adobe/aem-project-archetype/tree/develop/src/main/archetype/all).
I would suggest to raise this message just as a warning or even with lower
severity. At the same time the detection of jcr_root should never dive into the
target folders as those jcr_root folder are very volatile. Rather in such cases
there should be no web content root being set. (was: With SLING-9117 an error
marker is added to the pom whenever there could be no jcr_root directory found.
However sometimes this is rather being populated through embeds of the
fillevault-package-maven-plugin itself (e.g. in this module being generated by
the AEM archtype:
https://github.com/adobe/aem-project-archetype/tree/develop/src/main/archetype/all).
I would suggest to raise this message just as a warning or even with lower
severity.)
> Lower severity of message "Could not detect jcr_root path for this content
> package!"
> ------------------------------------------------------------------------------------
>
> Key: SLING-12955
> URL: https://issues.apache.org/jira/browse/SLING-12955
> Project: Sling
> Issue Type: Improvement
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.3.0
> Reporter: Konrad Windszus
> Priority: Major
> Fix For: Sling Eclipse IDE 1.3.2
>
>
> With SLING-9117 an error marker is added to the pom whenever there could be
> no jcr_root directory found. However sometimes the package is rather being
> populated through embeds of the filevault-package-maven-plugin itself (e.g.
> in this module being generated by the AEM archtype:
> https://github.com/adobe/aem-project-archetype/tree/develop/src/main/archetype/all).
> I would suggest to raise this message just as a warning or even with lower
> severity. At the same time the detection of jcr_root should never dive into
> the target folders as those jcr_root folder are very volatile. Rather in such
> cases there should be no web content root being set.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
