From 4afa24f9047c528ab191ca07b53ff77704c8ae9d Mon Sep 17 00:00:00 2001 From: "James R. Perkins" Date: Thu, 22 Jan 2026 19:00:24 -0800 Subject: [PATCH] Remove unneeded files and files that are provided by the .github repository. Signed-off-by: James R. Perkins --- CODEOWNERS | 1 - CONTRIBUTING.adoc | 68 ----------------------------------------------- security.txt | 13 --------- 3 files changed, 82 deletions(-) delete mode 100644 CODEOWNERS delete mode 100644 CONTRIBUTING.adoc delete mode 100644 security.txt diff --git a/CODEOWNERS b/CODEOWNERS deleted file mode 100644 index 3b582b2e..00000000 --- a/CODEOWNERS +++ /dev/null @@ -1 +0,0 @@ -* @committers \ No newline at end of file diff --git a/CONTRIBUTING.adoc b/CONTRIBUTING.adoc deleted file mode 100644 index 4a053655..00000000 --- a/CONTRIBUTING.adoc +++ /dev/null @@ -1,68 +0,0 @@ -:toc: - -= Contributing Guide - -Want to contribute to the RESTEasy Examples? We try to make it easy, and all contributions, even the smaller ones, -are more than welcome. This includes bug reports, fixes, documentation, etc. First though, please read this page -(including the small print at the end). - -== Legal - -All original contributions to RESTEasy Examples are licensed under the -https://www.apache.org/licenses/LICENSE-2.0[ASL - Apache License], -version 2.0 or later, or, if another license is specified as governing the file or directory being -modified, such other license. - -All contributions are subject to the https://developercertificate.org/[Developer Certificate of Origin (DCO)]. -The DCO text is also included verbatim in the [dco.txt](dco.txt) file in the root directory of the repository. - -== Reporting an issue - -This project uses GitHub issues to manage the issues. Open an issue directly in GitHub. - -If you believe you found a bug, and it's likely possible, please indicate a way to reproduce it, what you are seeing and -what you would expect to see. - -== Before you contribute - -To contribute, use GitHub Pull Requests, from your **own** fork. - -Also, make sure you have set up your Git authorship correctly: - ----- -git config --global user.name "Your Full Name" -git config --global user.email your.email@example.com ----- - -If you use different computers to contribute, please make sure the name is the same on all your computers. - -We use this information to acknowledge your contributions in release announcements. - -== Setup - -If you have not done so on this machine, you need to: - -* Install Git and configure your GitHub access -* Install Java SDK 11+ (OpenJDK recommended) - -=== IDE Config and Code Style - -RESTEasy has a strictly enforced code style. Code formatting is done by the Eclipse code formatter, using the config files -found in the https://github.com/resteasy/resteasy-dev-tools/tree/main/ide-config/src/main/resources[eclipse-code-formatter.xml] -file. By default, when you run `./mvnw install`, the code will be formatted automatically. -When submitting a pull request the CI build will fail if running the formatter results in any code changes, so it is -recommended that you always run a full Maven build before submitting a pull request. - -If you want to run the formatting without doing a full build, you can run `./mvnw process-sources`. - -==== Eclipse Setup - -Open the *Preferences* window, and then navigate to _Java_ -> _Code Style_ -> _Formatter_. Click _Import_ and then -select the `eclipse-code-formatter.xml` downloaded from the above link or clone the repository and navigate to the file. - -Next navigate to _Java_ -> _Code Style_ -> _Organize Imports_. Click _Import_ and select the `eclipse.importorder` file. - -==== IDEA Setup - -Install the https://plugins.jetbrains.com/plugin/6546-adapter-for-eclipse-code-formatter/[Adapter for Eclipse Code Formatter]. -See the https://github.com/krasa/EclipseCodeFormatter#instructions[documentation] on how to configure the plugin. \ No newline at end of file diff --git a/security.txt b/security.txt deleted file mode 100644 index 0c146a97..00000000 --- a/security.txt +++ /dev/null @@ -1,13 +0,0 @@ -# Security Policy - -## Security Contacts and Procedures - -The RESTEasy community takes security very seriously, and we aim to take immediate action to address serious -security-related problems that involve our products or services. - -Please report any suspected security vulnerability in this project to Red Hat Product Security at secalert@redhat.com. -You can use our GPG key to communicate with us securely. - -To report an issue in any Red Hat branded website or online service, please contact Red Hat Information Security at -site-security@redhat.com. -https://access.redhat.com/security/team/contact