- Sort Score
- Result 10 results
- Languages All
Results 31 - 40 of 54 for Sall (0.12 sec)
-
apache-maven/src/assembly/maven/conf/settings.xml
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Jun 19 15:06:01 GMT 2023 - 11K bytes - Viewed (0) -
guava-gwt/pom.xml
its builds. Thus, GWT doesn't get j2objc-annotations transitively, in contrast to the other deps of `guava`, which it does get transitively. (Arguably we should redeclare *all* the `guava` deps here.) --> <dependency> <groupId>com.google.j2objc</groupId> <artifactId>j2objc-annotations</artifactId> </dependency> <dependency> <groupId>com.google.guava</groupId>
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Apr 11 15:00:55 GMT 2024 - 19.8K bytes - Viewed (0) -
futures/listenablefuture1/pom.xml
"version" that omits the class to avoid conflicts with the copy in Guava itself. The idea is: - If users want only ListenableFuture, they depend on listenablefuture-1.0. - If users want all of Guava, they depend on guava, which, as of Guava 27.0, depends on listenablefuture-9999.0-empty-to-avoid-conflict-with-guava. The 9999.0-... version number is enough for some build systems (notably, Gradle) to select
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Wed Sep 12 21:42:09 GMT 2018 - 2.2K bytes - Viewed (0) -
pom.xml
</profile> </profiles> <build> <finalName>fess</finalName> <resources> <resource> <directory>src/main/resources</directory> </resource> </resources> <!-- This file contains all the common properties used to build the different packages (tar.gz, deb, rpm) using Maven resources plugin --> <filters> <filter>src/packaging/common/packaging.properties</filter> </filters> <plugins>
XML - Registered: Mon May 06 08:04:11 GMT 2024 - Last Modified: Mon Apr 22 12:06:58 GMT 2024 - 48.7K bytes - Viewed (0) -
guava-gwt/src/com/google/common/util/concurrent/Concurrent.gwt.xml
Java package; see https://goo.gl/pRV3Yn for details. The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. However, unlike our other packages, as of this writing it has test supersource but no prod supersource.
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Tue Jul 19 04:29:50 GMT 2022 - 1.5K bytes - Viewed (0) -
guava-gwt/src/com/google/common/cache/Cache.gwt.xml
Java package; see https://goo.gl/pRV3Yn for details. The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. However, unlike our other packages, as of this writing it has test supersource but no prod supersource.
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.6K bytes - Viewed (0) -
guava-gwt/test/com/google/common/collect/testing/google/Google.gwt.xml
Java package; see https://goo.gl/pRV3Yn for details. The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. However, unlike our other packages, as of this writing it has test supersource but no prod supersource.
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.7K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/basedir-aligned-interpolation/pom.xml
<name>Maven Integration Test :: MNG-3822</name> <description> Verify that POM interpolation uses basedir-aligned build directories. </description> <properties> <!-- this is where we collect all the interpolated values for the POM dump --> <buildMainSrc>${project.build.sourceDirectory}</buildMainSrc> <buildTestSrc>${project.build.testSourceDirectory}</buildTestSrc>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2.2K bytes - Viewed (0) -
apache-maven/src/assembly/maven/conf/toolchains.xml
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu Dec 24 18:09:10 GMT 2020 - 3.5K 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)