Thanks for the quick respond. So, I'm going to try it again next week. To get to work with all that invalid or valid projects, is there some place where valid team project sets are posted now and then?
Regards, Matthias Kempka
On Oct 26, 2007, at 3:34 PM, David M Williams wrote: For one thing, I'll suggest JSDT questions be asked on wtp-dev list from now on ... we've started building JSDT as part of WTP just this week, as it's planned to be part of WTP 3.0. (where as ATF will stay a separate build, being that it's still incubating). That also explains some of what you are seeing ... "we" are making some changes to be consistent with other WTP project settings and cleaning up stuff like unused imports. And, just partially done, apparently. (I think I forgot to commit some changes, or something). There are some plugins, like the debug and test ones are not used and needs the most cleanup and should just be closed (or deleted) from your workspace as they are not yet valid for use). Apologies for the rough transition, but I expect it to be in better order next week. In the mean time, reducing the settings severity is a good work around. Hi all, I'm evaluating how to bring type support for classes defined in frameworks like qooxdoo to JSDT. For that, I checked out the JSDT projects from the CVS on Tuesday, compiled and ran it to see what works and what not. Now I'm back and noticed about 3000 changes in the CVS. I got those and now many of my projects are red. Most of it seems to be missing resources, so here is a list of my problems: Where do I get the schema definitions for extension points in org.eclipse.wst.jsdt.core: classpathVariableInitializer classpathContainerInitializer codeFormatter compilationParticipant org.eclipse.wst.jsd.ui: all defined extension points ? The plug-in org.eclipse.wst.jsdt says it would export packages com.sun.jdi and some more child packages. Many classes in that plug- in depend on classes in those packages, too, but I don't find com.sun.jdi.* anywhere. It seems I am missing a source folder named "src-jdi". The build.properties talk about a source folder src-jdi which can not be found. The plug-in org.eclipse.wst.jsdt.support.firefox has it's compilation settings set to error for unused imports and variables. This results in a lot of compilation errors, which is odd, since it is in the CVS exactly like this. Once I reduce the compiler settings, everything's back to normal. Best regards, Matthias Kempka -- Matthias Kempka Innoopract Informationssysteme GmbH mkempka@xxxxxxxxxxxxxx Tel: 0721 - 66 47 33 - 0 Fax: 0721 - 66 47 33 29 ========================= Legal Disclaimer ===================== According to Section 80 of the German Corporation Act Innoopract Informationssysteme GmbH must indicate the following information: Address: Stephanienstrasse 20, 76133 Karlsruhe Germany General Manager: Jochen Krause, Eric von der Heyden Registered Office: Karlsruhe, Commercial Register Karlsruhe HRB 7883 ============================================================ _______________________________________________ atf-dev mailing list atf-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/atf-dev
_______________________________________________ atf-dev mailing list
-- Matthias Kempka Innoopract Informationssysteme GmbH Tel: 0721 - 66 47 33 - 0 Fax: 0721 - 66 47 33 29 ========================= Legal Disclaimer ===================== According to Section 80 of the German Corporation Act Innoopract Informationssysteme GmbH must indicate the following information: Address: Stephanienstrasse 20, 76133 Karlsruhe Germany General Manager: Jochen Krause, Eric von der Heyden Registered Office: Karlsruhe, Commercial Register Karlsruhe HRB 7883 ============================================================
|