[
https://issues.jboss.org/browse/JBIDE-13739?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-13739:
-------------------------------------
The maven CDI configurator automatically enables CDI support if CDI dependencies are
detected in the classpath. I see we can improve things a bit :
- currently any change on the project would trigger the CDI configurator to run. That
includes changing the CDI support in the project properties. We only want the configurator
to be invoked manually (maven > update project), or if the project dependencies changed
(a cdi dependency was added)
- if the CDI nature *AND* the CDI Facet is installed, configuration is skipped. We can
choose to skip if one *OR* the other requirement is met. That way, CDI EJB or Web faceted
projects can manually disable CDI support.
This leaves one corner case : A non faceted project with CDI dependencies. CDI support
would be re-enabled after each Maven > Project Update action.
How do you think we could handle that use case?
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
--
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