[
https://issues.apache.org/jira/browse/DELTASPIKE-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313252#comment-16313252
]
John D. Ament commented on DELTASPIKE-1311:
-------------------------------------------
[~romain.manni-bucau] no this is a common use case (the on list reporter
mentions CDI 2.0). Vetoed will work, I just worry about not having a solution
for EE6 use cases. The problem is that the repository is not an actual bean,
but we register one, so we want to use {{@Vetoed}} or similar to indicate it
should not have a repository bean registered.
[~gpetracek] [~tandraschko] what about the idea of also introducing a config
property, e.g. {{com.mycompany.repository.RepositoryClass.vetoed=true}} to see
if it should be vetoed? Considered {{false}} by default.
> Allow Excluded Repositories
> ---------------------------
>
> Key: DELTASPIKE-1311
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1311
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Data-Module
> Affects Versions: 1.8.1
> Reporter: John D. Ament
> Assignee: John D. Ament
> Fix For: 1.8.2
>
>
> When a repository is discovered, if it has @Exclude on it, then don't include
> it as a possible repository bean.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
