Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for asName (0.17 sec)

  1. api/maven-api-plugin/src/main/mdo/plugin.mdo

                Flags this Mojo as requiring information about the dependencies that would make up the specified class
                path. As the name suggests, this is similar to requiresDependencyResolution and supports the same values.
                The important difference is this will not resolve the files for the dependencies, i.e. the artifacts
                associated with a Maven project can lack a file. As such, this annotation is meant for Mojos that only
    XML
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Sun Apr 14 17:14:22 GMT 2024
    - 23.6K bytes
    - Viewed (0)
  2. api/maven-api-model/src/main/mdo/maven.mdo

                see <a href="../maven-core/artifact-handlers.html">default artifact handlers</a> for a list,</li>
                <li>distinguishing two artifacts
                that belong to the same POM but were built differently.
                For example, {@code jdk14} and {@code jdk15}.</li>
                </ul>
                ]]>
              </description>
              <type>String</type>
    XML
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Tue Apr 23 13:29:46 GMT 2024
    - 115.1K bytes
    - Viewed (0)
  3. guava-gwt/pom.xml

                covered by testModule.gwt.xml. Maybe I'll try it someday.
    
                [*] https://code.google.com/p/google-web-toolkit/wiki/ResourceOracle#When_multiple_PathPrefix_es_have_the_same_path
                    https://code.google.com/p/google-web-toolkit/issues/detail?id=7581
                -->
              <execution>
                <id>gwt-test</id>
                <goals>
                  <goal>test</goal>
    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. 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)
  5. android/pom.xml

                       animal-sniffer. And that would be fine for our -jre builds:
                       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.
    
    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)
  6. api/maven-api-metadata/src/main/mdo/metadata.mdo

                }
    
                if ( versioning.getLastUpdated() == null || versioning.getLastUpdated().length() == 0 )
                {
                    // this should only be for historical reasons - we assume local is newer
                    versioning.setLastUpdated( v.getLastUpdated() );
                }
    
                if ( v.getLastUpdated() == null || v.getLastUpdated().length() == 0
    XML
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Thu Apr 11 14:06:34 GMT 2024
    - 15.8K bytes
    - Viewed (0)
Back to top