Empty project groups after Netbeans update - netbeans

I recently upgraded from Netbeans 7.3.1 to 7.4 and all my project groups contain no projects in the newer version. I have not moved my projects at all and I chose to import all my settings from the previous Netbeans installation when prompted.
Anyone else having this problem?

Never mind my mistake, I downloaded the Netbeans + JDK from the Oracle website and forgot it doesn't come with PHP support. Please close this question.

Related

Auto save plugin for netbeans 8.2

Is there plugin for auto save feature in netbeans 8.2? I find it from IDE's plugins list but can't find it.
For netbeans 8.1 was a plugin in IDE's plugins list. It was not tested/verified for netbeans 8.2.
I download it(http://plugins.netbeans.org/plugin/63714/autosavemodified) manually and install it by IDE's plugin`s download section. It works well for me in Ubuntu 16.04!
Since you have not quite clarified your question, I assume you're referring to this Netbeans plug-in.
If so, this plugin is not marked as compatible with Netbeans 8.2, that's why you can't find it in the plug-ins list in Netbeans itself.
From my experience, it is possible to manually download and install it in Netbeans 8.1 (even if marked as compatible only with Netbeans 8.0 and lower), but it does not seem to work anymore with Netbeans 8.2 at all and it will work with Netbeans 8.2 also.
Edit:
It was not showing as installed at first, and I could not get it to install when I tried, probably because it was already installed when I imported the 8.1 profile in 8.2 (some non-descript error popped up), but after a while I found it to be working. Not sure what exactly happened... a machine reboot, Java update, another thing?
Anyway, I just wanted to confirm that it seems to work with Netbeans 8.2 without any issues.

FindBugs Does Not Show Up in Project Properties

I had just installed FindBugs plugin for Eclipse. My Eclipse is Juno. I am using Windows 7.
It shows up at Help -> about Eclipse -> Installed Software as FindBugs Feature
However it does not exist on Project Properties.
I had tried to run eclipse as Administrator, installing from either marketplace or manual.
But no luck.
I use a copied Eclipse (without installation) at Desktop.
Any thought on how to shows the FindBugs in project properties?
Thanks
Just in case you haven't figured out yet, and so it might help others like me.
If you are installing a version of Eclipse FindBugs 3.0 or greater, then it's only supported on Java 7.
Update your JDK to 7.0 and you will see Findbugs show up as a part of your properties. Wasted a lot of hours on this one.
I had same problem. I am using Kepler + windows 7 + jdk1.5. This got resolved with jdk update from 1.5 to 1.7.
May be it has dependency on 1.7 but there was no error message and like you said it was not visible in preference.
Check out this tutorial:
http://www.vogella.com/tutorials/Findbugs/article.html
I am using Eclipse Kepler in Windows 7, but it shouldn't make any difference.
There is also a FindBugs entry in context menu (right click project, under Import and Export options, in my case)
Edit your eclipse.ini file (you can find it in your eclipse installation folder) and change or add (if it does not exist) the -vm parameter value to a Java 7 JDK. More info here.
All other answers (installing latest Java, Eclipse update, adding '-vm ...' to the .ini-file did not work for me.
I solved it by clicking "Window"->"Perspective"->"Open Perspective"->"Other..."->"FindBugs".
Then switch back to 'Java'-perspective. Now the menu is available when you right-click the project.

IBM Worklight plugin on Eclipse Juno disppeared

I downloaded eclipse-jee-juno-SR2-win32 and installed IBM Worklight as a plugin. It worked well for almost 2 months (don't remember exactly how many days). But it disappeared all of a sudden. Now I don't see any work light related options in eclipse. Any idea what could be reason ? & How to install it again ?
Thanks..Johnson
It's strange indeed, but easiest solution would be to extract a fresh copy of Eclipse, install Worklight into it and import your existing Worklight project from the workspace of the previous Eclipse installation.

glassfish v2 in Netbeans 7.2

I've updated Netbeans 6.9 to Netbeans 7.2. But after that I cannot use glassfish v2 with new Netbeans. The problem is glassfish server v2 is not supported to Netbeans 7.2
The proposed solution of this problem is to add a plugin
http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/lastStableBuild/artifact/nbbuild/nbms/updates.xml
But it doesn't work for me. I tried it today but it didn't find any such plugin! I guess, it is removed from the repository.
Please anyone give me a suggestion how to resolve the problem now. I am stuck for the whole day.
Try to manually install the Netbeans plugin from here:
http://dlc.sun.com.edgesuite.net/netbeans/updates/6.9/uc/m1/dev/modules/enterprise/org-netbeans-modules-j2ee-sun-appsrv81.nbm
Download that file locally and then from NB:
Tools-Plugins-Downloaded - Add Plugins
That fixed it for my NB 7.3.1.

What is the best way to upgrade Eclipse 3.6 to 3.7 (or a subsequent version)?

In the past I've always downloaded the new version, and then manually reinstalled all of the plugins I use - but this is tedious in the extreme.
Is there a way to upgrade Eclipse "in-place"? How do I do this exactly?
The approach below worked for me, and seems to be the easiest. It's from this eclipse FAQ and slightly modified for clarity:
For upgrading from Eclipse 3.5+ to 3.6+
Help -> Install New Software
Enter the release update site url eg. 'http://download.eclipse.org/releases/indigo' <- if upgrading from 3.5 or 3.6 (Helios) to 3.7 (Indigo)
Click Add
Click Cancel
Help -> Check for Updates
Note: The original URL has changed. (I've left the original link for posterity)
following the NEW FAQ instructions
Also you may have to remove any incompatible updates plugins before proceeding.
(For Example: JBoss Tools has different versions for Helios and Indigo that are incompatible)
Update: I didn't try this when upgrading from 3.x to 4.x (Juno). I just set up a whole new workspace. I think I read somewhere that doing that is the safest approach to upgrading major versions.
As of 3.7 (Indigo), you may export/import install configurations via the
File > Import/Export > Install menu.
This allows you to install a new release of Eclipse, point it at your
existing workspace, and install your plugins from an older installed
copy.
If you always download all plugins manually and then deploy it by copying to dropins folder, then while migrating to newer version, just need to copy that folder to the new eclipse.
And even not all plugins will support newer version of Eclipse so I guess there is no really easy way available to do the migration.
The answer is, there is none. It's pointless to speculate here as to why the Eclipse community chooses not to make one. They haven't.