#420: Create Windows Installer with WixToolset

[alfeilex]

Fixes: #420

This PR implements the creation of a MSI file for Windows Installer with WixToolset

It includes:

• The Windows Installer Build Package with UI Sequence:
  • Accept License
  • Continue with default installation (default C:\projects) or customize
    • Volume Drive
    • Root Folder or User Home Folder
  • Copy files into installation folder and run ideasy.exe -f install
• The integration of the WixToolSet build logic into the Nightly Build and Release workflow

[coveralls]

Pull Request Test Coverage Report for Build 13548740329

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 68.227%

---

Totals
Change from base Build 13547736881:	0.0%
Covered Lines:	7860
Relevant Lines:	11071

---

💛 - Coveralls

[alfeilex]

We should also define the correct meta information for the MSI packages

[alfeilex]

One thing is that on the windows build (in matrix os), we need to build the MSI.
Further in maven (see here), we need to attach the artifact to the release being deployed. This does not make sense via assembly-plugin since we already have the artifact that is the MSI itself. Instead use attach-artifact.

But as I understand it, in the current workflow, we build the native image and include it in the deployment for the release. In the MSI build itself, we also need the whole package, including the binary ideasy.exe and also documentation, which is not built before mvn deploy.

[alfeilex]

@alfeilex now that my PR #1055 is merged, your MSI installer only needs to call ideasy.exe -f install:

IDEasy/cli/src/main/package/setup

Line 3 in 4caff46

./bin/ideasy -f install

Is added but has to be tested when #1084 is merged.

[alfeilex]

I removed the pattern key here, because we use all uploaded artifacts anyway. Since we also include the msi artifact, we would have to check how to extend the pattern here in the case, we want to stick with it.

[alfeilex]

I tried to integrate the whole MSI installation into maven, but the plugins are not compatbile with the latest version 5. https://wix-maven.github.io/wix-maven-plugin/

So I chose this place to insert the Wixtoolset installation. I would also be possible to move this to the last deploy job, but there we are using ubuntu as a runner and dotnet would not work properly.

I think we could also move the whole thing into a separate Github Action. But maybe, we could create a new issue for that.

If you have any suggestions, than please comment on this

[alfeilex]

It looks like the MSI is attached into the deployment. I haven't change the release workflow yet. Maybe we can first run the Nightly Build and then adapt the changes to the release workflow

https://github.com/alfeilex/IDEasy/actions/runs/13546792586/job/37860853837#step:5:1240

[alfeilex]

Right now, its named ide-cli-2025.02.002-beta.msi

If you change the name or the artifact-id, then you have also to change line 279 because I rename the downloaded ideasy.msi there