I develop a Vaadin Application with Eclipse and two things are driving me crazy:
whenever I hit CTRL+F11 (run), Eclipse opens a new Browser tab, even if I already have one (or 50) of that Application open
if I don't have the project selected in the project explorer but some class instead, Eclipse opens "http://localhost:8080/WEB-INF/classes/org/somepackage/MyClass.java" instead, which does not run the Application but gives me an error
Those two things don't make it impossible for me but because they occur so frequently they are a big annoyance for my work so I would be really glad if someone could tell me how to fix this.
Related
I'm running into an issue in Eclipse where the editor pane is not linked to the project in the Package Explorer window. For instance, if I click on a project in the package explorer and then open a Problems window that is set to Configure Contents > uncheck Show all items > set Scope to On any element in same project, it will show any applicable errors or warnings, but as soon as I open one of the class files with an error/warning in it, in the editor pane, the problems list goes blank as the editor pane does not appear to link the active tab to the active project. Simply clicking the Package Explorer window will then repopulate the problems tab until focus goes back to the editor window/tab.
This used to work with older versions of Eclipse, but ever since I updated Eclipse, it no longer does this and I don't recall which version it was that I had been using. I've also downloaded a completely clean copy of Eclipse Luna (latest version) and simply imported the old projects and still the same issue.
Is there any way to change it so the active tab in the editor points to its associated project? It's quite frustrating having to click the Package Explorer window every time I want to look at a list of problems or tasks for a specific project.
Edit: I've narrowed the issue down to minimized windows only and provided an example of the issue below.
Both windows are restricted to "Show issue on project" rather than showing all issues. Notice how the "Tasks" window works as intended while the "Problems" window does not.
Found the issue... sort of. Apparently, if you minimize the problems tab, then try to access it via the minimized icon for the tab, it loses the correct focusing to tell you what the problems are. My previous version was setup in exactly the same way and had no issues, so they must have changed something that broke this. Going to look at submitting this to the Eclipse team, as a bug.
I'm using Eclipse (Kepler) for a GWT application and for some reason, superDevMode keeps appearing in my arguments. We are stuck with GWT 2.4 which does not know what superDevMode is. I remove the argument, hit Apply and Debug to start the app, but when I look at the arguments again, -superDevMode is in there again. I am assuming there is some property that belongs to 2.6 (the version that was installed with the Eclipse plugin), but I can't seem to find it.
Update: Below, Adam recommended that I go to the GWT tab and take it out of superdevmode. Here is a screenshot of that tab:
There isn't a way to do that. The large area at the top of the tab (above the Super Dev Mode group) suggested that something was supposed to be there, so I set the project's GWT to 2.6. Sure enough, there was a Super/Classic dev mode selection. I set it to classic, saved the settings, and then put the project back to 2.4. The GWT tab looked exactly as it does above and the arguments now has "-nosuperDevMode" in it, which is also not recognized by 2.4.
Any help would be appreciated.
Thanks,
CC
I found a temporary workaround that comes with a caveat: I made the Eclipse Run Configuration file read-only.
Example path:
<YOUR_WORKSPACE>\.metadata\.plugins\org.eclipse.debug.core\.launches\<YOUR_RUN_CONFIG_NAME>.launch
Then whenever you bring up the Dev Mode Run Configuration in Eclipse it still shows the -superDevMode flag, but when you click the Close button it now asks you if you want to save and you can press No.
The big caveat: if you actually do want to change the Run Configuration Eclipse will ask if you want to save, you press Yes, the dialog closes, but it didn't actually save.
Easiest fix is to shutdown Eclipse, manually edit the .launch file to remove -superDevMode, make the file read-only, then start Eclipse again.
Here's the bug report.
Go to GWT tab (3rd from left) and switch from Super Development Mode to Classic Development Mode
I'm using soapUI eclipse plugin.
I open soapUI Navigator and create a new project. On the new project screen, I choose the location of the wsdl to generate test cases from.
After I click 'OK', the plugin starts loading the definitions. This is when it freezes.
I wasn't able to find any thing on the internet besides this 3 year old bug (which is the exact same issue I'm having, you can also see the screen shot of it): http://sourceforge.net/p/soapui/bugs/522/
Does any one know any information regarding what causes it, is there a way around, etc.
I'm inside a corporate network, can access internet fine, but there are firewall restrictions etc.
I use eclipse Soupui plugin version 4.0.1 and it works fine.
I'm using gwt-2.4.0, netbeans 7.0.1, and I have GWT4NB installed.
I create a new project using "Java Web Application" project wizard, and I add the "Google Web Toolkit" framework when asked to add frameworks. The GWT installation folder is selected, and I choose a name for GWT Module etc etc etc.
After all that, I then debug the project, and get nothing but a blank page in my browser window. When I adjust the "title" tag in the "welcomeGWT.html" file and reload the page, that takes effect, but nothing in the EntryPoint class works...
I remember having this problem before (about 2 years ago when I started a previous project), and I thought I fixed that by adjusting something in one the configuration files, but I can't seem to track it down now.
So it's a brand new project, no code added or anything, and it does "run" but the GWT stuff doesn't work. The "GWT Development Mode" window does appear, and I can click the "Launch Default Browser" button which does work, but again, only the "welcomeGWT.html" page loads. I don't see any logging tabs appear in the window either (like it does in my other GWT project).
Anybody have any ideas? I suspect it's just a configuration error... ?
Apparently gwt4nb doesn't support gwt 2.4 at this point; switching to gwt 2.0.2 which I also have installed works correctly.
I'm banging my head against the wall trying to figure this out.
I'm using NetBeans 6.9.1 and I have a project of type "Java Application." This project contains no Main method, but instead a Japplet named AlarmClock.java. When I right-click and run AlarmClock.java, it runs correctly with no problems. What I can't figure out is how to get this applet to run on a website (or even locally on my computer for that matter). I've tried building it and opening up ProjectDirectory/dist/launch.html which starts up launch.JNLP which opens up a webpage with a space for my applet, but this space just contains an error message.
I'm not sure if it's something wrong with my project settings, and I don't know what a "codebase" is or whether "Web Start" should be on. Do I need a main method that opens up my applet, and how would I do that? Some advice would be hugely appreciated.
That is a typical situation where a full IDE is too much. To understand the background is better to take a simple text editor and let you guide by a Java Applet Tutorial.
Once you feel good with applets make the same exercise with your preferred IDE. If not you have to learn Applets + "How my IDE handles Applets" at the same time.