apache / apache/netbeans

Component Border From Form Designed code had null

Open
#8,337 3 comments 0 reactions 0 assignees View on GitHub
FormDesigner kind:bug needs:triage
Dominant language
Java
Stars
3.1k
Forks
935
Avg merge
2d 3h
Merged PRs (30d)
17

Description

### Apache NetBeans version

Apache NetBeans 25

### What happened

I encountered an issue with Netbeans 25.
I installed AlamLinux 9 in a VM.
Then I installed openjdk 21 (latest as of 3/13/2025)
Then I install Netbeans 25 from the 'noarch' rpm.
I started Netbeans and made a new gradle project.
Then I made a JFrame form.
Then I added a panel. Tried to set the panel boarder but there were no options in the dropdown menu of the GUI designer.
The code it had generated would not compile.

So then I closed netbeans.
I downgraded to openjdk 17.
Restarted netbeans, and now the GUI designer would work, A raised bevel border could be created, and the code
would compile.

So now I've gone back to openjdk 21, and it also still seems to work. So this is good.
But I'm not sure why the original run would have failed, or if the issue is with first creating a java project,
or having first run with openjdk 21 versus 17.

### Language / Project Type / NetBeans Component

Java JFrame Form Border

### How to reproduce

Hopefully the above steps reproduce the issue for you.

### Did this work correctly in an earlier version?

No / Don't know

### Operating System

AlmaLinux 9

### JDK

openjdk 21

### Apache NetBeans packaging

Other, Apache NetBeans provided installer

### Anything else

Seemed to just be on the first run.

### Are you willing to submit a pull request?

No

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported JFrame form workflow on AlmaLinux 9 with OpenJDK 21, creating a Gradle project, panel, and border through the GUI designer. Compare the first-run behavior with OpenJDK 17 and inspect the generated form code and compiler failure; done means the cause is identified and the border options and generated code behave consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.