- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for Ball (0.21 sec)
-
.idea/runConfigurations/Analysis_All_Tests.xml
<component name="ProjectRunConfigurationManager"> <configuration default="false" name="Analysis All Tests" type="GradleRunConfiguration" factoryName="Gradle" folderName="Analysis"> <ExternalSystemSettings> <option name="executionName" /> <option name="externalProjectPath" value="$PROJECT_DIR$" /> <option name="externalSystemIdString" value="GRADLE" /> <option name="scriptParameters" value="" /> <option name="taskDescriptions">
XML - Registered: Fri May 03 08:18:13 GMT 2024 - Last Modified: Wed Jan 03 13:39:42 GMT 2024 - 1K bytes - Viewed (0) -
api/maven-api-plugin/src/main/mdo/lifecycle.mdo
</association> </field> <field> <name>configuration</name> <version>1.0.0</version> <type>DOM</type> <description>Configuration to pass to all goals run in this phase.</description> </field> </fields> </class> <class> <name>Execution</name> <version>1.0.0</version> <description>A set of goals to execute.</description>
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Feb 07 21:28:01 GMT 2024 - 4.2K bytes - Viewed (0) -
maven-core/src/main/mdo/extension.mdo
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Wed Feb 07 21:28:01 GMT 2024 - 3.5K bytes - Viewed (0) -
futures/failureaccess/pom.xml
InternalFutures. Most users will never need to use this artifact. Its classes are conceptually a part of Guava, but they're in this separate artifact so that Android libraries can use them without pulling in all of Guava (just as they can use ListenableFuture by depending on the listenablefuture artifact). </description> <build> <plugins> <plugin> <artifactId>maven-jar-plugin</artifactId>
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Tue Oct 17 02:24:23 GMT 2023 - 3.3K bytes - Viewed (0) -
api/maven-api-toolchain/src/main/mdo/toolchains.mdo
if match is found, the toolchain instance is made available to other Maven plugins.</p> <p>With {@code jdk} toolchain, for example, instead of being stuck with the JDK used to run Maven, all plugins can use the same other JDK instance without hardcoding absolute paths into the {@code pom.xml} and without configuring every plugin that require path to JDK tools.</p>
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Wed Feb 07 21:28:01 GMT 2024 - 8.5K bytes - Viewed (0) -
.teamcity/pom.xml
</properties> <groupId>Gradle_Check</groupId> <artifactId>Gradle_Check_dsl</artifactId> <version>1.0-SNAPSHOT</version> <repositories> <repository> <id>jetbrains-all</id> <url>https://download.jetbrains.com/teamcity-repository</url> <snapshots> <enabled>true</enabled> </snapshots> </repository> <repository>
XML - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Dec 05 00:08:14 GMT 2023 - 8.4K bytes - Viewed (0) -
guava/pom.xml
<configuration> <!-- Passing `-subpackages com.google.common` breaks things, so we explicitly exclude everything else instead. --> <!-- excludePackageNames requires specification of packages separately from "all subpackages". https://issues.apache.org/jira/browse/MJAVADOC-584 --> <excludePackageNames>
XML - Registered: Fri Apr 05 12:43:09 GMT 2024 - Last Modified: Mon Mar 11 16:37:45 GMT 2024 - 8.9K bytes - Viewed (0) -
android/guava/pom.xml
<configuration> <!-- Passing `-subpackages com.google.common` breaks things, so we explicitly exclude everything else instead. --> <!-- excludePackageNames requires specification of packages separately from "all subpackages". https://issues.apache.org/jira/browse/MJAVADOC-584 --> <excludePackageNames>
XML - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Mon Mar 11 16:37:45 GMT 2024 - 8.9K bytes - Viewed (0)