Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for apps (0.12 sec)

  1. maven-core/src/test/resources-project-builder/duplicate-exclusions-dependency/sub/pom.xml

        <artifactId>nexus</artifactId>
        <version>1.3.0-SNAPSHOT</version>
      </parent>
      <modelVersion>4.0.0</modelVersion>
      <artifactId>nexus-proxy</artifactId>
      <dependencies>
        <!-- For App basic -->
        <dependency>
          <groupId>org.codehaus.plexus</groupId>
          <artifactId>plexus-container-default</artifactId>
        </dependency>
      </dependencies>
    XML
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Sat Nov 09 12:45:14 GMT 2019
    - 628 bytes
    - Viewed (0)
  2. .teamcity/pom.xml

                <snapshots>
                    <enabled>true</enabled>
                </snapshots>
            </repository>
            <repository>
                <id>teamcity-server</id>
                <url>https://builds.gradle.org/app/dsl-plugins-repository</url>
                <snapshots>
                    <enabled>true</enabled>
                </snapshots>
            </repository>
        </repositories>
    
        <pluginRepositories>
            <pluginRepository>
    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)
  3. guava-gwt/pom.xml

              <show>package</show>
            </configuration>
          </plugin>
          <!-- Disable "normal" testing, which doesn't work for GWT tests. -->
          <plugin>
    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)
  4. android/pom.xml

                       If we're building with JDK8, then clearly we're sticking to
                       JDK8 APIs. However, I assume (but did not confirm) that we'd
                       have the same issue with our -android builds, which need
                       animal-sniffer so that they can check that we're sticking to
                       JDK6-like APIs.
    
                       So instead, we use javac9, which doesn't lead to this error.
                  -->
    XML
    - Registered: Fri Apr 26 12:43:10 GMT 2024
    - Last Modified: Tue Mar 12 20:26:18 GMT 2024
    - 19.4K bytes
    - Viewed (0)
Back to top