We would like to start next week. We have a few wrinkles to work out yet, like deciding on what JSDT projects to map our e4 work to, and how we want to promote the use of JSDI as API.
So far I think we have decided to make:
*.jsdt.debug.core encloses:
org.eclipse.e4.languages.javascript.debug.jsdi,
org.eclipse.e4.languages.javascript.debug.model
*.jsdt.debug.ui encloses:.
org.eclipse.e4.languages.javascript.debug.ui
*.jsdt.debug.launching (*.jsdt.launching perhaps?) encloses:
org.eclipse.e4.languages.javascript.debug.connect
*.jsdt.debug.rhino encloses:
org.eclipse.e4.languages.javascript.debug.jsdi.rhino
org.eclipse.e4.languages.javascript.debug.rhino
Michael Rennie
IBM Canada.
From: Nitin Dahyabhai/Raleigh/i...@ibmus
To: [email protected]
Cc: Simon Kaegi/Ottawa/i...@ibmca, Michael Rennie/Ottawa/i...@ibmca
Date: 2010/02/17 10:12 AM
Subject: webtools.jsdt project provisioned: what's next?
"Webmaster(Matt Ward)" <[email protected]> wrote on 02/17/2010 10:05:29
AM:
> From: "Webmaster(Matt Ward)" <[email protected]>
...
> The webtools.jsdt project is all set up and ready to go!
JSDT has now been provisioned as its own project under WTP. The next step
would be to move the existing JSDT modules into the new location, but I'm
pretty sure David handled the specifics of that when the WST and JST
projects were first split (alternately, I wasn't paying attention that time
or this really isn't the next step). I'm guessing this is something we'd
want to schedule very carefully, at least to keep the builds from failing
at an inopportune part of the week?
And to our newest Committers, Simon and Michael, I believe the same
question is in order? How soon do you want to begin moving your modules
in?
Regards,
---
Nitin Dahyabhai
Eclipse WTP Source Editing
IBM Rational
<<inline: graycol.gif>>
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
