Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729) Build Identifier: I20090611-1540 I am not able to compile our program and I am stuck due to different problems. I have tested many different steps, but everything returns to the same point, i.e. some classes are not build on the Build-path. As seen from the screenshot, I am unable to run an extended version from Hello-World. When I exclude the CacheInfo, the program runs fine. From the project-settings, you could see, that there is no exclusion from the files. From the package-settings you could see, that the CacheInfo is compilable without any Errors. I conclude this file is clean of any kind of Errors. From the Navigator-view you could see, that the Folder Cache is NOT filled with classes - as well as other folders have no content. From the result-output you see, either the generic compilation error, or most of the time the problem with the class not found. Tested workaround: Eclipse 3.6M1, with no plugins and nothing, but referencing to the workspace Clean Build for the projects Changeing the Java workspace-environment from 1.6.0_16 to 1.6.0.10 stuff it into another workspace, freshly created All of them did not help. Inspecting the .metalog does not reveal any suspect issues. Since the whole Error-situation blocks severe my whole developement process, I see it as crititcal. Especially, since I have no idea, why certain files are not compiled resp. are not in the bin-folder. The whole functionallity worked until I did some refactoring of classes, i.e. renaming a package-structure which cause a move. But the refactoring was done on another place, not relating to the current problems. Reproducible: Always
Created attachment 146747 [details] 2 screenshots + metalog Screenshot show my current Error-situation.
forgotten to mention: Startup with option -clean neither helps.
Would it be possible to get a test case so that we can try to reproduce this issue?
Hm', testcase? I understand that this would simplify the whole approach for this problem. But since so many people around the world, are able to use Eclipse the way I am experiencing a problem, I see it difficult to trace it the way you suggested. I have tried to make a simple reference to the other packages with a new created java-file. This works. On the one hand, I have problems to forward the whole sources from our project, since company wouldn't allow it. On the other hand, I do NOT see the connection, between our project-files and the failure. I heavily guess, there is something wrong with the settings. Especially since it works at a collegue of mine. We did not find any kind of reason, why it fails here. So, you would have the files, and are able to compile it, but I have no idea, what are critical settings here which causes that kind of failure. Since the whole project compilable till the morning, after a SVN-update and a refactoring, I have real clue, where Eclipse crash, to not find the proper build-settings. No changes in any kind of plugins! My approach would be, to provide you any kind of Debug-logs you are looking for, to figure out, why the bin-folders are empty. What additional logs are you interested in?
'Since the whole project compilable till the morning, after a SVN-update and a refactoring, I have real clue, where Eclipse crash, to not find the proper build-settings. No changes in any kind of plugins!' should be read as: The whole project was compilable till the morning, but after a SVN-update and a refactoring the problem started. I have NO real clue, where Eclipse crash, and how to find the suspect build-settings. I did not apply any changes on plugins! Hm', seems like me English is as well broken ;)
What happens if you exit Eclipse and restart ? Maybe the PDE container got corrupted. I understand the problem for you to provide the source code, but without further details it is impossible to know what could be wrong.
Nothing. Problem persists. as mentioned, even the startup with option -clean did not help. So, what kind of details you wanna have, which are not yet mentioned I have tried?
Created attachment 146782 [details] .options file to use Try to define a .options file that you put where your eclipse.exe is located that contains the attached file contents. Then add the -debug -consolelog -console on the eclipse command line and restart. Then let us know what is inside the console log. Hopefully we can understand what is going on with this debug trace. Thanks.
Created attachment 146792 [details] Logs + Option-File
Hm', I did as requested, but I am not pretty confident that the options are the proper ones. The reason why I think so, is that the content of the log did not change anything after start-up of Eclipse nor launching the HelloWorld-App. So, I guess there are not pretty much info about the way Eclipse performs the compilation.
Created attachment 146794 [details] Enhanced Options I turned as well org.eclipse.jdt.core/debug=true Now it can found that RBA4.0 exists with the accessible folder 'cache' AND as well, there is tiny info about the HelloWorld. But conclusion, why it fails (at least not a conclusion from my side).
After playing around for another couple of hours, I fixed the issue. Main hint was to review the Problems-View, which I by default, ignore. Reviewing it, revealed that some packages were missing. Adding them due to a failure in our SVN once more, solved the problem ;) Anyway, I do not understand several issues: 1) Why does the package-view not reveal the problems (see screenshots)? i.e. indication of missing packages? Resp. Errors, which mean, that the classes cannot be compiled. 2) The Java-file itself did not reveal any problems for compilation. Therefore I assumed, everything fine. I guess this was due to broken import-chain where the last chain was broken and the top did not reveal the problem. Very strange, and I would really like to improve in that sense to mark problems, even when they are in the sub-sequence of imports.
Ok, good to know that the issue is fixed. I have no idea why the problems didn't show up in the package explorer view. If you could describe what setup we need to do to be in your situation, please do. Since you got errors in the problem views that let you fix the issue, I don't plan to invest more time in this unless I get the proper settings. Thanks.
Closing as WORKSFORME. Reopen if you can provide a setup that can let us reproduce the issue in order to improve the error reporting.
Verified for 3.6M2
