Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for testudo (0.18 sec)

  1. guava-gwt/pom.xml

                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
                covered by testModule.gwt.xml. Maybe I'll try it someday.
    
    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/test/resources/project-dynamism/pom-interp.xml

        <plugins>
          <plugin>
            <artifactId>my-plugin</artifactId>
            <configuration>
              <testOne>${project.groupId}</testOne>
              <testTwo>${pom.groupId}</testTwo>
              <testThree>${groupId}</testThree>
            </configuration>
          </plugin>
        </plugins>
      </build>
    
    XML
    - Registered: Sun Mar 31 03:35:09 GMT 2024
    - Last Modified: Sat Nov 09 12:45:14 GMT 2019
    - 903 bytes
    - Viewed (0)
  3. api/maven-api-model/src/main/mdo/maven.mdo

              <description>
                This element specifies a directory containing the unit test source of the
                project. The generated build system will compile these directories when the project is
                being tested. The path given is relative to the project descriptor.
                The default value is {@code src/test/java}.
              </description>
              <type>String</type>
            </field>
            <field>
    XML
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Tue Apr 23 13:29:46 GMT 2024
    - 115.1K bytes
    - Viewed (0)
  4. android/pom.xml

          </activation>
          <properties>
            <!--
                Some tests need reflective access to the internals of these packages. It is only the
                tests themselves and not the code being tested that needs that access, though there's no
                obvious way to ensure that.
    
                We could consider arranging things so that only the tests we know need this would get
    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