- Sort Score
- Result 10 results
- Languages All
Results 1 - 2 of 2 for barrier (0.14 sec)
-
build-logic/documentation/src/test/groovy/gradlebuild/docs/FindBrokenInternalLinksTest.groovy
} def "validates present section links"() { given: sampleDoc << """ [[prior_section]] Text === Valid Section Links This section comes earlier: <<prior_section>> This section comes later: <<subsequent_section>> [[subsequent_section]] More text """ when: run('checkDeadInternalLinks').build() then:
Groovy - Registered: Wed Apr 17 11:36:08 GMT 2024 - Last Modified: Mon Nov 28 22:01:54 GMT 2022 - 7.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)