|(no subject) [message #671396 is a reply to message #671289]
||Tue, 17 May 2011 17:54
| David Williams
Registered: July 2009
On 05/17/2011 07:51 AM, Dwight Johnson wrote:|
> If however I download the entire WTP from HEAD it has tens
> of thousands of compiler errors.
> Where/how can I download Eclipse source for usage in
> debugger without compiler errors?
> Should I download WTP and regular Eclipse in one workspace?
Not sure how you define "the entire WTP", that's a lot!
But, assuming you really are getting (only) the released/distributed
bundles from HEAD, and
still seeing tens of thousands of errors, my guess it there are some
missing or mis-matched prereqs.
For HEAD code, the easiest way to get all the latest (matching)
pre-reqs, is to use the Java EE IDE package for Indigo M7, the most
recently built package, which would have most the pre-reqs in synch and
most of WTP.
If you are trying to do with Helios version, you really wouldn't want
HEAD anyway ... you'd want either R3_2_maintenance, or the exact version
that went into the build.
In either case, the easiest way to get started is to "Import", "Plugins
and Fragments", "from active target platform" (which should be entire
Java EE IDE, and -- here's the important part -- check the "Projects
from a repository". This makes use of a special tag in the bundle that
says exactly where it came from and which tagged version was used in
that build (but, does give the choice to get HEAD version instead, if
that's really what you want). This feature of Eclipse IDE (PDE) also
makes it easier to "start off small", getting just a few of the bundles
you are interested in, and adding more later if you find you need them.
To try and "get everything" wouldn't normally be a good thing to do
(there's so much).
But, if that's how you are getting source, and still getting tens of
thousands of errors ... then probably just a mis-match of versions too
far from HEAD version.
|Re: (no subject) [message #671523 is a reply to message #671396]
||Wed, 18 May 2011 08:13
| Dwight Johnson
Registered: March 2011
David, thanks for your time!|
The entire WTP is indeed a lot (more than 2GB), but if you don't know in advance what you need and what you don't need, there is not much choice.
Currently I am working on a plugin for Eclipse/Helios that is supposed to offer a development environment (adapted project, perspective, code completion and templates) for static webcontent (xhtml, js and css) with reduced/modified syntax as compared to standard web projects. And is precisely what I want to achieve: offer css/js/xhtml templates of my own, visibly in TemplatesView, with my templates stored in my plugin. My problem is that in contrast to the java editor, the css, js and xhtml editors do not display templates in the standard TemplatesView via Window/Show View/Other/Templates (although sttrangely there are templates defined, see Windows/Preferences). The templates view simply says 'No templates available'. So I need to find out what is happening via the debugger.
There are some vague pointers to be found on the web, like this, stating that I should provide for an adapter:
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .platform.doc.isv/reference/api/org/eclipse/ui/texteditor/te mplates/TemplatesView.html
I was able to get the debugger into TemplatesView.doCreatePage...
http://www.google.com/codesearch/p?hl=nl#smBcNx65Jqw/src/org /eclipse/ui/texteditor/templates/TemplatesView.java&q=te mplatesview&sa=N&cd=1&ct=rc
...seeing that for java ITemplatesPage was indeed not null, in contrast to the other editors, but I could not get deeper into the code, because of the compiler errors, so I need the eclipse code without compiler errors.
You advise me to download 'R3_2_maintenance' but when I google that I find:
http://dev.eclipse.org/viewcvs/viewvc.cgi/platform-launcher/ library/win32/eclipseWin.c?view=log&pathrev=R3_2_mainten ance
.. with dates 2005/2006. That cannot be right.
The only access I have to CVS is this:
In my CVS perspective I see:
Branches (as an end node)
...ah wait, 'Branches' has a context menu with 'Refresh Branches' that leads me to your R3_2_maintenance branche. I will check that out to see if I can get rid of these compiler errors. I will get back...
[Updated on: Wed, 18 May 2011 08:19]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.02704 seconds