[wtp-dev] XSL Tools Compilation Error
It appears that in 3.6M4, there is an API change for the AbstractTemplatesPage class from the org.eclipse.ui.workbench bundle. They changed an abstract protected class to be public, and is causing our current code to fail. I've opened bug 297024 with the platform text team about this issue. https://bugs.eclipse.org/bugs/show_bug.cgi?id=297024 Dave ___ wtp-dev mailing list wtp-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/wtp-dev
Re: [wtp-dev] XSL Tools Compilation Error
I think I have a fix for this that works for 3.5 and 3.6M4. Released and running a build now. Dave David Carver wrote: It appears that in 3.6M4, there is an API change for the AbstractTemplatesPage class from the org.eclipse.ui.workbench bundle. They changed an abstract protected class to be public, and is causing our current code to fail. I've opened bug 297024 with the platform text team about this issue. https://bugs.eclipse.org/bugs/show_bug.cgi?id=297024 Dave ___ wtp-dev mailing list wtp-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/wtp-dev ___ wtp-dev mailing list wtp-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/wtp-dev
Re: [wtp-dev] extending the jsp editor
Andrew Eisenberg wrote: Well, I made some changes to the grammar and the skeleton file, and ran the tests. Unfortunately, the changes I made will not allow the new grammar to be compiled using the old version of jflex. Also, I have 8 tests failing. I can create a bug report and attach the new grammar file. I expected that they'd not be able to compile with both versions unmodified--it's the price we pay for not keeping within JFlex's APIs. Attaching the changed version to a bug would be most helpful, assuming you mean changes made to port the grammar forward, and not for its use with gsps. -- --- Nitin Dahyabhai Eclipse WTP Source Editing IBM Rational ___ wtp-dev mailing list wtp-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/wtp-dev
[wtp-dev] JUnit 4: Am I silly and embarrassed? Or missing something?
Or all of the above? With the recent notes about the inclusion of org.junit version 4, and from following several bugs, I got the impression that we _had_ to make the kind of adjustments so well described in http://wiki.eclipse.org/Eclipse/Testing/JUnit4_Changes or else our tests would fail. Over the weekend, I updated to latest platform I-build prereq and ran a few test builds. I expected our unit tests to fail all over the place, since few have made the described adjustments. But ... all the tests ran just fine! So, I'm thinking maybe I have been misunderstanding all along? Or, maybe it is because no one in WTP is yet trying to use junit version 4? Or, perhaps our test scripts are different enough from the standard one (from Platform) that we are not effected? Or, maybe I'm missing something? Is it only running in the IDE that it matters? And does not matter when ran in batch mode? I currently can not get Run As ... plugin unit test to run in my workbench, so maybe that is where it does matters (but, its not failing in ways described, and I haven't ran any tests in my workspace for months, so not sure what shape it is in). Maybe I'm the only one confused, but thought I'd post this comment, and look forward to hearing of others experiences, if successful, or seeing your bug reports if not. :) Thanks, ___ wtp-dev mailing list wtp-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/wtp-dev
[wtp-dev] How to add the rename action to the extensions tab of the property view of wsdl editor
Hi all, I want to add the Refactor and Reference action to the extension element of wsdl element in the extension tab, Property view of the wsdl editor. How can I do? Thanks! Grid ___ wtp-dev mailing list wtp-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/wtp-dev
