How to make ant console always visible in eclipse? - eclipse

When I have to see ant console every time I do "widow -> show view -> ant". And when the eclipse is restarted the ant console is hidden I need to do the same process again to see the ant window, is there any way that ant console is always open by default ?

When you have the ant console showing you can save your perspective so you will see it every time eclipse is started. http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2FgettingStarted%2Fqs-43e.htm

Related

Ant buid clears eclipse console - how to stop?

whenever I do an ant build, my console results (Errors, warnings etc.) are deleted and it always Shows
"BUILD SUCCESSFUL
Total time: xxx milliseconds"
how can I prevent the ant file from overwriting my actual console Output?
thank you!
you can try this:
open "External Tools Configuration" (in my eclipse-ui its next to the green run button in the menu bar) -> open your ant runconfig -> go to "common" -> disable "Allocate console (necessary for input)"
this should prevent the overwriting of the console.
in my eclipse version (eclipse mars rc2) it leads to the situation that the current console is closed, but no ant console opens....i think this behaviour is not intended (maybe an eclipse bug). so its the half way to a solution: no ant output but still a deleted console output.
Maybe it works for your eclipse version
greetings

Is it possible to set which file to run by default in eclipse?

I'm writing a python project in Eclipse with the PyDev plug-in, which contains multiple files.
However I'm used to using visual studio, where it'll automatically find the main function of a project and run the program from there.
Eclipse will always run the file I am currently editing (which usually is a file containing function that are called from the main function).
Is it possible to set which file should be run then clicking run? I've looked at the launch options under Project->Properties->PyDev, but didn't find what I was looking for.
When you press the Debug or Run button (Debug on the left) Eclipse tries to intelligently determine what to launch based on your current editor.
You can change the behaviour by editing Window -> Preferences -> Run/Debug -> Launching -> Launch Operation as pictured below.
The default of launching the current editor works well for some languages, but not as well for Python when every single file is itself a valid program to run. In your case I recommend changing to Always launch the previously launched application.
You can create a custom run configuration.
Right click on your project > run as > run configurations
From here is just a matter of choosing your project type on the left hand side and filling in the required information. You can click 'Run' to use your new configuration.
To get to this configuration again, you can click the 'Run' drop down button in the eclipse tool bar and see all of your run configurations.
Hope this helps!

Launching Eclipse debug mode from terminal, Pydev

Let say I have a working Eclipse project . The debug configuration is set up correctly such that I can launch Eclipse and start debug mode with a few clicks. No other run time input is needed and a breakpoint is already added to the beginning of the program.
Instead of clicking, I want to know if there is a way that I can do this from a terminal. Basically I want to script the command. I've found the options to disable splashdown and select the workspace. The Eclipse version is Luna. Thanks.
Check the properties of the process that's in the Debug view when you start it from there. Also: http://help.eclipse.org/luna/topic/org.eclipse.platform.doc.user/tasks/running_eclipse.htm

Popup window blocks test in Eclipse

I'm running the pde test in ant build with parameter:
-application org.eclipse.pde.junit.runtime.uitestapplication.
When the eclipse instance is started while running the test, it pops up a dialog window (named "Usage Data Upload") which blocks the test run until I manually close it.
Any suggestions on how to fix this?
Exclude bundles com.instantiations.eclipse.usageprofiler and com.instantiations.eclipse.usageprofiler.ui from your product.

Eclipse "Waiting for virtual machine to exit"

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.