- Sort Score
- Result 10 results
- Languages All
Results 1 - 7 of 7 for Tate (0.17 sec)
-
.teamcity/performance-test-durations.json
"durations" : [ { "testProject" : "largeJavaMultiProject", "linux" : 508 }, { "testProject" : "largeMonolithicJavaProject", "linux" : 209 } ] }, { "scenario" : "org.gradle.performance.regression.java.JavaIncrementalExecutionPerformanceTest.up-to-date assemble (parallel true)", "durations" : [ {
Json - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Feb 19 11:22:56 GMT 2024 - 26.3K bytes - Viewed (1) -
architecture/standards/0005-introduce-core-ui-architecture-module.md
# ADR-0004 - Introduce a UI architecture module to the core platform ## Date 2024-02-07 ## Context The Gradle core platform provides many services to the Gradle platforms and builds logic. One such group of services allows logic to interact with the build user, to provide diagnostics, progress information, prompt for questions, and so on. Currently, these services are part of the core platform runtime architecture module.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Mar 04 23:19:15 GMT 2024 - 1.3K bytes - Viewed (0) -
architecture/standards/0001-use-architectural-decision-records.md
# ADR-0001 - Use Architectural Decision Records ## Date 2023-12-01 ## Context In a distributed team with many subteams, the best solution to communicate decisions is to use a format accessible by everyone in charge of development. We use *Specification* and *Discovery* documents stored in Google Drive, but they present some downsides:
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) -
.teamcity/performance-tests-ci.json
"groups" : [ { "testProject" : "largeJavaMultiProject", "coverage" : { "per_commit" : [ "linux", "windows" ] } } ] }, { "testId" : "org.gradle.performance.regression.java.JavaIncrementalExecutionPerformanceTest.up-to-date assemble with local build cache enabled (parallel false)", "groups" : [ {
Json - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon May 06 09:01:23 GMT 2024 - 35.5K bytes - Viewed (0) -
architecture/standards/0003-avoid-introducing-Groovy-types-to-public-api.md
# ADR-0003 - Avoid introducing Groovy types to public API ## Date 2024-01-12 ## Context Gradle's public API requires equal access from all JVM-based languages. Kotlin, Groovy, Java, and other JVM-based languages should be able to use the Gradle API without relying on another language's standard library. Historically, Gradle has shipped with some Groovy types in very prominent APIs.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun Mar 10 20:38:06 GMT 2024 - 1.8K bytes - Viewed (0) -
architecture/standards/0002-avoid-using-java-serialization.md
# ADR-0002 - Avoid using Java serialization ## Date 2012-12-01 ## Context In Gradle we often need to serialize in-memory objects for caching, or to transmit them across process barriers, etc. Java serialization is one way to implement this, however, despite its simplicity of implementation, it has several drawbacks: - **Performance:** Java's built-in serialization mechanism is often slower compared to other serialization solutions.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu Feb 29 22:32:18 GMT 2024 - 2.3K bytes - Viewed (0) -
architecture/standards/0004-use-a-platform-architecture.md
# ADR-0004 - Use a platform-oriented architecture for Gradle ## Date 2024-02-07 ## Context The Gradle code base is essentially a large monolith, without strong internal boundaries. This has a number of negative effects on productivity, including: - Unclear ownership of code. - Difficult to focus on one particular area. - Unintended coupling between areas of the code, including tests. ## Decision
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun Feb 25 22:19:29 GMT 2024 - 4.5K bytes - Viewed (0)