[
https://issues.apache.org/jira/browse/JCRVLT-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747474#comment-17747474
]
Roy Teeuwen commented on JCRVLT-711:
------------------------------------
Konrad pointed me to the excludeTransitive property, which makes sure that an
embed is not added without it being a direct dependency. This fixes the issue
and does not require a custom validator
> Add validation to ban specific packages to be added as subpackage
> -----------------------------------------------------------------
>
> Key: JCRVLT-711
> URL: https://issues.apache.org/jira/browse/JCRVLT-711
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Reporter: Roy Teeuwen
> Priority: Major
>
> When having following reactor module:
> - all
> - core
> - ui.apps
> - ui.content
> - it.content
> I only want the it.content to be installed to specific environments, namely
> local and an automated builds environment. To do this, the it.content is
> defined in the embedded section of the filevault plugin, but I check if an
> environment variable is available and profile-wise add the it.content
> dependency. The setting failOnMissingEmbed is set to 'false'.
> I now had the case that another submodule created a dependency on it.content,
> making it.content available as dependency to the 'all' package and installed
> on the wrong environment.
> To fix this, I'd like to see if I can add a FileVault validation rule to the
> 'all' package to ban a specific subpackage to exist based on group and name
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
