I installed Apache Netbeans a couple weeks ago, decided I didn't like it, and am attempting to uninstall it. However, it is not showing up in my Add/Remove Programs on Windows 10, nor can I find an Uninstall exe file in the files of NetBeans. Any help or advice would be appreciated.
You must have installed Apache NetBeans 11.0 by downloading a zip file named incubating-netbeans-11.0-bin.zip, then unzipping it to an installation directory, because that is the only approach that is offered. From the Apache NetBeans web site:
Apache NetBeans 11.0 is available for download from your closest
Apache mirror. For this release no official installers are provided,
please just download the binaries and unzip them.
This explains why you cannot uninstall NetBeans 11.0 from the Control Panel in Windows 10: you did not install it using an installer, you just unzipped a file.
So to uninstall NetBeans 11.0 on Windows 10 all you need to do is this:
Close NetBeans.
Delete the NetBeans installation directory.
Delete the downloaded zip file (if you had kept it).
However, there are a couple of additional optional steps that will free up (a lot of) disk space, and are definitely worth doing:
Before removing/uninstalling NetBeans, open it one last time.
Open the Help > About screen. You will see a couple of entries named User directory and Cache directory. They contain (a lot of) files related to the configuration of NetBeans, and they can and should be deleted as well:
Note the names of those two directories, and then close NetBeans.
Delete those two directories, and then delete the NetBeans installation directory and the downloaded zip file (if necessary).
Related
I have Eclipse installed on a removable drive that I take between my desktop and laptop. I have an old installation (Mars) that I installed ages ago by unzipping files. I have a newer installation (Neon) that I installed using the new Eclipse installer.
After upgrading both my computers to Windows 10 Anniversary Edition, both Eclipse installations continue to work when the drive is connected to the desktop machine. When I connect the drive to the laptop, however, the new Eclipse installation (Neon---the one installed using the installer) will not start and says:
The Eclipse executable launcher was unable to locate its companion shared library.
However the old installation (Mars---the one installed from unzipping an archive) still runs just fine.
What is the problem with the Neon installation on the laptop and how do I fix it?
Update: I looked in the eclipse.ini file, and there is a --launcher.library reference to a C:/Users/user/.p2/pool/plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.400.v20160518-1444. The laptop (which is failing) has only org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417. But the desktop (where it is working) has both org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.300.v20150602-1417 and org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.400.v20160518-1444.
So maybe somehow Eclipse updated its Equinox Launcher when the drive was attached to the desktop. Then when I attached the drive to the laptop, it referenced the updated launcher plugin, but the laptop didn't have the updated launcher.
This is a fine kettle of fish. I had no idea Eclipse was installing things in the user directory, outside the Eclipse installation directory. I guess that's one of the drawbacks of this newfangled launcher: it's not possible to use Eclipse on a shared drive.
How can I get Eclipse to install the launcher on the shared drive rather than in the system user home directory? Can I avoid this altogether if I install directly from zip files? How did Eclipse update this launcher in the first place without my knowing about it?
Update: Now I see that Eclipse also installed a org.eclipse.equinox.launcher_1.3.200.v20160318-1642.jar in the local plugins directory (that is, relative to the executable on the drive). Why is Eclipse putting some things on the removable drive relative to the executable (as they should be), and other things in the system user directory (where I don't want them)? This is a mess. So much for having a self-contained Eclipse installation like I did for over a decade.
By default, Eclipse installer does use a shared "bundle pool" so that if you have multiple different Eclipse instances running, the various plugins they're using are only downloaded once. This usually saves network bandwidth and disk space.
However, this bundle pool may probably be unable to work properly if the installation and bundle pool are on different drive (Especially if one of them is shared by multiple machines). You can report this limitation to http://bugs.eclipse.org .
As a workaround, for such custom installations, I would recommend that you skip the Eclipse installer, and get good old packages that will work just like Mars, everything in their own directory: https://www.eclipse.org/downloads/eclipse-packages/
I am using Install4j 6.1.1 to create a new installer that must be smart enough to support 3 installation scenarios:
Create a new installation
Upgrade an existing installation
Upgrade an existing installation that was created using an InstallAnywhere installer
Scenarios 1 and 2 function correctly. With scenario 3 there is a problem with installing a new jre.
If my installer finds an old non-Install4j instance, it invokes the previous version's uninstaller before proceeding with a new install. This seems to work just fine. However, the new bundled JRE is not being installed properly. The Install Files action copies the JRE to the install folder, and then the deletes the bin folder. This results in a corrupted installation that will not execute. I can see this happen- if I open the JRE subfolder during install I can see the jre's lib and bin folders get created and then watch the bin folder get deleted. The jre\lib folder remains. There does not seem to be anything in the installation log to explain what's happening.
Any idea what would cause a bundled JRE to partially install?
I am using eclipse 3.8.1 right now on Xubuntu and there were no problems until now. But 2 days ago some friends and me started a project together, they are using Windows 7 and Windows 8 (x64). When I installed eclipse in Xubuntu, it didnt have any plugins and features installed but I couldnt find any eclipse version for windows that has no plugins pre-installed.
Does anyone know how to do that?
Thanks a lot for every idea! :)
I know I'm three years late but: you can download it from here: http://download.eclipse.org/eclipse/downloads/index.html. There you can find 'clean' builds of Eclipse, which do not ship with common development tools.
If you do an apt-get install eclipse, it gets installed in a read-only directory; each user that runs Eclipse gets their own directory with the plugins he/she installs afterwards from within Eclipse.
On both Windows and Linux, you can just download a zip file of Eclipse, unzip it somewhere, and then run it directly. This is also the way to run different versions of Eclipse, and there is just one place for each version to store plugins: within its own directory.
I am currently trying to make an Eclipse istallation with installed plugins portable, so that you only have to copy the whole "eclipse"-folder to another system and have the same setup as on the original system.
My problem now is, that since eclipse 4.2 (?) when using Help > Install new Software... plugins are installed externally into the folder
C:/Users/Username/.eclipse/org.eclipse.platform_4.2.0_identifier
and not into the folder where the "eclipse.exe" is located:
C:/Program Files (x86)/eclipse
Now my question is if it is possible to make eclipse install additional plugins into the plugins/features-folder of eclipse's home folder (C:/Program Files (x86)/eclipse).
Unfortunately, it isn't possible to use the dropins-folder, because one plugin that shall be installed only exists as an update site.
I'm using
Windows 7 Professional Service Pack 1 64bit
with
Eclipse IDE for C/C++ Developers
Version: Juno Service Release 2
32-bit (to provide portability).
Greets :)
Do not put your eclipse installation under the "Program Files" folder. Eclipse will install all plugins to its own folder by default, unless that folder is not writable from Eclipse. And the "Program Files" folder should not be writable by you (unless you are using administrative access rights). Only the trusted installer service account should modify that folder (following Windows guidelines).
Therefore unzip Eclipse somewhere else into a location where anyone is allowed to write, install your plugins and zip the whole folder again.
As an alternative to that ZIP package you may want to look at File -> Export -> Install -> Software items to file, where you can export (and re-import) a list of your already installed plugins.
What mack is trying to do should work, this is essentially what the eclipse foundation do to provide the various distros.
The plugin that is only available as an update site could be installed into and existing in-installation then copied to the new distro. Only trick is making sure you have all the feature and plugin jar files.
I recently installed Netbeans 7.2 beta and it worked fine. Then I installed Netbeans 7.2 final release on top of beta and during the installation, Netbeans 7.1 and Netbeans 7.12 were there. Now when I launch Netbeans, it does not go beyond "loading modules" stage. Simply the Netbeans screen disappear few seconds after the launch. Then I did the following.
Uninstalled all the Netbeans versions and re-installed Netbeans 7.2
Deleted AppData/Netbeans folder
Deleted User/.nbi folder
Searched the registry and deleted Netbeans related entries. (But only one entry was found)
Deleted Netbeans Folder in Program Files folder.
Uninstalled and Re-installed in a separate drive.
Uninstalled and Re-installed under another user account.
None of the above worked, the only thing I did not try was to re-install the Windows XP operating system.
It there any option to try before re-installing the operating system?
I was having the same problem .... with netbeans 7.2 ,go to user/appdata/roaming/7.2/modules/ and delete all the jar files except docs,ext,locale folders ... and start the ide again... basically the problem betides when u update the ide after update when u start the ide it stuck to the loading module phase.
First of all, you need to check proper version of JDK is installed.
Netbeans 7.2 requires JDK 1.7, not 1.8.
You can check {Netbeans Install Path}/etc/netbeans.conf. There find netbeans_jdkhome and its value. Make sure you install JDK1.7 and this line netbeans_jdkhome="C:\Program Files\Java\jdk1.7.0_25" for example.
If not, change the value to proper installation path.
That's some stability issue with NetBeans 7.2
Just Kill and Restart the IDE and it should be fine.
Make sure that right JDK directory chosen in the installation wizard if you not sure you can change it from
C:\Program Files\NetBeans {netbeans version}\etc
you will see a file which is
netbeans.conf
edit it(I am using Notepad++ for that)
At the bottom of the file, you will see a line
netbeans_jdkhome="C:\Program Files\Java\{jdk directory you want}"
make sure it is valid JDK and it is JDK, not JRE
I had the same problem, make sure you have the required JDK version configured during the installation process.
First tried everything to no avail, finally I had to uninstall NetBeans 7, then install NetBeans 8, which also aligned with my JDK 8. This resolved the issue for me. Hope this helps others.
Ah, finally this worked with me on version 11.3, delete this folder, then run the program again
C:\Users\Dell\AppData\Roaming\NetBeans
here my main username is Dell, yours can be different ofcourse
I found out in my Windows installation of Apache Netbeans 12.4, the file 'tctracker.properties' in 'C:\Users\user\AppData\Roaming\NetBeans\12.4\config\Preferences\org\netbeans\core\windows' was filled with null values. I fixed the issue with letting netbeans generate a new file by moving this '12.4' directory to somewhere else on the disk, starting Netbeans, letting it generate a new 'tctracker.properties'-file, stop it, replace the corrupt file in with this newly generated file and put the '12.4' directory back in place.