Skip to content

WinRun4j executables do not respect program arguments in app.l4j.ini #173

@keastrid

Description

@keastrid

I'm submitting a…

  • bug report
  • feature request
  • other

Short description of the issue/suggestion:
When using winrun4j to build the exe, it does not respect the launch argument contents of app.l4j.ini.

Steps to reproduce the issue/enhancement:

  1. Build using winrun
  2. Setup app.l4j.ini
  3. Attempt to change the available memory of the application

What is the expected behavior?
For it to respect program arguments set there

What is the current behavior?
It ignores them

Do you have outputs, screenshots, demos or samples which demonstrate the problem or enhancement?

What is the motivation / use case for changing the behavior?
Unified config across all platforms and launchers

Please tell us about your environment:

  • JavaPackager version: 1.6.5
  • OS version: Win10
  • JDK version: 17
  • Build tool:
    • Maven
    • Gradle

Other information (e.g. related issues, suggestions how to fix, links for us to have context)

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingenhancementNew feature or requestfixedIssue fixed and release pending

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions