helios

Im trying JSF2 CDI (weld) beans in eclipse helios instead of ManagedBeans , but can't do the auto completion inside the expression language for my Named beans (the #{myNamedBean. Ctrl + Space } thingy) But OTOH with ManagedBeans, the content assist works well .. Is the content assist for CDI beans supported yet in Eclipse Helios? Anybody got experiences in this ? Install JBoss tools . Then by adding <nature>org.jboss.tools.jsf.jsfnature</nature> to the natures section of the .project file, the support improved in my Eclipse J2EE Helios edition. (This step is probably equal to Configure->Add

I deleted my ./bin folder in an Eclipse Indigo (super similar to Helios), and now I am wondering how to rebuild my Java project. I just cannot find a button like we can see in Netbeans. Abhishek Singh For Eclipse you can find the rebuild option under Project > Clean and then select the project you want to clean up... that's all. This will build your project and create a new bin folder. In Eclipse there is an "Auto Build" option, which is checked by default. When it is checked, you don't need to build your project, this happens automatically. If this behaviour is unwanted, uncheck this option

Java Decompiler (JD) is generally recommended as a good, well, Java Decompiler. JD-Eclipse is the Eclipse plugin for JD. I had problems on several different machines to get the plugin running. Whenever I tried to open a .class file, the standard "Source not found" editor would show, displaying lowlevel bytecode disassembly, not the Java source output you'd expect from a decompiler. Installation docs in http://java.decompiler.free.fr/?q=jdeclipse are not bad but quite vague when it comes to troubleshooting. Opening this question to collect additional information: What problems did you encounter

Can anyone help me with this error: java was started but returned exit code = -805306369 C:\Windows\System32\javaw.exe -jar C:\Program Files\Java\eclipse-jee-helios-SR2-win32-x86_64\eclipse\plugins\org.eclipse.equinox.launcher_1.11.1.R36x_v20101122_1400.jar Just had this issue, for me it was a corrupted workspace osgi cache. The solution was to run eclipse with the -clean parameter as eclipse.exe -clean After some time, eclipse required to clean up, the workspace selection dialog popped up and I could start eclipse normally again. The -clean parameter is documented in the eclipse help My