Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 6 of 6 for We (0.14 sec)

  1. guava-gwt/pom.xml

                of those modules are ones that it uses but forgets to list in its own <inherits>, we'd
                like to get an error. Currently we do, but if we add the extra <inherits> lines, we
                won't.
    
                I have one idea for a better approach, but it's painful, and I haven't tested it: We
                could postprocess Collect.gwt.xml to add <skip> lines for all the files that should be
    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)
  2. maven-core/src/main/resources/META-INF/maven/extension.xml

        <!--
          | We may potentially want to export these, but right now I'm not sure that anything Guice specific needs
          | to be made available to plugin authors. If we find people are getting fancy and want to take advantage of
          | Guice specifics we can expose that later. Really some testing needs to be done to see full hiding
    XML
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Mon Jan 08 10:37:09 GMT 2024
    - 12.2K bytes
    - Viewed (0)
  3. apache-maven/src/assembly/maven/conf/settings.xml

       | However, this repository may have problems with heavy traffic at times, so people have mirrored
       | it to several places.
       |
       | That repository definition will have a unique id, so we can create a mirror reference for that
       | repository, to be used as an alternate download site. The mirror site will be the preferred
       | server for that repository.
       |-->
      <mirrors>
        <!-- mirror
    XML
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Mon Jun 19 15:06:01 GMT 2023
    - 11K 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)
  5. 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 Apr 28 03:35:10 GMT 2024
    - Last Modified: Thu Apr 11 14:06:34 GMT 2024
    - 15.8K bytes
    - Viewed (0)
  6. build-logic-commons/code-quality-rules/src/main/resources/checkstyle/suppressions.xml

        <suppress checks="InterfaceIsTypeCheck"
                  files=".*[/\\]core-api[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]api[/\\]attributes[/\\]Usage.+"/>
    
        <!-- We like it explicit -->
        <suppress checks="ExplicitInitializationCheck"
                  files=".*"/>
    
        <!-- Ignore code from maven subproject under org.apache -->
        <suppress checks="RegexpSingleline"
    XML
    - Registered: Wed Apr 24 11:36:11 GMT 2024
    - Last Modified: Thu Apr 11 10:51:28 GMT 2024
    - 10.3K bytes
    - Viewed (0)
Back to top