flight-search-api source code

jdk_21_maven/cs/rest/flight-search-api/.gitattributes

@@ -0,0 +1,2 @@
+/mvnw text eol=lf
+*.cmd text eol=crlf

jdk_21_maven/cs/rest/flight-search-api/.gitignore

@@ -0,0 +1,36 @@
+HELP.md
+target/
+!.mvn/wrapper/maven-wrapper.jar
+!**/src/main/**/target/
+!**/src/test/**/target/
+
+### STS ###
+.apt_generated
+.classpath
+.factorypath
+.project
+.settings
+.springBeans
+.sts4-cache
+
+### IntelliJ IDEA ###
+.idea
+*.iws
+*.iml
+*.ipr
+
+### NetBeans ###
+/nbproject/private/
+/nbbuild/
+/dist/
+/nbdist/
+/.nb-gradle/
+build/
+!**/src/main/**/build/
+!**/src/test/**/build/
+
+### VS Code ###
+.vscode/
+
+### Environment file
+.env

jdk_21_maven/cs/rest/flight-search-api/CODEOWNERS

@@ -0,0 +1,2 @@
+# These owners will be the default owners for everything in the repo.
+* @Rapter1990 @furkantarikgocmen

jdk_21_maven/cs/rest/flight-search-api/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations

jdk_21_maven/cs/rest/flight-search-api/CONTRIBUTING.md

@@ -0,0 +1,182 @@
+# Contributing Guidelines
+
+Thank you for considering contributing to the "afet-yonetim-sistemi" project! We appreciate your interest and welcome
+any contributions that can help us improve the project.
+
+Please take a moment to review these guidelines before making any contributions. Following these guidelines will help
+you maintain a collaborative and inclusive environment for everyone involved.
+
+## Table of Contents
+
+- [How to Contribute](#how-to-contribute)
+- [Reporting Issues](#reporting-issues)
+- [Submitting Changes](#submitting-changes)
+- [Code Style](#code-style)
+- [Commit Messages](#commit-messages)
+- [Testing](#testing)
+- [Documentation](#documentation)
+- [Community Guidelines](#community-guidelines)
+
+## How to Contribute
+
+Thank you for considering contributing to our project! To make the process smooth, please follow these steps:
+
+1. **Fork the Repository:**
+
+    - Visit our [GitHub repository](https://github.com/EmreKiziltoprak/CRM_experiment) and fork it to your GitHub account.
+
+2. **Create a New Branch:**
+
+    - Create a branch for your contribution by referring to
+      the [Naming Conventions of Branches](#branch-naming-conventions) for guidance.
+    - Ensure your feature branch is associated with the corresponding GitHub issue from the 'Development' section in
+      each issue page.
+
+3. **Make Changes:**
+
+    - Implement your changes in the branch you created.
+    - Thoroughly test your changes to ensure they work as expected.
+
+4. **Commit Changes:**
+
+    - Commit your changes with clear and concise messages. Refer to the [Commit Messages](#commit-messages) section for
+      guidance.
+
+5. **Push Changes:**
+
+    - Push your changes to your forked repository.
+
+6. **Open a Pull Request (PR):**
+
+    - Open a PR against the `main` branch of the original repository by referring to
+      the [Pull Request Naming Conventions](#pull-request-naming-conventions) for guidance.
+    - Provide a detailed description of your changes in the PR.
+    - Link relevant issues or discussions in the PR description.
+    - Follow the pull request naming conventions outlined below.
+    - PR title should contain the issue/feature/bug number.
+
+7. **Review and Feedback:**
+    - Once your PR is submitted, project maintainers will review it and provide feedback.
+    - Be responsive to feedback and make necessary changes.
+
+## Development Standards
+
+Our project adheres to the [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow) for
+collaboration.
+Issues are managed on GitHub Discussions, with plans to transition them to Github.
+
+### Branch Naming Conventions:
+
+- `bugfix/{github-issue-number}/{optional-description}`
+- `development/{github-issue-number}/{optional-description}`
+- `refactor/{github-issue-number}/{optional-description}`
+- `hotfix/{github-issue-number}/{optional-description}`
+
+> Example : `development/1/add-feature-to-handle-user-authentication`
+
+### Pull Request Naming Conventions:
+
+- `#{github-issue-number} | {header-for-summary-of-development}`
+
+> Example : `#PR 1 | Add feature to handle user authentication`
+
+Here are some additional standards to keep in mind:
+
+- Link your feature branch to the corresponding GitHub issue.
+- `main` branch is protected.
+- PR should be linked to the relevant issue within the GitHub Project.
+- Only one code owner's approval is needed for merging feature branches.
+- PR should be squash-merged to avoid merge commit history.
+- PR should pass build and necessary tests before merging.
+- Releases should be tagged with a version.
+- Commit messages should be subjectless.
+- Resolve comments within the PR by the commenter.
+- PR should be concise and address one thing.
+- Avoid including secret/credential information.
+- Code should comply with existing coding standards; no new standards should be introduced without justification.
+
+## Reporting Issues
+
+If you encounter any bugs, have feature requests, or want to provide general feedback, please feel free to open a
+discussion
+in the "CRM_experiment" repository. When creating a discussion, please provide as much detail as possible,
+including:
+
+- A clear and descriptive title
+- Steps to reproduce the issue
+- Expected behavior
+- Actual behavior
+- Any error messages or logs
+
+## Submitting Changes
+
+When submitting changes, please ensure the following:
+
+- Your code adheres to the project's [code style guidelines](#code-style).
+- You have added appropriate tests for your changes (see [Testing](#testing)).
+- The documentation has been updated, if necessary (see [Documentation](#documentation)).
+- Your commits are clean and have clear commit messages (see [Commit Messages](#commit-messages)).
+
+## Code Style
+
+To maintain a consistent codebase, please follow the existing code style used in the project. If necessary, refer to any
+code style guidelines mentioned in the repository.
+
+## Commit Messages
+
+Writing clear and descriptive commit messages is essential for the maintainability of the project. Follow these
+guidelines when writing commit messages:
+
+- Limit the subject line to 50 characters.
+- Begin the subject line with a verb in the present tense (e.g., "Fix," "Add," "Update").
+- Use the imperative mood (e.g., "Fix bug" instead of "Fixed bug").
+- Provide additional details in the commit message body if necessary. Explain why the change was made and any relevant
+  information for reviewers.
+
+Example:
+
+```
+Add feature to handle user authentication
+
+- Implemented a new module for user authentication
+- Updated existing login page UI
+- Added new API endpoint for user registration
+```
+
+## Testing
+
+If you are contributing code changes, it is important to include appropriate tests to ensure the stability and
+functionality of the project. Follow these guidelines when writing tests:
+
+- Write tests that cover the new code you have added or modified.
+- Ensure your tests are easy to understand and maintain.
+- Run the existing test suite before submitting your changes to make sure they haven't introduced any regressions.
+- Provide instructions on how to run the tests if they require additional setup or specific commands.
+
+## Documentation
+
+Clear and up-to-date documentation is crucial for the project's users and contributors. If your contribution introduces
+new features, modifies existing functionality, or requires changes to the documentation, please make the necessary
+updates.
+
+Follow these guidelines for documenting your changes:
+
+- Update the relevant documentation files to reflect your changes.
+- Write clear and concise explanations.
+- Use code examples or screenshots, if appropriate, to enhance understanding.
+- Proofread your documentation to ensure it is accurate and free of errors.
+
+## Community Guidelines
+
+In addition to the technical aspects, it is important to follow the community guidelines to maintain a positive and
+inclusive environment for all contributors.
+
+- Be respectful and considerate of others' opinions and ideas.
+- Be open to feedback and willing to collaborate with other contributors.
+- Avoid personal attacks, offensive language, and harassment.
+- If you notice any inappropriate behavior, report it to the project maintainers.
+
+By adhering to these guidelines, we can work together to build a welcoming and productive community.
+
+Thank you for your interest in contributing to the "CRM_experiment" project! We appreciate your support and look
+forward to your contributions.

jdk_21_maven/cs/rest/flight-search-api/Dockerfile

@@ -0,0 +1,27 @@
+# Stage 1: Build stage
+FROM maven:3.9.7-amazoncorretto-21 AS build
+
+# Copy Maven files for dependency resolution
+COPY pom.xml ./
+COPY .mvn .mvn
+
+# Copy application source code
+COPY src src
+
+# Build the project and create the executable JAR
+RUN mvn clean install -DskipTests
+
+# Stage 2: Run stage
+FROM amazoncorretto:21
+
+# Set working directory
+WORKDIR flightsearchapi
+
+# Copy the JAR file from the build stage
+COPY --from=build target/*.jar flightsearchapi.jar
+
+# Expose port 1133
+EXPOSE 1133
+
+# Set the entrypoint command for running the application
+ENTRYPOINT ["java", "-jar", "flightsearchapi.jar"]