Eclipse Community Forums - RDF feed
https://www.eclipse.org/forums/
Eclipse Community ForumsHow to retrieve Eclipse source code without compiler errors?
https://www.eclipse.org/forums/index.php/mv/msg/209408/671289/#msg_671289
sometimes I have the need to understand the Eclipse code better so I download certain eclipse plugins source code step in the debugger if I am lucky enough to be able to download a plugin that has no compiler errors.
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?
Thanks in advance.
]]>Dwight Johnson2011-05-17T11:51:54-00:00(no subject)
https://www.eclipse.org/forums/index.php/mv/msg/209408/671396/#msg_671396
> ...
>
> 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.]]>David Williams2011-05-17T17:54:31-00:00Re: (no subject)
https://www.eclipse.org/forums/index.php/mv/msg/209408/671523/#msg_671523
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.
In my CVS perspective I see:
HEAD
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...
]]>Dwight Johnson2011-05-18T08:13:03-00:00Re: (no subject)
https://www.eclipse.org/forums/index.php/mv/msg/209408/671565/#msg_671565
- Open CVS connection via CVS perspective:
:pserver:anonymous@dev.eclipse.org:/cvsroot/webtools
- Right click on Branches, select Refresh Branches
- Select the projects you need
- click Finish
- Under Branches select (in my case) R3_2_Maintenace
- select projects, right click and select 'Check out'
Done
After deleting all the tests I had merely 13 errors left, all in XML/XSD.Should not hinder my debugging efforts.
I extracted the eclipse-sdk bundle and next merged the remaining 6 bundles into one helios install including source code. Now it seems that I have a solid installment for debugging eclipse source code without having to worry about missing plugins. It is all there.]]>Dwight Johnson2011-05-25T09:34:56-00:00