If I hit another error. I’ll check to see what MODS shows as then.
> On Jun 1, 2026, at 11:48 AM, Michael Hall <[email protected]> wrote:
>
> I don’t think it should…
> MODS=`jdeps --ignore-missing-deps --module-path
> ~/Documents/javafx-sdk-24.0.1/lib --print-module-deps input/qcapp.jar`
> echo $MODS
>
> Shows
> java.base,java.compiler,java.xml,javafx.controls,javafx.fxml
>
>
>> On Jun 1, 2026, at 11:44 AM, Alexey Semenyuk <[email protected]>
>> wrote:
>>
>> Interesting. I can think of no other component of this command line, other
>> than "${MODS}", that would cause the "Found 5 non-option arguments on the
>> command line" jpackage error.
>>
>> Any chance the MODS variable contains whitespaces?
>>
>> - Alexey
>>
>> On 6/1/2026 12:15 PM, Michael Hall wrote:
>>> Hello Alexey
>>>
>>> Fairly standard to what I usually use. I build another app from time to
>>> time and haven’t run into this. I still can’t reproduce on repeated builds.
>>> But have had the couple isolated errors.
>>>
>>> ${PACKAGER} \
>>> --verbose \
>>> --input input \
>>> --type "app-image" \
>>> --name QuantumJava \
>>> --main-jar qcapp.jar \
>>> --main-class us.hall.qcapp.QuantumJava \
>>> --java-options -Dapple.awt.application.name=QuantumJava \
>>> --mac-package-identifier "us.hall.quantumjava" \
>>> --mac-sign \
>>> --mac-signing-key-user-name "$SIGNING_CERT" \
>>> --module-path ~/Documents/javafx-jmods-24.0.1 \
>>> --add-modules ${MODS},jdk.compiler,java.logging \
>>> --jlink-options '--strip-debug --no-man-pages --no-header-files'
>>>
>>>> On Jun 1, 2026, at 11:08 AM, Alexey Semenyuk <[email protected]>
>>>> wrote:
>>>>
>>>> Hi Michael,
>>>>
>>>> Can you share the command line triggering jpackage failure?
>>>>
>>>> - Alexey
>>>>
>>
>
