Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for users (0.16 sec)

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

                Specifies that this parameter can be configured directly by the user (as in the case of POM-specified
                configuration). This is useful when you want to force the user to use common POM elements rather than
                plugin configurations, as in the case where you want to use the artifact's final name as a parameter. In
                this case, you want the user to modify {@code <build><finalName/></build>} rather
    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. guava-gwt/pom.xml

            <configuration>
              <excludes>
                <!-- 2. Don't include the source in the jar (since that would let users depend on it from GWT client code, which is compiled from source). -->
                <exclude>**/ForceGuavaCompilation*</exclude>
                <exclude>**/DummyJavadocClass*</exclude>
              </excludes>
            </configuration>
          </plugin>
          <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)
  3. android/pom.xml

                  <version>0.6.1</version>
                  <!-- TODO(cpovirk): In principle, it would make sense to *also* test compatibility with JDK 1.8, since guava-android also has JRE users. -->
                </signature>
                <ignores>
                  <!-- Unsafe isn't part of the documented Android API, but it is available.
    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