Sorry to muddy the waters, but if the intent is to merge the fork
back into the JSDT project, can we hold off renaming the
packages/bundles? I'd love to hear from the JSDT project and PMC
regarding the offer before we make John change the code (the changes
will make merging more challenging).|
I took a quick look at the commit log and it does seem that you're only modifying JSDT core. A lot of these changes appear to just be good housekeeping sorts of things (lots of bug fixes) that I think would be good to have back in the project.
It looks like you've modified the core bundle to support NJSDoc, rather than extend via plug-in. Does it make sense to consider factoring out the NJSDoc specific stuff into a separate bundle?
NJSDoc itself is EPL-licensed; are you thinking of contributing this to the project as well?
Are you willing to join the project as a committer to support your enhancements?
If not JSDT, might this code fit in with VJet?
On 04/24/2013 10:12 PM, Mike Milinkovich wrote:
Back to the top