[ https://issues.jboss.org/browse/JBIDE-10788?page=com.atlassian.jira.plugi... ] Rob Stryker edited comment on JBIDE-10788 at 9/21/15 5:00 PM: -------------------------------------------------------------- I'm linking this to JBIDE-473 Current suggestion is to add some type of marker provider which will check if a given WTP-style project is targeted to a jboss-as / wf / eap / etc runtime. If it is, we can check if the context root in the wtp project matches what we expect (via deployment preferences) for the actual context root to be on the server. If they don't match, we can add a marker on the project. This won't be of use to you if your project is targeting an openshift server / runtime combination, though, or if your project isn't a wtp-style project... but odds are your validator would need to do different tasks anyway (check the openshift project's various build config files instead) so the patches probably won't match or be re-usable, but can simply serve as instruction on what to do. was (Author: rob.stryker): I'm linking this to JBIDE-473 Current suggestion is to add some type of marker provider which will check if a given WTP-style project is targeted to a jboss-as / wf / eap / etc runtime. If it is, we can check if the context root in the wtp project matches what we expect (via deployment preferences) for the actual context root to be on the server. If they don't match, we can add a marker on the project. This won't be of use to you if your project is targeting an openshift server / runtime combination, though, and odds are your validator would need to do different tasks (check the openshift project's various build config files instead) so the patches probably won't match or be re-usable, but can simply serve as instruction on what to do. -- This message was sent by Atlassian JIRA (v6.4.11#64026)