[jira] [Commented] (JCRVLT-556) jackrabbit-packagetype validator wrongly complains about OSGI configurations in tools/config path

["Konrad Windszus (Jira)" <ji...@apache.org>]

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

Konrad Windszus commented on JCRVLT-556:
----------------------------------------

[~sseifert] Thanks for the report. Is that a regression of 3.5.2? Would you be able to add a PR with a failing test case?

> jackrabbit-packagetype validator wrongly complains about OSGI configurations in tools/config path
> -------------------------------------------------------------------------------------------------
>
>                 Key: JCRVLT-556
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-556
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: validation
>    Affects Versions: 3.5.2
>            Reporter: Stefan Seifert
>            Priority: Major
>
> scenario: content package project
> https://github.com/stefanseifert/filevault-package-maven-plugin-validation-issues/tree/master/content-packages/sample-content
> compile package with filevault-package-maven-plugin 1.1.9-SNAPSHOT using filevault 3.5.2
> validation fails with:
> {noformat}
> [ERROR] ValidationViolation: "jackrabbit-packagetype: Package of type 'CONTENT' is not supposed to contain OSGi bundles or configurations!", filePath=jcr_root\content\filevaultsample\en\tools\config\.content.xml, nodePath=/content/filevaultsample/en/tools/config, line=3
> [ERROR] ValidationViolation: "jackrabbit-packagetype: Package of type 'CONTENT' is not supposed to contain OSGi bundles or configurations!", filePath=jcr_root\content\filevaultsample\en\tools\config\.content.xml, nodePath=/content/filevaultsample/en/tools/config/jcr:content, line=8
> {noformat}
> but this is wrong, as the folder does not contain any OSGi configurations or bundle. it simply has the name /config - but this surely is not enough to "prove" it's illegal in a CONTENT package? any CMS user may create a path with a name like this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)