[
https://issues.jboss.org/browse/JBIDE-9289?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-9289:
----------------------------------------------
I have found the cause and it will be useful to describe it here so that not to lose a lot
of time next time.
Usually I create a test project in studio, and then copy it into the test plugin. It works
fine in my environment. But, file .classpath is generated with
{code}
<classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/jdk1.6.0_21">
{code}
And it turns out that to work in any environment it should be just
{code}
<classpathentry kind="con"
path="org.eclipse.jdt.launching.JRE_CONTAINER">
{code}
CDI model should scan all web content folders
---------------------------------------------
Key: JBIDE-9289
URL:
https://issues.jboss.org/browse/JBIDE-9289
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdi (jsr-299)
Affects Versions: 3.3.0.M2
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.M3
Web root component in Eclipse can have several underlying resources. At present,
model/builder take only 'primary' resource.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira