Bug 215329

Comment 1 David Williams 2008-03-02 03:19:31 EST

I'll make a couple of observations on this, though not sure what I'd recommend, yet. 

First, I find it surprising this issue would have existed for 2 years or so and no one else noticed or complained, so ... I'm wondering ... if something in the platform changed. And, in fact, it did, as they changed in M4 to allow for individual source jars, which changed how PDE and others "look up" source. 

And, while they claim backwards compatibility, they do not guarantee forward compatibility ... that is, if your dev. env. is, say, M3 then it might not work correctly against an M5 target. So ... some of use should be sure this behavior still exists with a "pure" M5 environment and an M5 target. 

If someone has the interest, I'd even appreciate knowing if the problem exists, say in a 3.3.x env. with a 3.3.x target (that'd be WTP 2.0.2). 

But ... seems there's a side issue of whether the schemas should be part of binary distribution ... which I'm sort of 50/50 on. I mostly believe anyone doing "add on" plugins should really have an SDK version installed, to get the proper help documents, etc, so that's a fair expectation. And, those wanting a runtime only environment, just to develop web apps might not like the extra info, not just for size, but also cluttering information? But, like I said, I can see other side too. 

Also, we are ready this coming week to start jarring our source plugins, see bug 132094 ... so, perhaps first we should wait till then to decide. Also, before deciding the binary/sdk issue, I'd like to open up to over committers comments on wtp-dev. Perhaps even some cross-platform input, to see if there is any Ganymede-wide agreement on how it should be (though, unlikely). 

Comment 2 David Williams 2008-04-05 03:38:10 EDT

I think this is fixed now in M6, given that we are jarring our source plugins. 

I had only Eclipse SDK as Dev. Env., and pointed to a complete install of WTP SDK as the target. 

Created a test plugin, added validation and sse to the dependencies page in manifest editor. Then found an extensions page and could "add" validation extension and others from SSE. When I clicked on Description, a web page was diplayed of the actual exsd contents. 

If you find cases that don't work, let me know (i.e. re-open). 

On the issue of having them in binary distributions vs. SDK, I would prefer to keep them in the SDK. Mostly since that's conceptually correct. (i.e. matches my model I  have of which-users-use-which) ... but, it is not a strong bias. If anyone wants to crusade the idea to put schemas in binary distributions, that you open a general bug on the topic, and advocate it on wtp-dev ... and see if you can convince anyone else to go along. 

Thanks,