Re: [wtp-dev] Clarify when JSDT completion is supposed to work

There are a few bugzillas which refer to broken CA for certain cases: [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=488912 [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=497903 On Mon, Sep 12, 2016 at 11:36 AM, Mickael Istria wrote: > Hi all, > > As I'm testing the

[wtp-dev] Clarify when JSDT completion is supposed to work

Hi all, As I'm testing the Neon.1 RC3 JavaScript package, I tried a few more scenarios than the usual (too) basic ones I'm doing. I got confused about JSDT's completion. In which cases is this supposed to work, in which cases not? I have found multiple places where we could expect some

[wtp-dev] [aeri] Weekly Problem Digest for Web Standard Tools ?4.6.0.i20160501

New problems reported last week Summary Reporters Status SeverityBug 1. ClassNotFoundException below OpenDeclarationHandler. (thrown in BundleLoader.findClassInternal)

[wtp-dev] [aeri] Weekly Problem Digest for JavaScript Development Tools ? 4.6.0.i20160501

New problems reported last week Summary Reporters Status SeverityBug 1. BadLocationException below JavaFormatter$VariableTracker.removeRangeMarkers (thrown in AbstractDocument.replace)

[wtp-dev] [aeri] Weekly Problem Digest for J2ee Standard Tools ? 4.6.0.i20160501

New problems reported last week Summary Reporters Status SeverityBug 1. ConcurrentModificationException below CommonPackageImpl.initializePackageContents (thrown in AbstractEList$EIterator.checkModCount)