- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 52 for All (0.2 sec)
-
maven-core/src/main/mdo/extension.mdo
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Wed Feb 07 21:28:01 GMT 2024 - 3.5K bytes - Viewed (0) -
guava-gwt/test/com/google/common/testing/Testing.gwt.xml
Java package; see https://goo.gl/pRV3Yn for details. The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. However, unlike our other packages, as of this writing it has test supersource but no prod supersource.
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.5K bytes - Viewed (0) -
guava-gwt/src/com/google/common/xml/Xml.gwt.xml
Java package; see https://goo.gl/pRV3Yn for details. The summary is that it ignores one file in favor of the other. util.concurrent, like nearly all our packages, has two .gwt.xml files: one for prod and one for tests. However, unlike our other packages, as of this writing it has test supersource but no prod supersource.
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.5K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/baseuri-interpolation/pom.xml
<version>1.0-SNAPSHOT</version> <name>Maven Integration Test :: MNG-3760</name> <description> Test interpolation of ${project.baseUri} </description> <properties> <!-- this is where we collect all the interpolated values for the POM dump --> <prop1>${project.baseUri}</prop1> </properties>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 1.2K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/basedir-interpolation/pom-with-unusual-name.xml
<name>Maven Integration Test :: MNG-3944</name> <description> Test that interpolation of ${basedir} works for a POM that is not named "pom.xml" </description> <properties> <!-- this is where we collect all the interpolated values for the POM dump --> <prop0>${basedir}</prop0> <prop1>${project.basedir}</prop1> </properties>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 1.3K bytes - Viewed (0) -
maven-core/src/test/resources-settings/test-pom-and-settings-interpolation/pom.xml
Test that POM interpolation uses the property values from the dominant profile source (POM vs. settings.xml). This boils down to the proper order of profile injection and interpolation, i.e. interpolate after profiles from all sources are injected. </description> <properties> <!-- collect the effective property values as derived by interpolation --> <pomVsSettingsInterpolated>${pomVsSettings}</pomVsSettingsInterpolated>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jan 11 18:17:16 GMT 2021 - 2.4K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/full-interpolation/pom.xml
<artifactId>coreit</artifactId> <version>0.1</version> <packaging>jar</packaging> <name>Maven Integration Test :: MNG-3833</name> <description> Test that POM interpolation fully interpolates all properties in data flow chain, i.e. where property A depends on property B, and property B depends on property C and so on. </description> <properties> <!--
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2.4K bytes - Viewed (0) -
api/maven-api-model/src/main/mdo/maven.mdo
| | o need to clean up all the descriptions, matching anything to the current project-descriptor.xml file and | improving on that | | o use enums where appropriate (eg dependency scope) | | o a number of elements have a groupId/artifactId and sometimes version. It would be good to have them all extend one | definition of these types | -->
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) -
futures/failureaccess/pom.xml
InternalFutures. Most users will never need to use this artifact. Its classes are conceptually a part of Guava, but they're in this separate artifact so that Android libraries can use them without pulling in all of Guava (just as they can use ListenableFuture by depending on the listenablefuture artifact). </description> <build> <plugins> <plugin> <artifactId>maven-jar-plugin</artifactId>
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Tue Oct 17 02:24:23 GMT 2023 - 3.3K bytes - Viewed (0) -
maven-core/src/test/projects/lifecycle-executor/project-with-inheritance/pom.xml
comprehension tool. Based on the concept of a project object model: builds, dependency management, documentation creation, site publication, and distribution publication are all controlled from the declarative file. Maven can be extended by plugins to utilise a number of other development tools for reporting or the build process. </description> <url>http://maven.apache.org/</url>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Thu Aug 03 09:29:10 GMT 2023 - 22.4K bytes - Viewed (0)