- Sort Score
- Result 10 results
- Languages All
Results 1 - 6 of 6 for Messages (0.22 sec)
-
CONTRIBUTING.md
If you feel the source code should be reformatted, create a separate PR for this change. + Check for unnecessary whitespace with `git diff --check` before committing. + Make sure your commit messages are in the proper format. Your commit message should contain the key of the JIRA issue. ``` [MNG-XXX] - Subject of the JIRA Ticket Optional supplemental description. ```
Plain Text - Registered: Sun May 05 03:35:11 GMT 2024 - Last Modified: Sun Oct 10 09:48:27 GMT 2021 - 4.7K bytes - Viewed (0) -
maven-core/src/site/apt/offline-mode.apt
a debug message. * If the wagon is bound to "file://" then: Retrieve the file or base-url file to be "downloaded". * If the file (or more usefully, the base-url file) exists, proceed. * If the file (or base-url file) doesn't exist, assume that this location is part of a file-share. Ignore the request and print a debug message as above.
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 18 00:24:53 GMT 2024 - 10.6K bytes - Viewed (0) -
maven-core/src/site/apt/index.apt
with its <<<DefaultExceptionHandler>>> implementation ({{{./xref/org/apache/maven/exception/DefaultExceptionHandler.html}source}}), use to transform exception into useful end-user messages. * Toolchains * {{{./toolchains.html}Toolchains descriptor reference}},
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) -
.github/pull_request_template.md
where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue. - [ ] Also format the first line of the commit message like `[MNG-XXX] SUMMARY`. 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.
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/test/resources/apiv4-repo/junit/junit/4.13.1/junit-4.13.1.pom
<message>Current JDK version ${java.version} should be ${jdkVersion}, or higher! </message> <version>${jdkVersion}</version> </requireJavaVersion> <requireNoRepositories>
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Dec 19 19:08:55 GMT 2023 - 24.5K bytes - Viewed (0) -
README.md
development for Lucene and Solr is happening in each project's git repository now: - Lucene: <https://gitbox.apache.org/repos/asf/lucene.git> - Solr: <https://gitbox.apache.org/repos/asf/solr.git> If you're seeing this message then switch the development to 'main': git checkout main Development for branch 8x remains in the shared repository: - https://gitbox.apache.org/repos/asf/lucene-solr.git ## GitHub forks?
Plain Text - Registered: Wed May 08 00:11:12 GMT 2024 - Last Modified: Wed Mar 10 10:02:23 GMT 2021 - 1.5K bytes - Viewed (0)