[
https://issues.apache.org/jira/browse/ISIS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337985#comment-17337985
]
ASF subversion and git services commented on ISIS-2640:
-------------------------------------------------------
Commit 9f25f8438f37a9ff5db8d2e77c83eb837e560eb5 in isis's branch
refs/heads/master from [email protected]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=9f25f84 ]
ISIS-2640: add new BeanSort: VETOED
also inspect types for @Profile annotations
> Spring @Profile support
> -----------------------
>
> Key: ISIS-2640
> URL: https://issues.apache.org/jira/browse/ISIS-2640
> Project: Isis
> Issue Type: Improvement
> Components: Isis Core
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-M6
>
>
> We have support for @Vetoed and @Programmatic at type level. In addition we
> should also support Spring's @Profile annotation, to allow for the framework
> to decide at runtime, which types must not contribute to the meta-model.
> A valid use-case is the demo-app, that we want to either showcase JDO or JPA
> features.
> 2 profiles 'demo-jdo' and 'demo-jpa' are used, to decide what persistence
> stack to provision and what is effectively shown/hidden with the demo.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
