[JBoss JIRA] (JBIDE-24960) JBDS 11 produces warnings about missing schemas inconsistently
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24960?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-24960:
-------------------------------
Fix Version/s: 4.5.1.Final
(was: 4.5.1.AM3)
> 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.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-24960) JBDS 11 produces warnings about missing schemas inconsistently
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24960?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24960:
----------------------------------
Assignee: Rob Stryker (was: Jeff MAURY)
> 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.AM3
>
>
> 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.2.3#72005)
8 years, 6 months
[JBoss JIRA] (JBIDE-25118) improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6
by Mat Booth (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25118?page=com.atlassian.jira.plugi... ]
Mat Booth commented on JBIDE-25118:
-----------------------------------
Nice work, I think we're done for now. :-)
> improve errata waiver check script - add waivers for desktop-file-sanity, patches, IP v6
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-25118
> URL: https://issues.jboss.org/browse/JBIDE-25118
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, rpm
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: release
> Fix For: 4.5.1.Final
>
> Attachments: errata-waiver.results-can't-find-dali.txt
>
>
> {quote}
> It sounds like we could add these check types to my script:
>
> * desktop-file-sanity (always waive?)
> * IP v6 (always waive using existing waiver details, eg., https://errata.devel.redhat.com/rpmdiff/show/182126?result_id=5028358
> Yep, yep.
>
> * patches (waive if %autopatch)
> And if the only other complaints are "patch not applied" (I'm not sure if this check may throw different kinds of error){quote}
> So, the next time we have an errata with the above types of issues, I can update this script [1] to add those use cases.
> [1] https://github.com/jbosstools/jbosstools-build-ci/blob/master/util/errata...
> cc: [~mat.booth]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months