| Keep jdt from interpreting .java file contents [message #253694] |
Mon, 02 June 2008 14:49  |
Eclipse User |
|
|
|
Hi,
some time ago I asked on the newcomers list and thought i have solved my
problem. Now I switched to RC3 and the problem reappears:
Inside a Java project, I generate java code that contains bgga closures
- in other words it is full of errors for the standard compiler.
I want to open the generated files, without error markers being added.
I thought that disabling all the project builders would keep eclipse
completely from interpreting the files contents. But I am not familiar
with how the jdt builder and the editor are related..
However, I still get error markers when opening the file with the Java
editor. Even when I open the file with the "text editor" the markers
persist.
Is there anything I can do against? I need to demo the code, and those
errors would be really disturbing...
Thanks for help.
Felix
|
|
|
|
|
| Re: Keep jdt from interpreting .java file contents [message #253873 is a reply to message #253703] |
Thu, 12 June 2008 06:38  |
| Eclipse User |
|
|
|
Felix Dorner wrote:
> Ed Merks wrote:
>> Felix,
>>
>> Is the .java file in a folder that's considered a source folder on the
>> build path?
>
> Yes unfortunately. Otherwise I ran into troubles with the Jet
> transformation that generates those files.
>
> It turns out that the markers from the text editor were only "cached" or
> so, these disappeared now.
>
> Felix
You could try excluding them from compilation, by going to build path
properties, and using exclude/include rules on your source entry.
|
|
|
Powered by
FUDForum. Page generated in 0.03786 seconds
Home