- Sort Score
- Result 10 results
- Languages All
Results 1 - 9 of 9 for Method (0.15 sec)
-
build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/rules/NullabilityBreakingChangesRule.groovy
} else if (member instanceof JApiMethod) { JApiMethod method = (JApiMethod) member CtMethod oldMethod = method.oldMethod.get() CtMethod newMethod = method.newMethod.get() inspectParametersNullabilityOf(oldMethod, newMethod) def oldNullability = hasNullableAnnotation(oldMethod)
Groovy - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Sat Apr 13 10:04:28 GMT 2024 - 5.4K bytes - Viewed (0) -
build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/rules/AbstractGradleViolationRule.groovy
return isAnnotatedWithIncubating(clazz) } private boolean isIncubatingOrOverrideMethod(JApiMethod method) { return isAnnotatedWithIncubating(method) || isAnnotatedWithIncubating(method.jApiClass) || isOverride(method) } private static boolean isIncubatingField(JApiField field) {
Groovy - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Apr 23 08:40:36 GMT 2024 - 10.4K bytes - Viewed (0) -
build-logic/binary-compatibility/src/test/kotlin/gradlebuild/binarycompatibility/UpgradedPropertiesChangesTest.kt
assertHasAccepted( "Method com.example.Task.getSourceCompatibility(): Is not binary compatible. Reason for accepting this: Upgraded property" to listOf("Method return type has changed", "Method is now abstract"), "Method com.example.Task.setSourceCompatibility(java.lang.String): Is not binary compatible. Reason for accepting this: Upgraded property" to listOf("Method has been removed") ) } }
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Apr 23 08:40:36 GMT 2024 - 20.2K bytes - Viewed (0) -
build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/upgrades/UpgradedProperties.java
import static gradlebuild.binarycompatibility.rules.SinceAnnotationMissingRule.SINCE_ERROR_MESSAGE; import static japicmp.model.JApiCompatibilityChange.METHOD_ADDED_TO_PUBLIC_CLASS; import static japicmp.model.JApiCompatibilityChange.METHOD_REMOVED; import static japicmp.model.JApiCompatibilityChange.METHOD_RETURN_TYPE_CHANGED; public class UpgradedProperties { private static final Pattern SETTER_REGEX = Pattern.compile("set[A-Z].*");
Java - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Apr 23 08:40:36 GMT 2024 - 6.8K bytes - Viewed (0) -
.github/workflows/codeql-analysis.yml
steps: - name: Checkout repository uses: actions/checkout@v4 # Checkout must run before the caching key is computed using the `hashFiles` method - name: Cache Gradle Modules uses: actions/cache@v4 with: path: | ~/.gradle/caches/modules-2/ ~/.gradle/caches/build-cache-1/ ~/.gradle/caches/signatures/
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 4K bytes - Viewed (0) -
build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/rules/UpgradePropertiesRulePostProcess.java
String formattedLeft = CollectionUtils.join("\n", keptAccessors.keySet()); throw new RuntimeException("The following accessors were upgraded, but didn't match any removed/changed method:\n\n" + formattedLeft); } // Find accessors that were removed but shouldn't be Map<AccessorKey, ReplacedAccessor> removedAccessors = new HashMap<>(oldAccessorsOfUpgradedProperties);
Java - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Apr 23 08:40:36 GMT 2024 - 3.4K bytes - Viewed (0) -
.idea/inspectionProfiles/Gradle.xml
<replaceConfiguration name="Treat some Guava Collection factory methods as Deprecated" uuid="82f9f9ab-9c3b-367f-99ad-40841dc13819" description="Many no-argument Guava Collection factory methods are marked in their javadoc "Should be treated as deprecated". These should not be used." suppressId="guava-collection-factory" problemDescriptor="Treat some Guava Collection factory methods as Deprecated" text="com.google.common.collect.Lists.newArrayList()" recursive="false"...
XML - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu Apr 11 13:39:08 GMT 2024 - 13K bytes - Viewed (0) -
architecture/standards/0003-avoid-introducing-Groovy-types-to-public-api.md
This has been mostly done, but there remain a few holdouts (fixing these is out of scope). To keep the Groovy DSL ergonomic, we generate methods as necessary from the non-Groovy equivalents. Doing this provides the following specific benefits: - **Reduce the API surface** - We no longer need to maintain two methods. - **Consistency** - All languages have consistent access to the same APIs and ergonomics in the DSL.
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) -
CONTRIBUTING.md
## Making your change ### Code change guidelines All code contributions should contain the following: * Create unit tests using [Spock](https://spockframework.org/spock/docs/2.0/index.html) for new classes or methods that you introduce. * Create integration tests that exercise a Gradle build for the bug/feature. * Annotate tests that correspond to a bug on GitHub (`@Issue("https://github.com/gradle/gradle/issues/2622")`).
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sat May 04 07:43:02 GMT 2024 - 15.6K bytes - Viewed (0)