Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 5 of 5 for Shing (0.17 sec)

  1. build-logic/binary-compatibility/src/test/kotlin/gradlebuild/binarycompatibility/AbstractBinaryCompatibilityTest.kt

            }
    
            fun newApi(thing: String, desc: String): String =
                "$thing ${describe(thing, desc)}: New public API in 2.0 (@Incubating)"
    
            fun added(thing: String, desc: String): List<String> =
                listOf(
                    "$thing ${describe(thing, desc)}: Is not annotated with @Incubating.",
                    "$thing ${describe(thing, desc)}: Is not annotated with @since 2.0."
                )
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Mon Sep 25 13:49:37 GMT 2023
    - 16.4K bytes
    - Viewed (0)
  2. build-logic/documentation/src/test/groovy/gradlebuild/docs/dsl/docbook/JavadocConverterTest.groovy

            PropertyMetaData propertyMetaData = Mock()
            _ * propertyMetaData.rawCommentText >> 'returns the name of the thing.'
    
            when:
            def result = parser.parse(propertyMetaData, listener)
    
            then:
            format(result.docbook) == '''<para>The name of the thing.</para>'''
        }
    
        def convertsPropertySetterMethodCommentToPropertyComment() {
    Groovy
    - Registered: Wed Apr 17 11:36:08 GMT 2024
    - Last Modified: Wed Dec 09 08:14:05 GMT 2020
    - 14.2K bytes
    - Viewed (0)
  3. architecture-standards/0001-use-architectural-decision-records.md

    The main logic with ADRs is to describe (architectural) decisions made:
    
    * To provide best practices and solutions we (as *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.
    
    ADRs can be written by any team.
    Plain Text
    - Registered: Wed Feb 14 11:36:15 GMT 2024
    - Last Modified: Wed Feb 07 00:43:19 GMT 2024
    - 2.8K bytes
    - Viewed (0)
  4. architecture/standards/0001-use-architectural-decision-records.md

    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.
    
    ADRs can be written by any team.
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Sat Mar 02 21:54:40 GMT 2024
    - 2.8K bytes
    - Viewed (0)
  5. build-logic/cleanup/src/test/groovy/gradlebuild/cleanup/services/LeakingProcessKillPatternTest.groovy

            def projectDir = 'C:\\some\\agent\\workspace'
    
            expect:
    Groovy
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Thu Sep 28 07:00:39 GMT 2023
    - 14.4K bytes
    - Viewed (0)
Back to top