[ 
https://issues.apache.org/jira/browse/JCRVLT-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750583#comment-17750583
 ] 

Konrad Windszus commented on JCRVLT-713:
----------------------------------------

I prepared 
https://github.com/apache/jackrabbit-filevault-package-maven-plugin/pull/95 
which leads to build failure in case either {{jcrSourceDirectory}} or 
{{metaInfVaultDirectory}} is inside the {{workDirectory}}. [~royteeuwen] Can 
you cross-check?

> filevault-package-maven-plugin wrongly reports duplicate files for same path
> ----------------------------------------------------------------------------
>
>                 Key: JCRVLT-713
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-713
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>            Reporter: Roy Teeuwen
>            Assignee: Konrad Windszus
>            Priority: Major
>
> I have the following setup:
>  * a maven plugin generates css files from scss files in the 
> src/main/content/jcr_root folder, add's them to target/vault-work/jcr_root/...
>  * maven resources plugin adds all the other files that are in the 
> src/main/content/jcr_root to the target/vault-work/jcr_root
>  * filevault-package-maven-plugin creates the package, with as settings 
> jcrRootSourceDirectory = 
> ${project.build.directory}/vault-work/jcr_root
> When doing this, the filevault plugin throws errors on duplicate files, for 
> example:
> {code:java}
> Found duplicate file 'jcr_root/apps/author/websites/general/css/_header.scss' 
> from sources 
> 'target/vault-work/jcr_root/apps/author/websites/general/css/_header.scss' 
> and 
> 'target/vault-work/jcr_root/apps/author/websites/general/css/_header.scss'{code}
>  
> As you can see, this is two times the same path.
> I'm not sure if this is fixable through different plugin configuration? I can 
> make a PR that checks if both paths are the same before logging as duplicate 
> file, but that just sounds like a workaround instead of a correct fix
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to