Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 5 of 5 for within (0.56 sec)

  1. 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-...
    Registered: Wed Jun 12 16:38:11 UTC 2024
    - Last Modified: Wed Sep 12 21:42:09 UTC 2018
    - 2.2K bytes
    - Viewed (0)
  2. guava/pom.xml

    <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
      <!-- do_not_remove: published-with-gradle-metadata -->
      <modelVersion>4.0.0</modelVersion>
      <parent>
        <groupId>com.google.guava</groupId>
        <artifactId>guava-parent</artifactId>
        <version>HEAD-jre-SNAPSHOT</version>
      </parent>
    Registered: Wed Jun 12 16:38:11 UTC 2024
    - Last Modified: Mon Mar 11 16:37:45 UTC 2024
    - 8.9K bytes
    - Viewed (0)
  3. android/guava/pom.xml

    <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
      <!-- do_not_remove: published-with-gradle-metadata -->
      <modelVersion>4.0.0</modelVersion>
      <parent>
        <groupId>com.google.guava</groupId>
        <artifactId>guava-parent</artifactId>
        <version>HEAD-android-SNAPSHOT</version>
      </parent>
    Registered: Wed Jun 12 16:38:11 UTC 2024
    - Last Modified: Mon Mar 11 16:37:45 UTC 2024
    - 8.9K bytes
    - Viewed (0)
  4. android/pom.xml

                       builds with JDK8 began failing animal-sniffer with the error:
    
                       Failed to check signatures: Bad class file .../CollectionFuture$ListFuture.class
    
                       One way of dealing with that would be to disable
                       animal-sniffer. And that would be fine for our -jre builds:
                       If we're building with JDK8, then clearly we're sticking to
    Registered: Wed Jun 12 16:38:11 UTC 2024
    - Last Modified: Mon Jun 03 20:33:34 UTC 2024
    - 19.4K bytes
    - Viewed (0)
  5. pom.xml

                       builds with JDK8 began failing animal-sniffer with the error:
    
                       Failed to check signatures: Bad class file .../CollectionFuture$ListFuture.class
    
                       One way of dealing with that would be to disable
                       animal-sniffer. And that would be fine for our -jre builds:
                       If we're building with JDK8, then clearly we're sticking to
    Registered: Wed Jun 12 16:38:11 UTC 2024
    - Last Modified: Mon Jun 03 20:33:34 UTC 2024
    - 19K bytes
    - Viewed (0)
Back to top