- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 17 for execute (0.17 sec)
-
api/maven-api-plugin/src/main/mdo/lifecycle.mdo
</field> <field> <name>executions</name> <version>1.0.0</version> <description>The goals to execute within the phase.</description> <association> <type>Execution</type> <multiplicity>*</multiplicity> </association> </field> <field>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Wed Feb 07 21:28:01 GMT 2024 - 4.2K bytes - Viewed (0) -
api/maven-api-plugin/src/main/mdo/plugin.mdo
<required>true</required> <version>1.0.0+</version> <type>String</type> <description> The goal name for the Mojo, that users will reference from the command line to execute the Mojo directly, or inside a POM in order to provide Mojo-specific configuration. </description> </field> <field> <name>description</name>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Apr 14 17:14:22 GMT 2024 - 23.6K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/plugin-exec-inheritance/w-merge/pom.xml
</parent> <artifactId>child-1</artifactId> <name>Maven Integration Test :: MNG-4129 :: Child-1</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 redefine the test plugin again, i.e. trigger plugin merging --> <plugin>
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-order/w-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 uses plugin management for the test plugin --> <pluginManagement> <plugins> <plugin>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2.3K bytes - Viewed (0) -
maven-core/pom.xml
<groupId>org.apache.rat</groupId> <artifactId>apache-rat-plugin</artifactId> <configuration> <excludes combine.children="append"> <exclude>lifecycle-executor.txt</exclude> <exclude>plugin-manager.txt</exclude> <exclude>project-builder.txt</exclude> <exclude>src/site/resources/design/**</exclude> </excludes>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Thu Apr 25 08:48:58 GMT 2024 - 15.4K bytes - Viewed (0) -
maven-core/src/test/resources-project-builder/plugin-exec-goals-order/wo-plugin-mgmt/pom.xml
<artifactId>test</artifactId> <version>0.1</version> <packaging>pom</packaging> <name>Maven Integration Test :: MNG-3886</name> <description> Test that the goals from a plugin execution are executed in the order given by the POM, regardless whether plugin management is present or not. </description> <build> <!-- This project does not use plugin management for the test plugin --> <plugins>
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/plugin-exec-inheritance/pom.xml
<version>0.1</version> <packaging>pom</packaging> <name>Maven Integration Test :: MNG-4129</name> <description> Verify that plugin executions defined in the parent with inherited=false are not executed in child modules. </description> <modules> <module>child-1</module> <module>child-2</module> </modules> <build> <plugins> <plugin>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Mar 29 19:02:56 GMT 2020 - 2.3K bytes - Viewed (0) -
apache-maven/src/assembly/maven/conf/settings.xml
| or merely testing its existence. Profiles can also be activated by JDK version prefix, where a | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'. | Finally, the list of active profiles can be specified directly from the command line. | | NOTE: For profiles defined in the settings.xml, you are restricted to specifying only artifact
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jun 19 15:06:01 GMT 2023 - 11K bytes - Viewed (0) -
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>
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-compat/src/main/resources/META-INF/maven/plugin-expressions/settings.paramdoc.xml
<configuration> <![CDATA[ <offline>true</offline> ]]></configuration> <description> <![CDATA[ Flags the system as offline, to prevent accessing the network to resolve artifacts or execute plugins. NOTE: It's also possible to switch to offline mode on a per-build basis, using the '-o' command-line option. ]]></description> </expression> <expression>
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 2K bytes - Viewed (0)