Skip to content

[2143] Replace Path with String in library loading configuration#2144

Merged
AxelRICHARD merged 1 commit intomainfrom
fro/fix/library-loader
Apr 16, 2026
Merged

[2143] Replace Path with String in library loading configuration#2144
AxelRICHARD merged 1 commit intomainfrom
fro/fix/library-loader

Conversation

@frouene
Copy link
Copy Markdown
Contributor

@frouene frouene commented Apr 15, 2026

Bug: #2143

PLEASE READ ALL ITEMS AND CHECK ONLY RELEVANT CHECKBOXES BELOW

Auto review

  • Have you reviewed this PR? Please do a first quick review, It is very useful to detect typos and missing copyrights, check comments, check your code... The reviewer will thank you for that :)

Project management

  • Has the pull request been added to the relevant milestone?
  • Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
  • Have the relevant issues been added to the pull request?
  • Have the relevant labels been added to the issues? (area:, type:)
  • Have the relevant issues been added to the same project milestone as the pull request?

Changelog and release notes

  • Has the CHANGELOG.adoc + doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc been updated to reference the relevant issues?
  • Have the relevant API breaks been described in the CHANGELOG.adoc?
  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
  • In case of a change with a visual impact, are there any screenshots in the doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?
  • In case of a key change, has the change been added to Key highlights section in doc/content/modules/user-manual/pages/release-notes/YYYY.MM.0.adoc?

Documentation

  • Have you included an update of the documentation in your pull request? Please ask yourself if an update (installation manual, user manual, developer manual...) is needed and add one accordingly.

Tests

  • Is the code properly tested? Any pull request (fix, enhancement or new feature) should come with a test (or several). It could be unit tests, integration tests or cypress tests depending on the context. Only doc and releng pull request do not need for tests.

@frouene
Copy link
Copy Markdown
Contributor Author

frouene commented Apr 15, 2026

I'm not sure if we need to add an entry to the user manual, it doesn't seem like a change that would affect end users.

@AxelRICHARD
Copy link
Copy Markdown
Member

I'm not sure if we need to add an entry to the user manual, it doesn't seem like a change that would affect end users.

No we don't need to add an entry to the user manual.

@frouene frouene force-pushed the fro/fix/library-loader branch from a8d6527 to ed0c956 Compare April 15, 2026 12:30
Bug: #2143
Signed-off-by: Florian ROUËNÉ <florian.rouene@obeosoft.com>
@AxelRICHARD AxelRICHARD force-pushed the fro/fix/library-loader branch from ed0c956 to 90c21f6 Compare April 16, 2026 07:17
@AxelRICHARD AxelRICHARD merged commit 5a9f183 into main Apr 16, 2026
4 checks passed
@AxelRICHARD AxelRICHARD deleted the fro/fix/library-loader branch April 16, 2026 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Path objects are incompatible with classpath resource resolution on Windows

2 participants