[
https://issues.apache.org/jira/browse/JCRVLT-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964398#comment-16964398
]
Stefan Seifert commented on JCRVLT-355:
---------------------------------------
i can confirm that it works with 1.0.5-SNAPSHOT for conf-content (but only
after fixing invalid filter rules reported with the latest snapshot of the
plugin):
https://github.com/stefanseifert/filevault-package-maven-plugin-1.0.4-validation-issues/commit/2eeae01e72a502347ede8081d10d4ea49ac64849
for ui-apps i get the same errors as listed in your commet using 1.0.5-SNAPSHOT.
what i want to achieve is to maven-filter some files in the client library
folder - e.g. for replacing "${project.version}-${buildNumber}" in the
epsilon65Project.all clientlib .content.xml in the final package. i cannot do
this in the source folder, as it should replace the variables only when
building the package. how is this possible without manually copying (and
filtering) the files using build-helper-maven-plugin together wit the latest
filevaule-package-maven-plugin?
> False error in case embedded file/subpackage is overwritten by
> jcrRootSourceDirectory
> -------------------------------------------------------------------------------------
>
> Key: JCRVLT-355
> URL: https://issues.apache.org/jira/browse/JCRVLT-355
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: package maven plugin
> Affects Versions: package-maven-plugin-1.0.4
> Reporter: Stefan Seifert
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: package-maven-plugin-1.1.0
>
>
> i've found problem with the check introduced with JCRVLT-279 - or i do not
> understand why the check leads to a failure in my case.
> i've two projects where this happens:
> 1. conf-content:
> https://github.com/stefanseifert/filevault-package-maven-plugin-1.0.4-validation-issues/tree/master/content-packages/conf-content
> fails with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.jackrabbit:filevault-package-maven-plugin:1.0.4:package
> (default-package) on project
> mycompany.myprojectgroup.myproject1.conf-content:
> org.apache.maven.plugin.MojoFailureException: Found duplicate files in
> content package, most probably you have overlapping filter roots or you embed
> a file which is already there in 'jcrRootSourceDirectory'. For details check
> the nested exception!: Duplicate file
> jcr_root\conf\myproject1\settings\wcm\policies was found and the duplicate
> attribute is 'fail'. {noformat}
> 2. ui.apps
> https://github.com/stefanseifert/filevault-package-maven-plugin-1.0.4-validation-issues/tree/master/content-packages/ui.apps
> fails with:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.jackrabbit:filevault-package-maven-plugin:1.0.4:package
> (default-package) on project mycompany.myprojectgroup.myproject1.ui.apps:
> org.apache.maven.plugin.MojoFailureException: Found duplicate files in
> content package, most probably you have overlapping filter roots or you embed
> a file which is already there in 'jcrRootSourceDirectory'. For details check
> the nested exception!: Duplicate file
> jcr_root\apps\epsilon65Project\clientlibs\.content.xml was found and the
> duplicate attribute is 'fail'.
> {noformat}
> the second project is a special case because in some files in the
> "clientlibs" folder placeholders are replaced using maven resource filtering,
> if the corresponding build-helper-maven-plugin definition is removed the
> build works.
> but the first project is really simple project.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
