- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 33 for note (0.4 sec)
-
api/maven-api-plugin/src/main/mdo/plugin.mdo
<version>1.0.0+</version> <type>String</type> <description> Defines a default phase to bind a Mojo execution to if the user does not explicitly set a phase in the POM. <p><b>Note:</b> This will not automagically make a Mojo run when the plugin declaration is added to the POM. It merely enables the user to omit the {@code <phase>} element from the
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sun Apr 14 17:14:22 GMT 2024 - 23.6K bytes - Viewed (0) -
.idea/kotlinTestDataPluginTestDataPaths.xml
XML - Registered: Fri May 03 08:18:13 GMT 2024 - Last Modified: Fri Apr 19 08:18:44 GMT 2024 - 4.9K bytes - Viewed (0) -
guava-gwt/src/com/google/common/collect/Collect.gwt.xml
Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) --> <super-source path="super"/> <inherits name="com.google.common.annotations.Annotations" />
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Mon Apr 24 14:08:06 GMT 2023 - 1.5K bytes - Viewed (0) -
api/pom.xml
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu Apr 25 08:48:58 GMT 2024 - 3.7K bytes - Viewed (0) -
maven-bom/pom.xml
<plugin> <groupId>org.apache.rat</groupId> <artifactId>apache-rat-plugin</artifactId> <executions> <execution> <id>rat-check</id> <phase>none</phase> </execution> </executions> </plugin> </plugins> </build>
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Thu Apr 25 08:48:58 GMT 2024 - 7.4K bytes - Viewed (0) -
api/maven-api-model/src/main/mdo/maven.mdo
<fields> <field> <name>defaultGoal</name> <version>3.0.0+</version> <description>The default goal (or phase in Maven 2) to execute when none is specified for the project. Note that in case of a multi-module build, only the default goal of the top-level project is relevant, i.e. the default goals of child modules are ignored. Since Maven 3,
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) -
maven-core/src/main/resources/META-INF/maven/extension.xml
<exportedArtifact>org.eclipse.aether:aether-util</exportedArtifact> <exportedArtifact>org.eclipse.aether:aether-connector-basic</exportedArtifact> <!-- | NOTE: Don't exclude the wagons or any of their dependencies (apart from the wagon API). This would otherwise | provoke linkage errors for wagons contributed by build extensions. We also don't need to exclude the wagons
XML - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jan 08 10:37:09 GMT 2024 - 12.2K bytes - Viewed (0) -
apache-maven/src/assembly/maven/conf/settings.xml
| | NOTE: This location can be overridden with the CLI option: | | -gs /path/to/global/settings.xml | | The sections in this sample file are intended to give you a running start at | getting the most out of your Maven installation. Where appropriate, the default | values (values used when the setting is not specified) are provided. | |-->
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Jun 19 15:06:01 GMT 2023 - 11K bytes - Viewed (0) -
maven-compat/src/main/resources/META-INF/maven/plugin-expressions/settings.paramdoc.xml
<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> <syntax>settings.interactiveMode</syntax>
XML - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 2K bytes - Viewed (0) -
guava-gwt/src/com/google/common/annotations/Annotations.gwt.xml
Our workaround is to tell GWT that util.concurrent and all other packages have prod supersource, even if they have none. GWT is happy to ignore us when we specify a nonexistent path. (I hope that this workaround does not cause its own problems in the future.) --> <super-source path="super"/> <inherits name="com.google.gwt.core.Core" /> <inherits name="com.google.gwt.user.User" />
XML - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Thu Jan 06 15:30:58 GMT 2022 - 1.3K bytes - Viewed (0)