[
https://issues.jboss.org/browse/JBIDE-13739?page=com.atlassian.jira.plugi...
]
Fred Bricon edited comment on JBIDE-13739 at 3/28/13 5:16 AM:
--------------------------------------------------------------
no, you still have to run Maven > Project Update for non-JavaEE projects.
I know the behavior is inconsistent between non-JavaEE and JavaEE projects, but I wanted
to limit the CPU overhead of scanning each workspace project for CDI whenever *any* change
is detected in a project. Let's say it's a trade-off.
was (Author: fbricon):
no, you still have to run Maven > Project Update for non-JavaEE projects.
I know the beahvior is inconsistent between non-JavaEE and JavaEE projects, but I wanted
to limit the CPU overhead of scanning each workspace project for CDI whenever *any* change
is detected in a project. Let's say it's a trade-off.
CDI Support cannot be disabled if CDI Maven Configurator is installed
and enabled
---------------------------------------------------------------------------------
Key: JBIDE-13739
URL:
https://issues.jboss.org/browse/JBIDE-13739
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI, maven
Affects Versions: 4.0.1.Final
Reporter: Denis Golovin
Assignee: Fred Bricon
Fix For: 4.1.0.Alpha2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira