[jbosstools-issues] [JBoss JIRA] (JBIDE-15825) JAX-RS problems don't show up after target runtime is set

[ https://issues.jboss.org/browse/JBIDE-15825?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15825: --------------------------------------- Postponing to 4.2.0.Alpha1 since the expected validation problem appear as soon as a Project>Clean is executed. Some thoughts on how to fix that: the change listeners should not respond to classpath changes (as it's already the case), but it could accept changes on some classes, as the log show that this happened after the target runtime was set: {code} 16:42:08.627 [Worker-15] TRACE **ignored** Delta /test2/build/classes/MyAnnotation.class [Changed] ... 16:42:08.629 [Worker-15] DEBUG JAX-RS Metamodel for project 'test2' now has 0 Applications, 6 HttpMethods, 0 Resources and 0 Endpoints. ... 16:42:08.955 [Worker-11] DEBUG *** Validating project test2 after files [L/test2/.settings/org.eclipse.wst.common.project.facet.core.xml] changed... *** ... {code} In that case, if JDT can provide us with the associated Java source file, the JAX-RS builder could look at this source file, instanciate a custom JAX-RS HTTP Method element from it (which is not the case ATM). This element would be part of the validation (even if only org.eclipse.wst.common.project.facet.core.xml is marked as a changed file). -- 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