ADDITIONAL SYSTEM INFORMATION :
osx 10.12 jdk25
A DESCRIPTION OF THE PROBLEM :
jpackager for jdk25 produces binaries that are marked to be exectable only on macos 11 and greater.
In other words, in this case, produces a binary that can't be executed on the machine that built it,
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
just do it
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
at the very least, the freshly minted app ought to default to being executable on the
machine that built it!
In general, past versions of jpackager produced apps that required at least the same level
as was used to create them. This isn't ideal either. There ought to be some support for
backward compatibility. Developers tend to have bleeding edge machines. Users not so.
osx 10.12 jdk25
A DESCRIPTION OF THE PROBLEM :
jpackager for jdk25 produces binaries that are marked to be exectable only on macos 11 and greater.
In other words, in this case, produces a binary that can't be executed on the machine that built it,
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
just do it
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
at the very least, the freshly minted app ought to default to being executable on the
machine that built it!
In general, past versions of jpackager produced apps that required at least the same level
as was used to create them. This isn't ideal either. There ought to be some support for
backward compatibility. Developers tend to have bleeding edge machines. Users not so.