I'm not exactly sure what i changed, but my project is running as an applet and not an application anymore so therefore its trash. How do i go back to application? You'd think there would be something on the internet for this..
when you right click to do "Run as ..." you should also see "Run Configurations" - click on this. On the left side you will see Applets, delete what is below this.
Related
Okay, Something strange happens now with eclipse.
Everytime I click to open the console window, eclipse closes it automatically.
Try to reset your perspective. This worked for me.
What worked for me (eventually) was to switch perspective, then open the Console, then switch back to the original perspective.
(Sort it out Eclipse)
I was using Java in Eclipse 8 and I accidentally opened this debug perspective. I want to exit this debug perspective, but I don't know how.
Thanks!
As already many authors mentioned, you can click on "java"-perspective tab. You can read more about eclipse in official user guide.
There are also a plenty of resources on web with eclipse guides/introductions/tutorials.
You see a box named java at the right top side? i.e, between quick access and debug texts. Click it! :)
You can use java button right corner to come back to regular java perspective.
In MyEclipse go to the Top-Right corner. Switch to the required mode using the following Buttons:
Open perspective
Debug perspective
Java perspective
MyEclipse Java Enterprise perspective
Right top corner! You prolly used the shortcut ;-)
Right Click the project and Open Properties.
Then Select Run/Debug Setting from there you will find all the launch Configured.
Delete all the launch and Run the application.
On the top right of your window you see that the "Debug" button is active.
To the left of it there is a button for the usual "Java" perspective. You just need to click that :)
I work on Eclipse Luna on my windows 7, the java version insatlled on the computer itself is up to date.
I build some simple JApplet to see how it runs on an html page in my computer. I mean not through
'run as applet' in eclipse, rather on a real html page.
But I can not run it due to the restriction - "Application blocked by java security". How can I see it? do I must get certificate for just simple trial?
If yes, how to do it with eclipse? Is it a short procedure? Can I see the applet runs without it?
Thanks in advance, Liron
Are you sure that you have enabled Java for your web browsers? Here are instructions for Internet Explorer:
Click Tools and then Internet Options
Select the Security tab, and select the Custom Level button
Scroll down to Scripting of Java applets
Make sure the Enable radio button is checked
Click OK to save your preference
So I am learning Google App Engine with Java. When modifying files i realized I dont always see my changes. I try clicking the red button to stop the web application in eclipse and then restarting the application however I dont see the changes. This even happens if i run chrome in incognito mode. I also have the same problem with IE and Firefox (By default i use firefox when developing due to my preference of firebug).
Also at times I will get annoyed with one project and start a new google app engine project. However the GAE will still be running the first one not the second one even though i close the project. Even worse was when i deleted the root project folder I still saw the index.html page though the links were broken for the project i deleted.
I am thinking there are two issues one is that my browser is storing these files in a cache. And the other is that I am not actually restarting the google app engine. Is the right procedure just to click the red square in the console in eclipse or is there something to run on the command line (in windows)?
To be brief , if i want to stop the GAE from in eclipse and restart it to see any changes i made whats the easiest way to do this on windows?
Thanks
edit:
Rumor has it that adding Google Web Toolkit to the project made my App Engine launch show up in the Development Mode pane, where it could be easily be killed or restarted. Is handling this issue this way a wise idea?
Trying out this touch command idea, i was hoping there was a command line way to restart the server similar to ruby on rails
the answer by dragon in this question would be helpful if it had more detail
The red button will stop it. You shouldn't need to run anything from the command line.
What you should do though is look at "Developement Mode" view and confirm nothing is running. It's under Window-->show view -->Other--> Google. Clicking on the gray arrows will show you what is open (running or not). Also, you can press the grey Xs to clear all stopped instances. This should confirm if something is running.
Also, look under run --> run configurations -->server. You have an option to set the port, or have it automatically set. If you are trying to run more than one project, your second one may not start if the first one has already taken the port. Keep that in mind.
As far as your browser storing Dev Mode page in cache, I don't think it can. In fact, if you close the running dev mode in instance your browser page should immediately update reflecting the fact that it has lost a connection. If it doesn't, surely you didn't manage to shut it down.
Ok, so I said the red button will stop it and it will, but you have to get the right red button. If you have more than one instance running, again look at the "Developement Mode" view, there is only one red button and you have to use the grey arrows I mention to get focus on the dev mode instance you want.
It's not really that complicated and you'll have it down by tommorrow!
Here is the Dev. Mode view. You can see I have three instances. The first is actually running, but shows red as there was an error. Clicking the grey grey Xs will get rid of the second two non-running instances and clicking the document icon with one grey x (it's not greyed out), will clear the log from the current running instance and remove the red x as there would then be no errors in the log.
Got it?
I feel silly asking this and even more silly to have this problem. I have a android project that has been executing fine until now.
but a couple of days ago, without me doing anything particular that I know of, my project has been always launching itself in debug no matter what I try (clicking on the debug or run gives me the same result). I try looking in the project settings and the build configuration but can't see anything justifying this.
so right now each time I launch the app I have to go to go to debug tab and click on disconnect...
Any ideas
Restart the device
I was experiencing the same problem where my app was always being run in debug mode. Restarting the device did the trick for me.
Have you checked your run configurations menu? You might have some extraneous configurations in there that Eclipse is defaulting to when you choose to launch the project.
Failing that, there is an option called "Launch in debug mode whenever the workspace contains breakpoints" in the Run/Debug -> Launching preference page. You might want to check to make sure that this option is not enabled.
As a last resort when facing these kinds of quirks I will sometimes create a new project and copy over my source files (provided the project is not very large). Closing and re-launching Eclipse sometimes works wonders for me as well.
As said above, the problem is with the device not eclipse.
Restarting the device will work, but also killing the application thread/process in the DDMS will do the same job.
On the emulator, go to App Drawer, launch application "Dev Tools". Inside there, pick "Development Settings". Make sure that the field "Debug App" has value "(none)".
Ok, I know I am a bit late with this one but I found a solution. It might be not acceptable for someone, but than again, it solved the problem.
I just reset my phone to factory settings. After that I was able to install the app without getting "waiting debugger to attach" message always.
I ran into the same problem these days, but none of the solutions above worked for me(except for factory reset, don't wanna do that for now).
As Kennifer stated, problem is with the device since this happens only on my Zync Z5 phone (I have several other devices with Android on which app start in Run mode, not Debug mode).
The only trick that worked for me was to delete the launch configuration every time wanted to run app after a debug, but it's annoying to do this every time I need a debug.
I'd tried everything on here and was surprised by the overwhelming acceptance of the top answer
Restart the device
then I realised, "this is a development phone, stop treating it like a business's server", and proceeded to restart.
Worth risking an answer to endorse this solution as a last resort.
My outcome- the app quickly, but quietly died. Result ! :(
My Eclipse version:
Luna.
My case:
The option Launch in debug mode when workspace contains breakpoints is Never, but eclipse launches in debug mode.
My Solution:
Go to Window->Preferences->Run/Debug->Launching.
Mark Prompt in option Launch in debug mode when workspace contains breakpoints.
Launch.
A dialog will popup: There are breakpoints enabled in the workspace. Would you rather launch in debug mode?
Check Remember my decision, then press No button,
and problem resolved.