Skip to content

Comments

MCR-3609 MCRMODSCommands not found#2813

Open
rsteph-de wants to merge 2 commits into2025.12.xfrom
issues/MCR-3609-MODS_Commands_not_found
Open

MCR-3609 MCRMODSCommands not found#2813
rsteph-de wants to merge 2 commits into2025.12.xfrom
issues/MCR-3609-MODS_Commands_not_found

Conversation

@rsteph-de
Copy link
Member

Link to jira.

Pull Request Checklist (Author)

Please go through the following checklist before assigning the PR for review:

Ticket & Documentation

  • The issue in the ticket is clearly described and the solution is documented.
  • Design decisions (if any) are explained.
  • The ticket references the correct source and target branches.
  • The fixed-version is correctly set in the ticket and matches the PR's target branch (main).

Feature & Improvement Specific Checks

  • Instructions on how to test or use the feature are included or linked (e.g. to documentation).
  • For UI changes: before & after screenshots are attached.
  • New features or migrations are documented.
  • Does this change affect existing applications, data, or configurations?
    • NO - Yes: Is a migration required? If yes, describe it.
    • n.a. - Breaking change is marked in the commit message.

Bugfix-Specific Checks

  • Affected version is listed in the ticket.
  • Minimal code changes were made (no refactoring).
  • This PR truly fixes only the reported bug.
  • No breaking changes are introduced.
  • NO - A relevant test was added (if feasible).

Testing

  • I have tested the changes locally.
  • The feature behaves as described in the ticket.
  • Were existing tests modified?
    • NO - Yes: explain the changes for reviewers.

MCR Conventions & Metadata

  • MCR naming conventions are followed
  • If the public API has changed:
    • NO - Old API is deprecated or a migration is documented.
    • [X If not, no action needed.
  • Java license headers are added where necessary.
  • Javadoc is written for non-self-explanatory classes/methods (Clean Code).
  • All configuration options are documented in Javadoc and mycore.properties.
  • No default properties are hardcoded — all set via mycore.properties.

Multi-Repo Considerations

  • NO Is an equivalent PR in MIR required?
    • NO If yes, is it already created?

@rsteph-de rsteph-de requested a review from sebhofmann February 20, 2026 14:18
@rsteph-de rsteph-de changed the base branch from main to 2025.12.x February 20, 2026 14:19
@sebhofmann
Copy link
Member

sebhofmann commented Feb 20, 2026

Ich glaube das Verschieben nach classifcation war nicht von mir beabsichtigt. Vielleicht lieber wieder zurück schieben?

@rsteph-de
Copy link
Member Author

Vielleicht lieber wieder zurück schieben?
Das können wir auch so lösen. Ich konnte mich mit dem "neuen Ort" auch nicht anfreunden und dachte, Du hättest dir was dabei gedacht.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants