Add files via upload

[rajapandi1234]

Summary by CodeRabbit

• Documentation
  • Added comprehensive open-source license documentation for Apache 2.0, BSD-2-Clause, Eclipse Public License, LGPL, MIT, and Mozilla Public License.
  • Added third-party attribution notice documenting included dependencies and their respective licenses.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Added a comprehensive collection of open-source license files (Apache-2.0, BSD-2-Clause, EPL-1.0, LGPL-3.0-only, MIT, and MPL-2.0) to the licenses directory, along with a NOTICE file aggregating third-party component attributions and their corresponding licenses.

Changes

Cohort / File(s)	Summary
License Text Files licenses/Apache-2.0.txt, licenses/BSD-2-Clause.txt, licenses/EPL-1.0.txt, licenses/LGPL-3.0-only.txt, licenses/MIT.txt, licenses/MPL-2.0.txt	Added complete license text documents for six open-source licenses, including full terms, conditions, disclaimers, and any appendices as per each license's specifications.
License Attribution Notice licenses/NOTICE	Added aggregated license notice file documenting three third-party components (Project Lombok, JUnit 4, SonarQube Scanner for Maven) with version, copyright, and license references.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 Six licenses bundled with care,
BSD, MIT, Apache fair,
A notice of thanks for the tools we use,
Legal compliance—we can't lose!
Hops away with compliance in paw 🎉

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Add files via upload' is vague and generic, failing to convey the specific purpose of adding multiple license files to the project.	Replace with a more descriptive title like 'Add license files (Apache 2.0, BSD 2-Clause, EPL 1.0, LGPL 3.0, MIT, MPL 2.0)' or 'Add third-party license documentation and NOTICE file'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Mahesh-Binayak]

@CodeRabbit review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 4

Fix all issues with AI Agents 🤖

In @licenses/EPL-1.0.txt‎:
- Around line 1-73: EPL-1.0.txt is incomplete and diverges from the official
Eclipse Public License; replace the current EPL-1.0.txt contents with the
authoritative, complete EPL 1.0 text published by the Eclipse Foundation
(including all 15 sections such as TERMINATION, RESPONSIBILITY FOR CLAIMS,
NOTICES, COPYRIGHT, TRADEMARKS, and ASSIGNMENT), ensuring the exact canonical
wording and copyright/Agreement Steward notice are preserved; update the file
EPL-1.0.txt with that exact official text and verify the copied license matches
the Eclipse Foundation source verbatim.

In @licenses/LGPL-3.0-only.txt:
- Around line 1-304: The LGPL file differs from the canonical FSF text: replace
all occurrences of "http://fsf.org/" with "https://fsf.org/" and replace the
literal "(C) 2007 Free Software Foundation, Inc." with the copyright symbol form
"© 2007 Free Software Foundation, Inc." (i.e., change "(C)" to "©"), and ideally
overwrite the entire licenses/LGPL-3.0-only.txt content with the official FSF
LGPL-3.0 text from https://www.gnu.org/licenses/lgpl-3.0.en.html to ensure exact
canonical wording.

In @licenses/NOTICE:
- Around line 28-31: Update the copyright line for the JUnit entry by changing
the text "Copyright © 2002-2025" to the correct year (e.g., "Copyright ©
2002-2026") or replace it with the accurate release range for JUnit 4.12; locate
the JUnit block that begins with "JUnit 4 (junit:junit)" and modify the
Copyright line accordingly.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between db7e1c5 and 810a0ba.

📒 Files selected for processing (7)

• licenses/Apache-2.0.txt
• licenses/BSD-2-Clause.txt
• licenses/EPL-1.0.txt‎
• licenses/LGPL-3.0-only.txt
• licenses/MIT.txt
• licenses/MPL-2.0.txt
• licenses/NOTICE

🧰 Additional context used

🪛 LanguageTool

licenses/MPL-2.0.txt

[style] ~47-~47: Consider removing “of” to be more concise
Context: ...tial grant or subsequently, any and all of the rights conveyed by this License. 1.10....

(ALL_OF_THE)

---

[style] ~106-~106: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...te The licenses granted in Section 2.1 with respect to any Contribution become effective for e...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

---

[style] ~211-~211: As an alternative to the over-used intensifier ‘absolutely’, consider replacing this phrase.
Context: ...lf of any Contributor. You must make it absolutely clear that any such warranty, support, indemn...

(EN_WEAK_ADJECTIVE)

---

[style] ~223-~223: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...y with any of the terms of this License with respect to some or all of the Covered Software due...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

---

[style] ~241-~241: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...non-compliance by some reasonable means prior to 60 days after You have come back into c...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~246-~246: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...h Contributor, and You become compliant prior to 30 days after Your receipt of the notic...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~253-~253: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...tent, then the rights granted to You by any and all Contributors for the Covered Software u...

(EN_WORDINESS_PREMIUM_ANY_AND_ALL)

---

[style] ~258-~258: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...or Your distributors under this License prior to termination shall survive termination. ...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

licenses/LGPL-3.0-only.txt

[style] ~69-~69: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ished by the Free Software Foundation. If the Library as you received it specifie...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[style] ~84-~84: To make your writing flow more naturally, try moving ‘also’ before the verb.
Context: ...ic License for most of our software; it applies also to any other work released this way by ...

(ALSO_PLACEMENT)

---

[style] ~86-~86: Consider using only “Public” to avoid wordiness.
Context: ...re referring to freedom, not price. Our General Public Licenses are designed to make sure that...

(GENERAL_XX)

---

[style] ~145-~145: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...by exercising rights under this License with respect to the covered work, and you disclaim any ...

(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)

---

[style] ~176-~176: Consider using only “public” to avoid wordiness.
Context: ...ce of the work are being offered to the general public at no charge under subsection 6d. A se...

(GENERAL_XX)

---

[style] ~210-~210: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...survive such relicensing or conveying. If you add terms to a covered work in acco...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[style] ~218-~218: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ... the violation by some reasonable means prior to 60 days after the cessation. Moreover,...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~220-~220: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...ight holder, and you cure the violation prior to 30 days after your receipt of the notic...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~225-~225: Consider a more concise word here.
Context: ...are not required to accept this License in order to receive or run a copy of the Program. A...

(IN_ORDER_TO_PREMIUM)

---

[style] ~225-~225: To make your writing clearer, consider a shorter, more direct phrase.
Context: ...tion of a covered work occurring solely as a consequence of using peer-to-peer transmission to rece...

(AS_A_CONSEQUENCE_OF)

---

[style] ~237-~237: To make your writing clearer, consider a shorter, more direct phrase.
Context: ...ude claims that would be infringed only as a consequence of further modification of the contributor...

(AS_A_CONSEQUENCE_OF)

---

[uncategorized] ~247-~247: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...conveying the work, and under which the third party grants, to any of the parties who would...

(EN_COMPOUND_ADJECTIVE_INTERNAL)

---

[style] ~247-~247: ‘prior to’ might be wordy. Consider a shorter alternative.
Context: ...nt, or that patent license was granted, prior to 28 March 2007. Nothing in this License...

(EN_WORDINESS_PREMIUM_PRIOR_TO)

---

[style] ~252-~252: ‘So as to’ expresses purpose and is used in formal texts. Consider using “to”.
Context: ...se. If you cannot convey a covered work so as to satisfy simultaneously your obligations...

(SO_AS_TO)

---

[style] ~261-~261: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...ished by the Free Software Foundation. If the Program specifies that a proxy can ...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

---

[style] ~300-~300: This phrase is redundant (‘I’ stands for ‘interface’). Use simply “GUI”.
Context: ...am's commands might be different; for a GUI interface, you would use an “about box”. You sho...

(ACRONYM_TAUTOLOGY)

licenses/Apache-2.0.txt

[style] ~161-~161: ‘any and all’ might be wordy. Consider a shorter alternative.
Context: ...ge, computer failure or malfunction, or any and all other commercial damages or losse...

(EN_WORDINESS_PREMIUM_ANY_AND_ALL)

🔇 Additional comments (4)

licenses/BSD-2-Clause.txt (1)

1-9: ✓ License file properly added.

The BSD-2-Clause license text is correctly formatted and complete. Ensure this is being used to document a third-party dependency listed in your NOTICE or attribution file.

licenses/MIT.txt (1)

1-9: ✓ License file properly added.

The MIT license text is correctly formatted with Project Lombok copyright attribution (2009-2021). Verify that the NOTICE file documents Lombok's usage and links it to this license.

licenses/MPL-2.0.txt (1)

1-373: ✓ License file properly added.

The Mozilla Public License v2.0 is complete and properly formatted. The file reproduces the official license text without modifications, which is correct.

Note: Static analysis tools have flagged style/wordiness suggestions in this license text (e.g., "of the rights," "with respect to," "prior to"). These suggestions must be ignored — standard open-source license documents must remain in their official, unmodified form to preserve legal validity and compliance integrity.

Verify that the NOTICE file properly attributes which third-party dependencies are licensed under MPL-2.0.

licenses/Apache-2.0.txt (1)

1-200: Remove this comment — Apache-2.0 license correspondence is correct.

The Apache-2.0.txt license file is appropriately included. Multiple Apache 2.0 licensed dependencies are documented in the project's THIRD-PARTY-NOTICES file, including Spring Boot, Spring Security, Jackson, Reactor Core, SpringDoc OpenAPI, cache2k, JNA, Javassist, and others. No action needed.

Likely an incorrect or invalid review comment.