|Re: [wtp-dev] JSDT Future|
The JSDT project is still active, the debug sub-component more so than the core and web areas in the last few months. Our next priority is to review the backlog of community submitted patches for inclusion in the 3.5 maintenance releases. We're also currently investigating a possible integration with a NJSDoc fork of JSDT.
Dawid, we'd be happy to accept any help. The best way is to open bugs/enhancements and submit patches, as I know you have already done.
Dawid Pakuła ---05/01/2013 01:35:39 PM---Hi, is there any plan to clean up jsdoc / inference engine ? How I can help?
From: Dawid Pakuła <dawid.pakula@xxxxxxxxx>
To: "General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>,
Date: 05/01/2013 01:35 PM
Subject: Re: [wtp-dev] JSDT Future
Sent by: wtp-dev-bounces@xxxxxxxxxxx
On Wednesday, 1 May 2013 at 15:33, Wayne Beaton wrote:
The GitHub mirrors are often out of date ; in this case, however, I think that what GitHub is reporting is accurate for this repository (this is more of a for-future-reference FYI)
The JSDT project has three Git repositories; the webtools.jsdt.debug.git repository's most recent commit occurred on April 10. The project is still active.
The relationship between VJet and JSDT has not been fully explored.
I'll leave the other questions for the project committers to asnwer.
On 05/01/2013 03:31 AM, Paul Verest wrote:
Back to the top