Hi,
The logic in the filevault-package-maven-plugin is as follows:
It looks for the first found directory below any of the following:
${project.basedir}/jcr_root,${project.basedir}/src/main/jcr_root,${project.basedir}/src/main/content/jcr_root,${project.basedir}/src/content/jcr_root,${project.build.outputDirectory}
(http://jackrabbit.apache.org/filevault-package-maven-plugin/package-mojo.html#jcrRootSourceDirectory)
This works pretty well and rarely forces anyone to reconfigure the plugin.
The list could be even extended to cater for other use cases like script in a
bundle...
Thanks,
Konrad
> On 9. Sep 2019, at 10:46, Radu Cotescu <[email protected]> wrote:
>
> Hi Robert,
>
> On Fri, 6 Sep 2019 at 17:49, Robert Munteanu <[email protected]> wrote:
>
>> Hi,
>>
>> I have added the htl-maven-plugin for validation to a content package
>> project. I noticed initially that the validation did process anything,
>> because of looking by default in ${project.build.sourceDirectory},
>> which is src/main/java.
>>
>> Would it make sense to change this default, so that it picks up expect
>> locations of htl scripts, e.g. jcr_root or src/main/content/jcr_root?
>>
>> Thanks,
>> Robert
>
>
> I guess such a change shouldn’t affect users, since we’ve always advised
> them to either change the source directory in the pom or configure the
> plugin. However, I’d stay away from JCR specific tooling and conventions as
> defaults.
>
> Cheers,
> Radu
>
>>
