||Tue, 16 June 2009 04:29
| Nitin Dahyabhai
Registered: July 2009
Sheshadri Mantha wrote:|
> i'm having the hardest time in getting / setting up a development env
> for WTP/JSDT (w/sdk source)
> the doc in HELP appears to be outdated (talks about releng etc.)... the
> FAQ on WTP seems to point to a way of setting up an env that includes
> WTP (or portions that i wish to load) through the update site. so i've
> followed the stuff on FAQ (which basically asks one to use Update
> manager) & loaded both the JSDT and JSDT SDK...
> first i created a std java project, added jsdt*.jar files and then to
> each jar file added the appropriate source. i can see the source... but
> it did not look to me like a java project i'm used to - the organization
> of packages, classes look weird...
> so i unzipped all the java files for all jsdt*.source* into a folder,
> loaded that folder as a Java Project and now i'm able to see all the
> class files, the js libraries etc.
> now if i can use that code to debug what happens w/in the JS editor i
> can start learning how inference engine etc. work. questions:
> 1. is rhino ( i'm assuming that js in jsdt gets xlated into java
> objects via Rhino - is correct? or am i confusing this with ATF? ) code
> already part of jsdt sources ?
There's no use of Rhino in JSDT (other than the odd image popping up
here and there), as we're not doing any translations like that. The
out of web pages in the workspace so they can be validated by JSDT.
Rhino may have been used in parts of ATF, but I'm not an expert on
> 2. how do i setup a project to start with a simple js file that say
> has one global scope var and function, and walk thru' the java source
> for code highlighting, inference etc. ? do i have the right setup
> (starting with j2ee, adding WTP w/ JSDT) ? or should i be in PDE ??
> i appreciate any HELP in walking me through this...
The hardest thing for most people to fully grasp is the idea that
you're not working with jar files just containing classes anymore,
where everything's put on the ClassPath and it runs. Eclipse is a
platform for plug-ins, and JSDT is merely a group of plug-ins, just
like everything else in WTP.
attempts to illustrate this. This is doubly important since you can
contribute to the inference engine and many other parts of JSDT
through your own plug-ins, and keeping the organizational separation
clear in your mind becomes vital later on.
If you're completely new to Eclipse, a quick read through the
( http://help.eclipse.org/stable/topic/org.eclipse.platform.do c.user/gettingStarted/qs-01.htm)
will help prevent a great deal of confusion when comes to the
vocabulary that's going to be thrown at you in the UI.
So once you're on board with the concept of plug-ins, there are two
steps to take: 1) making sure you have the Plug-in Development
Environment (PDE) installed, and 2) that you have the JSDT sources
at least viewable for debugging, if not completely editable for your
The PDE should be installable through the Update Manager where it is
probably called the "Eclipse Plug-in Development Environment". It's
also part of the downloadable Eclipse-SDK, but when you want to work
with existing plug-ins as your first exposure to it all, installing
the PDE through the Update Manager will be simpler.
Once completed, you'll be able to use the Import wizard (from the
File menu) to choose "Plug-ins and Fragments", accepting the
defaults in its first page, and selecting org.eclipse.wst.jsdt.*
from the left column of the second page. If we've assembled things
correctly, you should see a Referenced Libraries node in the Java
Perspective's Package Explorer under projects whose names correspond
to the plug-ins you chose. Jars located under it will contain
..class files, but opening the class files should expose the original
Java source in the editor, where you'll be able to do useful things
like set breakpoints using the left-hand ruler
( http://help.eclipse.org/ganymede/topic/org.eclipse.jdt.doc.u ser/concepts/cbrkpnts.htm).
This is just makes our sources viewable, though. For modifiable
sources, you can connect to our CVS server at
:pserver:firstname.lastname@example.org:/cvsroot/webtools and look in the
sourceediting/plugins folder for the raw JSDT plug-in projects
( http://help.eclipse.org/stable/topic/org.eclipse.platform.do c.user/tasks/tasks-96.htm
for how to check those out). Beware that if you're not familiar
with how CVS branches work, you really will want do all of this with
a Galileo build.
After that, it should just be a matter of launching a "runtime
workbench" based off of what's in your workspace. By default,
sources for plug-ins will compile against the copy of Eclipse you're
already running. I recommended getting PDE through Update Manager
for this reason--what you're running includes WTP and everything WTP
needs to run already.
illustrates this process. Once that's working, you're on your way!
Eclipse WTP Source Editing
Current Time: Mon May 29 15:21:12 GMT 2017
Powered by FUDForum
. Page generated in 0.02219 seconds