Skip to content

option to only package matching start script #103

@Vampire

Description

@Vampire

If you build a windows and a linux package, you currently have the quirk, that both packages contain both start scripts.
This is somewhat strange for the end user, because usually he can only use one with the packaged runtime.
It would be nice if the plugin had some built-in way so that only the matching script is packaged.
Currently I do it with

tasks.runtime {
    doLast {
        delete {
            delete(
                runtime.imageDir.get()
                    .dir("${project.name}-windows")
                    .file(tasks.startScripts.get().unixScript.name),
                runtime.imageDir.get()
                    .dir("${project.name}-linux")
                    .file(tasks.startScripts.get().windowsScript.name)
            )
        }
    }
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions