Done
Details
Assignee
UnassignedUnassignedReporter
Julian LadischJulian LadischPriority
TBDDevelopment Team
SpitfireFix versions
Release
Orchid (R1 2023)RCA Group
Implementation coding issueTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter
Julian Ladisch
Julian LadischPriority
Development Team
Spitfire
Fix versions
Release
Orchid (R1 2023)
RCA Group
Implementation coding issue
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 13, 2023 at 11:09 AM
Updated February 14, 2023 at 9:21 PM
Resolved February 14, 2023 at 5:04 PM
folio-custom-fields ships with ModuleName.java that contains the module name "folio_custom_fields".
mod-users has it's own ModuleName.java with module name mod_users.
Which one is used depends on the order the jar files are returned by the file system.
When running in my IDE sometimes mod-users has the wrong one.
folio-custom-fields is a library that doesn't have a module name and therefore it's a bug that it ships with ModuleName.