- Sort Score
- Result 10 results
- Languages All
Results 61 - 70 of 90 for Aare (0.12 sec)
-
apache-maven/src/assembly/maven/conf/toolchains.xml
| | NOTE: This location can be overridden with the CLI option: | | -gt /path/to/global/toolchains.xml | | The sections in this sample file are intended to give you a running start at | getting the most out of your Maven installation. |--> <toolchains xmlns="http://maven.apache.org/TOOLCHAINS/1.1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu Dec 24 18:09:10 GMT 2020 - 3.5K bytes - Viewed (0) -
build-logic-commons/code-quality-rules/src/main/resources/checkstyle/suppressions.xml
<!-- These packages are duplicated in ide-native from ide, don't require a package-info.java in each place --> <suppress checks="JavadocPackage" files=".*[/\\]ide-native[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]plugins[/\\]ide[/\\]api[/\\][^/\\]+"/>
XML - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Thu Apr 11 10:51:28 GMT 2024 - 10.3K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/plugin-exec-inheritance/wo-merge/pom.xml
</parent> <artifactId>child-2</artifactId> <name>Maven Integration Test :: MNG-4129 :: Child-2</name> <description> Verify that plugin executions defined in the parent with inherited=false are not executed in child modules. </description> <build> <plugins> <!-- NOTE: It's essential part of this test variant to *not* define the test plugin again, i.e. bypass plugin merging --> </plugins>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 1.4K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/merged-plugin-exec-goals-order/wo-plugin-mgmt/pom.xml
<version>0.1</version> <packaging>pom</packaging> <name>Maven Integration Test :: MNG-3937</name> <description> Test that during inheritance/merging of a plugin execution the goals specified by child and parent are properly ordered. </description> <build> <!-- This project does not use plugin management for the test plugin --> <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-project-builder/managed-profile-dependency/pom.xml
<artifactId>parent</artifactId> <version>1.0-SNAPSHOT</version> <packaging>pom</packaging> <name>Maven Integration Test :: MNG-4034</name> <description> Verify that dependencies defined in profiles are subject to the dependency management of the parent. </description> <modules> <module>sub</module> </modules> <dependencyManagement> <dependencies> <dependency>
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/profile-plugin-mng-dependencies/sub/pom.xml
<artifactId>child</artifactId> <version>1.0-SNAPSHOT</version> <name>Maven Integration Test :: MNG-2174</name> <description> Verify that plugin dependencies defined by plugin management of a parent profile are not lost when the parent's main plugin management section is also present. </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 - 2K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/plugin-config-attributes/w-plugin-mgmt/pom.xml
<artifactId>test2</artifactId> <version>1.0-SNAPSHOT</version> <name>Maven Integration Test :: MNG-4053</name> <description> Verify that attributes in plugin configuration elements are not erroneously duplicated to other elements when plugin management is used. </description> <build> <!-- NOTE: This test used plugin management for the IT plugin --> <pluginManagement> <plugins>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/plugin-exec-order/wo-plugin-mgmt/pom.xml
<artifactId>test</artifactId> <version>0.1</version> <packaging>pom</packaging> <name>Maven Integration Test :: MNG-3887</name> <description> Test that multiple plugin executions bound to the same phase are executed in the order given by the POM. </description> <build> <!-- This project does not use plugin management for the test plugin --> <plugins> <plugin>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2K bytes - Viewed (0) -
futures/listenablefuture9999/pom.xml
version number is enough for some build systems (notably, Gradle) to select that empty artifact over the "real" listenablefuture-1.0 -- avoiding a conflict with the copy of ListenableFuture in guava itself. If users are using an older version of Guava or a build system other than Gradle, they may see class conflicts. If so, they can solve them by manually excluding the listenablefuture artifact or manually forcing their build systems to
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) -
maven-core/src/test/resources-project-builder/xml-coalesce-text/pom.xml
--> <prop0>A <![CDATA[ Test ]]> Project<![CDATA[ ]]>Property</prop0> <!-- This checks the coalescing of CHARACTERS events that are interleaved with comments. Note that inner whitespace formed by whitespace-only events must be retained. --> <prop1><!-- X -->That's<!-- X --> <!-- X -->a<!-- X --> <!-- X -->test!<!-- X --></prop1> <!--
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 34.5K bytes - Viewed (0)