Skip to content

Refactor the Windows installer to allow for branding and customisations #1033

@tellison

Description

@tellison

The Windows installers code should allow for full branding and customisation by third-parties so that the code can be reused in other circumstances. By default, the installers will be branded for installing Adoptium Temurin and coded to install the binaries produced by the project; however, there is value in reusing common behavior and logic across participants who are installing Temurin as a different branded binary, or even a different custom build.

The customisation code should not be stored in the Adoptium repository for users other than Temurin. At the moment there are customisations that require developers to update the Adoptium installer repository for their own use - this should not be necessary.

This issue is to capture requirements for the refactoring of the existing code to permit current external requirements, and ensure that those currently using the code can include their requirements, and track any changes undertaken.

(Raising on behalf of @karianna . Please amend or update as required.)

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