Bug 1032789
| Summary: | Honour all schema locations setting is not disabled when creating a new project | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Rob Cernich <rcernich> |
| Component: | SwitchYard Editor | Assignee: | Rob Cernich <rcernich> |
| Status: | CLOSED WONTFIX | QA Contact: | Jiri Sedlacek <jsedlace> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.0.0 | CC: | atangrin, dlesage, kconner, oskutka, soa-p-jira |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The "Honour all schema locations" setting is not disabled when the user creates a new project in the SwitchYard Editor. This occurs if the project was created using a version that cannot be resolved from any configured Maven repositories. If the version specified in the wizard can be located, the preference is disabled appropriately. The user will encounter XML errors. To work around this fix the version and update the project, as this will install the SwitchYard facet, which will disable the XML validation setting.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-09-02 18:27:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Rob Cernich
2013-11-20 20:37:20 UTC
Rob Cernich <rcernich> made a comment on jira SWITCHYARD-1837 This only occurs if the project was created using a version that cannot be resolved from any configured maven repositories. If the version specified in the wizard can be located, the preference is disabled appropriately. The fix for this is probably more involved as it looks like the SwitchYard facet is not installed if this is the case (which is why the preference isn't updated). I'm not sure if there's any way for us to detect this and update the project accordingly. The user may have to use Maven->update project to fix the problem. Moving to 2.0 Rob Cernich <rcernich> updated the status of jira SWITCHYARD-1837 to Resolved Rob Cernich <rcernich> made a comment on jira SWITCHYARD-1837 Seeing as the project fails to be detected as a SwitchYard project, I don't think this is critical. Fixing the version and updating the project will install the SwitchYard facet, which will disable the xml validation setting. Dependent on upgrading tooling to JBDS 8 Andrej Podhradsky <apodhrad> updated the status of jira SWITCHYARD-1837 to Closed |