Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/lacasseio/gradle-packaging
https://github.com/lacasseio/gradle-packaging
Last synced: 2 days ago
JSON representation
- Host: GitHub
- URL: https://github.com/lacasseio/gradle-packaging
- Owner: lacasseio
- License: apache-2.0
- Created: 2018-11-09T13:16:29.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2018-11-09T13:48:04.000Z (about 6 years ago)
- Last Synced: 2024-11-11T21:42:32.895Z (2 months ago)
- Size: 5.86 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 9
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Gradle Packaging Support
## Problem
Officially, the Gradle team has only the bandwidth to package Gradle distribution as a zip hosted on [their Website](https://gradle.org/install/). The Gradle community is strong and filled with motivated developers to maintain a varity of packaging support such as Debian, Fedora, Homebrew, MacPorts, etc. The fundamental issue with this approach is the transparency of the process used to publish those package. As an user, you are trusting those adhoc process. After looking at some of them, I'm seeing horrors such as patching the distribution to use a different dependency version then what was originally build with. Although those patch were probably done with care, it deliver a similar but different version of Gradle to the consumer. These difference is what could cause a bad experience Gradle and in turn hurt Gradle's reputation. It goes without saying that some of these adhoc process could fall out of date due to the unavailibility of the maintainer or, worst, packaged with unsafe code.## Solution
Let's gather all the Gradle packaging support in the same repository and automate everything under the same, transparent, process. The goal is to be greatful to all their hard work done by the maintainer and centralizing all the packaging support needs of the community. On the security side, we can vet that the distribution remains intact throughout the packaging chain.## Contribution
We accept all contribution regarding how each packaging needs to be supported. Each packaging support automation chain needs to include test coverage.