- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 10 for show (0.12 sec)
-
apache-maven/src/assembly/maven/lib/jansi-native/README.txt
This directory contains Jansi native libraries extracted from Jansi JAR. You can add your own build for platforms not natively supported by Jansi. See here [1] on how to compile for your platform and here [2] how libraries follow Jansi's directory and filename conventions. [1] https://github.com/fusesource/jansi/tree/master/src/main/native
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 486 bytes - Viewed (0) -
.github/pull_request_template.md
Best practice is to use the JIRA issue title in both the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the [Core IT][core-its] successfully.
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Tue Dec 20 13:14:27 GMT 2022 - 1.9K bytes - Viewed (0) -
maven-core/src/site/apt/inheritance.apt
~~ under the License. ----- Inheritance in Maven ----- The Maven Team ----- Inheritance in Maven In order the understand how inheritance works in Maven there are a few notions that you must be familiar with: * The maven super model * how parent poms are processed * the order in which elements in the POM are overridden * minimum element-set for a valid project pom Maven super model
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Jul 18 17:22:19 GMT 2022 - 3.5K bytes - Viewed (0) -
maven-compat/src/site/apt/index.apt
{{{https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies} Plugin migration to Maven3 dependencies}}
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Tue Jan 24 22:50:10 GMT 2017 - 1.3K bytes - Viewed (0) -
maven-artifact/src/site/apt/index.apt
with its <<<DefaultArtifact>>> implementation ({{{./xref/org/apache/maven/artifact/DefaultArtifact.html}source}}). The jar file is executable and provides a little tool to display how Maven parses and compares versions: +----+ $ java -jar maven-artifact-*.jar 3.2.4-alpha-1 3.2.4-SNAPSHOT 3.2.4.0 Display parameters as parsed by Maven (in canonical form) and comparison result:
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sun Nov 30 20:57:07 GMT 2014 - 1.7K bytes - Viewed (0) -
maven-core/src/site/apt/artifact-handlers.apt
define for each {{{../maven-model/maven.html#class_dependency}dependency type}} information on the artifact (classifier, extension, language) and how to manage it as dependency (add to classpath, include dependencies). They are replaced in Maven 4 with Maven 4 API Core's {{{../api/maven-api-core/apidocs/org/apache/maven/api/Type.html}Dependency Types}},
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Apr 23 06:12:44 GMT 2024 - 4.6K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
+-----+ ${maven.home} | +--- maven.properties +-----+ * Group configuration As far as properties go for an entire build the maven.properties could be placed at the top of the group but I'm not really sure how this might work. There could probably also be a directory for plugins.xml and maven.properties. * Project configuration At the project level all configuration is achieved by tweaking the POM. One of the differences between
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 18 00:24:53 GMT 2024 - 5.8K bytes - Viewed (0) -
apache-maven/src/assembly/maven/lib/ext/hazelcast/README.txt
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Tue Aug 23 19:41:57 GMT 2022 - 300 bytes - Viewed (0) -
apache-maven/src/assembly/maven/lib/ext/redisson/README.txt
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Tue Aug 23 19:41:57 GMT 2022 - 295 bytes - Viewed (0) -
maven-core/src/site/apt/index.apt
This means for example that adding pluginA:goal2 to pre-existing (pluginA:goal1, pluginB:goal) will lead to (pluginA:goal1, pluginA:goal2, pluginB:goal) * see effective POM as shown by {{{/plugins/maven-help-plugin/effective-pom-mojo.html}<<<help:effective-pom>>>}} to see the effective plugins then goals order.
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Wed Jun 14 05:48:39 GMT 2023 - 5.3K bytes - Viewed (0)