Moving Netbeans app after first launch causes errors in IDE
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 935
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Description
### Apache NetBeans version
Apache NetBeans 24
### What happened
Running on macOS:
If the Netbeans application bundle is moved to a new directory after it has already been launched at least once then the IDE will start reporting errors in the notifications window.
The log file shows that netbeans is attempting to load files from the prior directory location.
### Language / Project Type / NetBeans Component
_No response_
### How to reproduce
1) Install netbeans
2) Launch netbeans
3) Close netbeans
4) Move netbeans application bundle to another directory
5) Launch netbeans
Netbeans will launch at step 5. However it will report that it has detected an error. The log files show that it cannot find netbean jar files located in the original install location.
### Did this work correctly in an earlier version?
No / Don't know
### Operating System
macOS 15.2 (24C101)
### JDK
openjdk version "22.0.2"
### Apache NetBeans packaging
Apache NetBeans provided installer
### Anything else
The issue seems to be cached configuration information that continues to point to the old install location found in the file:
{$USER}/Library/Application Support/NetBeans/24/build.properties
If the folder containing the build.properties file is removed (eg .../24) then netbeans no longer reports any errors after it is re-launched and rebuilds the cache.
### Are you willing to submit a pull request?
No
Contributor guide
Research direction
Start by reproducing the macOS launch and relocation sequence, then inspect ~/Library/Application Support/NetBeans/24/build.properties, which the report identifies as retaining the old installation path. Done means moving the application bundle and relaunching it no longer produces missing-JAR errors or notifications about the previous location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, macos
- Domain
- desktop-dev, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100