Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 60508

Summary: Extension shows warnings when using included schema elements
Product: [Eclipse Project] PDE Reporter: Jared Burns <jared_burns>
Component: UIAssignee: 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 CLA 2004-04-29 17:06:45 EDT
org.eclipse.jdt.debug.ui/plugin.xml shows warnings on its extensions to the org.eclipse.debug.ui.
launchShortcuts extension point. The warnings complain about invalid references which should, in 
fact, be covered by an <include> statement in the launchShortcuts schema (org.eclipse.debug.
ui/schema/launchShortcuts.exsd).

It's possible that there's some error on our side here? The <include> statement in the 
launchShortcuts schema is available in the HEAD version of Debug UI. It's not in an integration 
build yet.
Comment 1 Wassim Melhem CLA 2004-04-29 18:05:57 EDT
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?
Comment 2 Dejan Glozic CLA 2004-04-29 18:41:01 EDT
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.
Comment 3 Wassim Melhem CLA 2004-04-29 18:45:01 EDT
*** Bug 60087 has been marked as a duplicate of this bug. ***
Comment 4 Wassim Melhem CLA 2004-04-29 18:46:23 EDT
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 ;-)
Comment 5 DJ Houghton CLA 2004-04-30 08:02:40 EDT
Even worse...since its closer to release time I've traded in the hammer for an
axe.  I find that its more "modivating". :-)
Comment 6 Jared Burns CLA 2004-06-07 16:20:10 EDT
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.
Comment 7 Wassim Melhem CLA 2004-06-07 16:24:15 EDT
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
Comment 8 Jared Burns CLA 2004-06-14 11:18:00 EDT
*** Bug 66927 has been marked as a duplicate of this bug. ***
Comment 9 Darin Wright CLA 2004-06-14 13:39:02 EDT
*** Bug 67045 has been marked as a duplicate of this bug. ***
Comment 10 Wassim Melhem CLA 2004-06-20 21:23:18 EDT
This was a combination of two problems:
1. a bug the launchShortcuts schema (bug 67463)
and 
2. a bug in PDE's handling of included schemas (bug 64182)

Bug 60087 is not a dup of this one, and I have therefore reopened it.

*** This bug has been marked as a duplicate of 64182 ***