[
https://issues.jboss.org/browse/JBIDE-18964?page=com.atlassian.jira.plugi...
]
Viacheslav Kabanovich edited comment on JBIDE-18964 at 12/16/14 1:26 PM:
-------------------------------------------------------------------------
CDI Core builder checks discovery mode change:
{code}
//5.2.a Update bean discovery mode.
if(updateBeanDiscoveryMode()) {
kind = FULL_BUILD;
}
{code}
and does full build when it happens.
Validator, however, starts with incremental build and has to detect that bean mode changed
since previous validation.
Current mode can be obtained as
{code}
CDICoreNature.getBeanDiscoveryMode()
{code}
Can validator be stateful, to keep last value of mode and compare it to the current one?
Alternatively, we can add to CDI model methods
{code}
boolean isFullValidationRequired();
void setFullValidationRequired(boolean b);
{code}
This will be of use when CDI builder for any reason decides that validation should be
full.
CDI validator, when doing by this hint full validation, will return that property to
false.
was (Author: scabanovich):
CDI Core builder checks discovery mode change:
{code}
//5.2.a Update bean discovery mode.
if(updateBeanDiscoveryMode()) {
kind = FULL_BUILD;
}
{code}
and does full build when it happens.
Validator, however, starts with incremental build and has to detect that bean mode changed
since previous validation.
Current mode can be obtained as
{code}
CDICoreNature.getBeanDiscoveryMode()
{code}
Can validator be stateful, to keep last value of mode and compare it to the current one?
Changing bean discovery mode doesn't run validation for existing
beans
----------------------------------------------------------------------
Key: JBIDE-18964
URL:
https://issues.jboss.org/browse/JBIDE-18964
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi
Affects Versions: 4.2.0.Final, 4.2.1.Final
Reporter: Rastislav Wagner
Assignee: Viacheslav Kabanovich
Fix For: 4.3.0.Alpha1
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)