I have GNATbench installed in my Eclipse (Indigo) for coding in Ada; and for some odd reason, the program is first run and then compiled, which doesn't quite work when I update the code. I know the compiler works, because if I run the program manually it works fine; and if I hit run again, it runs with the proper changes made. A side note: I prefer using eclipse, and I'd rather not just compile from the command line. I am running Indigo on Ubuntu 11.4.
You should disable "Build Automatically" in the Project menu and then build manually before running. This can be done using the Ctrl+B shortcut.
odd. is it actually running? Gnatbench does a syntax/file check everytime it saves. I'd make sure your gpr file is correct and that your project isn't nested within another eclipse project or else eclipse can act kinda weird.
Related
The system is Linux. I have a C++ prjoject opened with eclipse. In another window I have a terminal in the folder where the binary is created. Normally I edit the project, I build it and i execute the binary from the terminal and it works. However sometimes it seems that the build doesn't update the binary. Anyone knows how to fix this behavior?
Note: I don't want to do a Clean manually all the times because isn't comfortable, expecially because I my touchpad's right click that doesn't work very well under Linux. However it would be ok if the clean was done automatically.
Thanks
Do you have the save automatically before build setting set?
If you do not save your project before the build eclipse will not create a new binary.
I'm a Visual Studio .NET developer who's trying to switch to Eclipse/SpringSource Tool Suite, so I get stuck on probably simple problems. Please bear with me.
I'm working on a Spring MVC project associated with an Apache Tomcat server. If I right-click the server and choose Start (alternatively Package Explorer->right-click project->Run As->Run on Server), my project is compiled and started. Compiler output is shown in Console window. Fine.
But if I simply want to compile the project without running it, I try selecting Project->Build All, Project->Build Project, or Project->Build Working Set. Nothing happens, no screen output, nothing -- despite having non-compiling code.
I expected to see the compiler errors on screen, preferably with the errors highlighted in the code. For what it's worth, I have deselected Project->Build Automatically. Anybody knows what I should do?
Eclipse and STS use incremental compilation. So, every time a file is saved, it is automatically compiled (as well as all files dependent on it). When you deselect Build Automatically, then yes, you will need to explicitly build, but this will still be an incremental build (ie- only the changed files and dependencies).
See here for a bit of a discussion on how incremental building works in Eclipse: http://www.eclipse.org/articles/Article-Builders/builders.html
I am writing some scripts in Eclipse 2.7 RC4, using the latest Groovy Eclipse plugin.
Everything works fine except that I have a Run Configuration that I created that passes 2 arguments to the script but every time I click the Play button to run the project, Eclipse creates a new Groovy Script Run Configuration called "Server (1)". If I click the Play button again, Eclipse creates another Run Configuration called "Server (2)", etc.
So, every single time I want to run my project, I have to go in and delete the last run configuration it made.
Why does Eclipse do this? Can't I lock the configuration so that it wont change?
I realize this question is quite old but it's still an issue that happens (as it was happening to me today) I played around with it a little and found that in the 'Run Configurations' window where you can set Arguments/Classpath variables etc there is also a tab named Common. I found that within this there is an option called "Save as" and if the 'Shared File:' option is selected (pointing to the exported launch configuration) it will keep creating new Run Configs every time you run it. If you instead select the Local File option and Apply the changes, I believe you will stop seeing new run configs saved each time. This worked for me, at least!
This is probably a bug in Groovy-Eclipse in that it is not recognizing that an existing launch configuration is the "same" as a new one.
Can you get around this by simply re-using the old on explicitly, ie- by clicking on the little arrow to the right of the run button and choosing the old configuration:
I am seeing the same thing for Java and Scala test programs I created in Juno version of Eclipse (latest as of Nov 2012). Very irritating to have to delete all those run configurations explicitly.
I've just installed Eclipse and PyDev (again - I've been without it for some time) and everything works like a charm, except one little annoyance:
Every time I start Eclipse, I have to go to Window->Preferences... and configure a Python Interpreter. It's not hard to do (pressing "Auto Configure" works) but for some reason Eclipse seems to forget that I set that setting before, and has me do it every time I start the program.
Is there any way to force Eclipse to remember, or to automatically configure the interpreter on startup? Since AutoConfigure works, Eclipse can apparently do the work on its own - it just doesn't...
Perhaps your Eclipse settings directory is not fully writable? Check and see if everything is writable by your user.
And if that doesn't work, you can try starting it with eclipse -clean.
And if that didn't help either, you can try removing your profile completely.
I'm working on a blackberry project using eclipse and bb-ant tools. I've created a build.xml file to perform the build. Everytime I try to run an Ant build, eclipse pops up the progress dialog and it hangs stating "Waiting for virtual machine to exit."
I downloaded an open source Blackberry project that has an ant build and it is showing the same behavior.
Does anyone have any suggestions?
Edit:
I used the command line to build my xml file and it built fine. However, when I tried from Eclipse it still hangs.
I've tried both the standard eclipse plugin directory and the path I downloaded ant to.
You could check if your ANT_HOME settings are correct (see also this blog post).
"Window > Preference > Ant > Runtime": "Ant Home Entries".
if the jars files are from a plugin directory (beside the default 'org.apache.ant_1.7.1.v20090120-1145' one) and not an independent ant installation, that might explain the problem.
Try clicking the "Ant Home" button on the right side and setting up ant home such as "C:\path\to\apache-ant-1.7.0"
There are similar bugs to this kind of situation (bug 173419, ticket 91).
It is worth checking the JVM used for the project.
It can also occurs when a ant task is poorly implemented.
You had the problem because the java version ant tries to run with is incorrect.
By default, eclipse will try to run the ant build with the java version it uses to compile the java files (Blackberry JRE), which won't work! You need to change the jre version by choosing "Run As... > Ant build". Before clicking run, go to the JRE tab, choose "Separate JRE:" and change "Blackberry JRE " to a standard java JRE. Press the run button and everything should work correctly.
I hit this problem also. Although I never used the same solution, you pointed me in the same direction.
I was using a ant file as a builder in my project, and I disabled the Allocate Console build option. This is when I hit the 'Waiting for virtual machine to exit'.
So I simply enabled the Launch in background option and it worked.