| Summary: | Extension shows warnings when using included schema elements | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Jared Burns <jared_burns> |
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | curtispd, deboer, dj.houghton, eclipse |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Jared Burns
Jared, the schemas against which we validate the workspace plug-ins are the ones that come packaged with the build. We don't use the ones you have checked out from HEAD into your host workspace. Dejan, DJ opened a similar defect the other day. I'm not sure why the confusion. This has been the design from day 1, isn't it? I know, although expecting to pick up schemas in the workspace over those in the build is somewhat reasonable i.e. in line with the rest of PDE. *** Bug 60087 has been marked as a duplicate of this bug. *** I guess we should get with the times and modify the original behavior. Because if we don't, then DJ will start chasing me around the lab with a hammer again ;-) Even worse...since its closer to release time I've traded in the hammer for an axe. I find that its more "modivating". :-) We still have this problem, even in the current builds which have the <include> statement in the host version of the schemas. It's a real mess, in fact. We see different errors on the same file in different workspaces which are running on the same version of Eclipse with the same version of our plugin checked out of the repository. At home, I was seeing warnings all over the included elements in our plugin.xml. Here at the office, I only see warnings on the top-level nodes (<with variable="selection">) of our launchShortcut enablement expressions. Meanwhile Luc sees errors all over our launchShortcut extensions *and* all over our refactoring extensions. I think these are two different problems. There certainly seems to be a problem with PDE's handling of linked schemas. This will be addressed in bug 64182 *** Bug 66927 has been marked as a duplicate of this bug. *** *** Bug 67045 has been marked as a duplicate of this bug. *** |