JAkutenshi opened a new pull request, #4408: URL: https://github.com/apache/ignite-3/pull/4408
JIRA Ticket: [IGNITE-23221](https://issues.apache.org/jira/browse/IGNITE-23221) ## The goal The main goal is to remove obsolete links on Apache Ignite documentation website. ## The reason We should use proper up-to-date documentation warning messages for our users. ## The solution The only place that contains a link with the noticed prefix https://apacheignite.readme.io/ is JAVA_VER_WARN variable that is used for user's notification about Java version specific startup parameters. But for now we're supporting only Java 11+, so at most the message is obsolete and we should to inform a user about proper JVM's startup parameters with a link on a proper documentation about Ignite startup but 3.0.0-beta version until release: https://ignite.apache.org/docs/3.0.0-beta/quick-start/getting-started-guide Also the constant itself was renamed accordingly. --- Thank you for submitting the pull request. To streamline the review process of the patch and ensure better code quality we ask both an author and a reviewer to verify the following: ### The Review Checklist - [ ] **Formal criteria:** TC status, codestyle, mandatory documentation. Also make sure to complete the following: \- There is a single JIRA ticket related to the pull request. \- The web-link to the pull request is attached to the JIRA ticket. \- The JIRA ticket has the Patch Available state. \- The description of the JIRA ticket explains WHAT was made, WHY and HOW. \- The pull request title is treated as the final commit message. The following pattern must be used: IGNITE-XXXX Change summary where XXXX - number of JIRA issue. - [ ] **Design:** new code conforms with the design principles of the components it is added to. - [ ] **Patch quality:** patch cannot be split into smaller pieces, its size must be reasonable. - [ ] **Code quality:** code is clean and readable, necessary developer documentation is added if needed. - [ ] **Tests code quality:** test set covers positive/negative scenarios, happy/edge cases. Tests are effective in terms of execution time and resources. ### Notes - [Apache Ignite Coding Guidelines](https://cwiki.apache.org/confluence/display/IGNITE/Java+Code+Style+Guide) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@ignite.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
