[
https://issues.jboss.org/browse/JBIDE-17549?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-17549.
---------------------------------
Resolution: Done
I put these entries back into plugin.xml since it seems to work better. I've verified
that at the very least, this works, and that's the higher importance than any benefits
we'd get from exposing our catalog for others to use.
XML file generated from catalog contains absolute paths
-------------------------------------------------------
Key: JBIDE-17549
URL:
https://issues.jboss.org/browse/JBIDE-17549
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Beta2
Reporter: Martin Malina
Assignee: Rob Stryker
Fix For: 4.2.0.Beta3
Copied over from JBIDE-16358.
When I create a xml file from schema, it contains absolute path:
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee
jar:file:/Users/rasp/jbossqa/JBDS/8.0.0/jbdevstudio-8.0.0.Beta2-106/studio/plugins/org.jboss.tools.as.catalog_3.0.0.Beta2-v20140528-1139-B52.jar!/schema/xsd/jboss-web_5_1.xsd
"
Also, notice the extra space at the end. Validation seems to work, but shouldn't it
point to the schema online? Or at least using a relative path?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)