- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for Practices (0.19 sec)
-
Development.md
# Development best practices This is a collection of best practices for Gradle implementation. Should and should not do's. ## Error messages and suggestions Traditionally, if an error occurred, the error message and the possible solution were provided to the console via a single String in the corresponding exception. That meant possible solutions for Problems could be scattered all over the console output.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Feb 06 22:54:40 GMT 2024 - 1.8K bytes - Viewed (0) -
README.md
</picture> [![Revved up by Develocity](https://img.shields.io/badge/Revved%20up%20by-Develocity-06A0CE?logo=Gradle&labelColor=02303A)](https://ge.gradle.org/scans) [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/4898/badge)](https://bestpractices.coreinfrastructure.org/projects/4898)
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun Mar 24 20:49:08 GMT 2024 - 3.9K bytes - Viewed (0) -
architecture/standards/0001-use-architectural-decision-records.md
The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow. The main logic with ADRs is to describe (architectural) decisions made: * To provide best practices and solutions we (as the *build tool* team) want to promote. * To avoid asking the same thing multiple times during code review. * To explain *rejected solutions*, for now, and future development, in case they are proposed again.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sat Mar 02 21:54:40 GMT 2024 - 2.8K bytes - Viewed (0)