[Bug 296414] java/openjdk25: flavor headless doesn't get used

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D296414

            Bug ID: 296414
           Summary: java/openjdk25: flavor headless doesn't get used
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]
             Flags: maintainer-feedback?([email protected])
          Assignee: [email protected]

I apologize if I'm misunderstanding something here, but:

I just noticed in the 2025 fourth quarter status report -- I'm slow :) -- t=
hat
there's a new "headless" option for openjdk25. I built it, uninstalled
openjdk25@jdk along with the things that use it, and installed
openjdk25@headless. All went fine to here.

But then I tried to reinstall the first of the things that I was using the =
JDK
for (devel/nexus2-oss, though I'm not sure that it matters all that
specifically to the problem I'm posting about), and was surprised to see pkg
say that it was going to install openjdk25. Like I said, I had already
installed openjdk25@headless.

I then noticed that the names of the things produced by the two flavors are
different: "openjdk25-25.0.3+9.f.1" vs. "openjdk25-headless-25.0.3+9.f.1". =
I'm
ignorantly guessing this might have something to do with it? Like, maybe
devel/nexus2-oss is looking specifically for the former, and doesn't care a=
bout
the latter?

I hadn't noticed anything saying that something special had to be done to
actually use the new flavor, so I had just assumed it was a drop-in replace=
ment
(at least, on a headless machine). In addition to the fourth quarter status
report itself, I had also checked for that sort of thing in /usr/ports/UPDA=
TING
and in the release messages on FreshPorts.

Is there something else that needs to be done?

Thanks in advance.

--=20
You are receiving this mail because:
You are the assignee for the bug.=