New package: Flakron.ApacheMaven version 3.8.9

[flakron]

The installer for the package, is built in this repo: https://github.com/flakron/winget-apache-maven

Checklist for Pull Requests

• Have you signed the Contributor License Agreement?
• Is there a linked Issue? [Issue] ([Package Request]: Apache Maven #65391)

Manifests

• Have you checked that there aren't other open pull requests for the same manifest update/change? - There is one, but it is stale.
• This PR only modifies one (1) manifest
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[flakron]

@microsoft-github-policy-service agree [company="Flakron Bytyqi"]

[flakron]

@microsoft-github-policy-service agree

[stephengillie]

Hi @flakron,

• This appears to be the same package as another PR - should the same PackageIdentifier be used?
• This package appears to be a Java application.
  
• This means both that:
  • A JRE is a dependency
  • Unfortunately we're not currently accepting scripted (non-compiled) applications.

[flakron]

Hi @stephengillie

• I didn't see where any specific rule in regards to naming the PackageIdentifier, But to the point, since Maven is maintained by the Apache Foundation, and I'm not affiliated with them it didn't seem to me right to pretend that the package is built by them, and it seemed a bit disingenuous.
• The package is a dependency manager for java development. It is dependent on jdk not jre, JAVA_HOME is referred to the jdk install directory (whatever jdk the user is using).
• Unfortunately they will never have a executable binary. So maybe I close the pull request altogether, if the guidelines do not accept such cases (unfortunately since a lot of Java tools will never have binary executables).