- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 19 for if (0.13 sec)
-
maven-core/src/test/resources-project-builder/plugin-exec-order-with-lifecycle/pom.xml
<packaging>JAR</packaging> <name>Maven Integration Test :: MNG-4341</name> <description> Test that plugins bound to the same phase get executed in POM order even if one of the plugins participates in the default lifecycle bindings for the project's packaging. </description> <build> <plugins> <plugin> <groupId>org.apache.maven.its.plugins</groupId>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 1.9K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/id-container-joining-with-empty-elements/pom.xml
<version>0.1</version> <packaging>pom</packaging> <name>Maven Integration Test :: MNG-3979</name> <description> Test that during inheritance the merging/joining of subtrees with equal identifier doesn't crash if the parent POM has a non-empty element and the child POM has an empty element to join. </description> <properties> <prop0>test</prop0> </properties> <repositories> <repository>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 2.8K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/unique-repo-id/artifact-repo-in-profile/pom.xml
<version>0.1</version> <packaging>jar</packaging> <name>Maven Integration Test :: MNG-4193</name> <description> Test that multiple artifact repository declarations with the same id cause a validation error even if the repositories are defined within a (non-active) profile. </description> <profiles> <profile> <id>test</id> <repositories> <repository> <id>one</id>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 1.6K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/plugin-exec-merging-wo-version/pom.xml
<version>0.1</version> <packaging>pom</packaging> <name>Maven Integration Test :: MNG-3916</name> <description> Test that plugin executions are properly merged during inheritance, even if the child plugin section has no version. </description> <build> <plugins> <plugin> <groupId>org.apache.maven.its.plugins</groupId> <artifactId>maven-it-plugin-a</artifactId>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 1.7K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/plugin-exec-merging-version-insensitive/sub/pom.xml
<version>0.1</version> </parent> <artifactId>child</artifactId> <name>Maven Integration Test :: MNG-3943</name> <description> Test that plugin executions are properly merged during inheritance, even if the child uses a different plugin version than the parent. </description> <build> <plugins> <plugin> <groupId>org.apache.maven.its.plugins</groupId>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 1.8K bytes - Viewed (0) -
maven-core/src/test/resources/org/apache/maven/lifecycle/pom.xml
<classWorldsVersion>1.3</classWorldsVersion> <commonsCliVersion>1.0</commonsCliVersion> <!-- Do not update this, Doxia will be decoupled completely from 3.x and someone can create a rendering engine for it if they like when the release stabilizes. JVZ --> <doxiaVersion>1.0-alpha-9</doxiaVersion> <easyMockVersion>1.2_Java1.3</easyMockVersion> <junitVersion>4.13.1</junitVersion>
XML - Registered: Sun Mar 31 03:35:09 GMT 2024 - Last Modified: Sat Sep 11 08:52:20 GMT 2021 - 22.4K bytes - Viewed (0) -
maven-core/src/test/projects/plugin-manager/project-with-inheritance/pom.xml
<classWorldsVersion>1.3</classWorldsVersion> <commonsCliVersion>1.0</commonsCliVersion> <!-- Do not update this, Doxia will be decoupled completely from 3.x and someone can create a rendering engine for it if they like when the release stabilizes. JVZ --> <doxiaVersion>1.0-alpha-9</doxiaVersion> <easyMockVersion>1.2_Java1.3</easyMockVersion> <junitVersion>4.13.1</junitVersion>
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) -
maven-core/src/test/resources-project-builder/id-container-joining-with-empty-elements/sub/pom.xml
</parent> <artifactId>child</artifactId> <name>Maven Integration Test :: MNG-3979</name> <description> Test that during inheritance the merging/joining of subtrees with equal identifier doesn't crash if the parent POM has a non-empty element and the child POM has an empty element to join. </description> <properties/> <repositories> <repository> <id>equal-repo-id</id>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 2.3K bytes - Viewed (0) -
maven-core/src/test/projects/lifecycle-executor/project-with-inheritance/pom.xml
<classWorldsVersion>1.3</classWorldsVersion> <commonsCliVersion>1.0</commonsCliVersion> <!-- Do not update this, Doxia will be decoupled completely from 3.x and someone can create a rendering engine for it if they like when the release stabilizes. JVZ --> <doxiaVersion>1.0-alpha-9</doxiaVersion> <easyMockVersion>1.2_Java1.3</easyMockVersion> <junitVersion>4.13.1</junitVersion>
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) -
futures/listenablefuture9999/pom.xml
contains com.google.common.util.concurrent.ListenableFuture class, without any other Guava classes. The idea is: - If users want only ListenableFuture, they depend on listenablefuture-1.0. - If users want all of Guava, they depend on guava, which, as of Guava 27.0, depends on listenablefuture-9999.0-empty-to-avoid-conflict-with-guava. The 9999.0-...
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Wed Sep 12 21:42:09 GMT 2018 - 2.2K bytes - Viewed (0)