[
https://issues.jboss.org/browse/JBIDE-24960?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-24960:
---------------------------------------
[~mjurc], I tried that and got this error:
{code}
Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-checkstyle-plugin:2.17:checkstyle (execution: check-style,
phase: compile)
{code}
I did not get the schema error.
But this doesn't really prove anything I'm afraid, because the EAP quickstart
could still fail. Can you check with the latest nightly of devstudio?
https://devstudio.redhat.com/11/snapshots/builds/devstudio.product_master/
JBDS 11 produces warnings about missing schemas inconsistently
--------------------------------------------------------------
Key: JBIDE-24960
URL:
https://issues.jboss.org/browse/JBIDE-24960
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsp/jsf/xml/html-source-editing
Affects Versions: 4.5.0.Final
Reporter: Michal Jurc
Assignee: Rob Stryker
Fix For: 4.5.1.Final
The following warning is produced by JBDS11 consistently upon import of
{{ejb-security-jaas}} quickstart:
||Description||Resource||Path||Location||Type||
|No grammar constraints (DTD or XML Schema) referenced in the
document.|wildfly-config.xml|/ejb-security-jaas/src/main/resources|line 1|XML Problem|
The {{ejb-remote}} quickstart uses the same configuration file ({{wildfly-config.xml}}),
however no such warning is produced unless the user selects the file to validate it.
This is inconsistent, confusing and it is not at all obvious where the JBDS is taking
schemas from - after all, {{wildlfy-config.xml}} is standard descriptor file for any
application using Elytron client with EAP7.1.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)