Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Update Windows packaging to support Open With... on files

Open
#133 0 comments 0 reactions 0 assignees View on GitHub

@geertjanw is already working on this.

Since Oct 1, 2026.

  • #147 by @geertjanw — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java

Research direction

Start with the Windows installer packaging and the launcher changes in PR 8408, then inspect how netbeans.conf sets the relative BASEDIR and how the shortcut currently supplies --jdkhome. Test the packaged IDE and platform with Open With... on files, including bundled and system JDK cases; done means the supported launch paths work without relying on the shortcut.

Written by the indexing model from the issue text.

Description

For legacy reasons, the Windows installer with bundled JDK sets the --jdkhome location via the shortcut. This does not work when used with Open With... on a file, and is susceptible to other issues. Using the launcher directly will either use a system installed JDK or fail to launch at all.

Related issue / discussion thread (amongst others) at https://github.com/apache/netbeans/discussions/9378

With changes in the launcher in https://github.com/apache/netbeans/pull/8408 it should now be possible to specify a relative link in the netbeans.conf file using BASEDIR. This will require testing with IDE and platform. Thought should be given whether to keep the shortcut support for packaging older versions, and also whether to filter out the 32-bit launcher from the installed files.

Dominant language
Java
Stars
35
Forks
13
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/netbeans-nbpackage

All issues in apache/netbeans-nbpackage

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.