You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The project currently includes both mockito-core and mockito-inline dependencies. However, recent versions of mockito-core now include support for inline mocking, making the mockito-inline dependency redundant. This issue proposes removing mockito-inline to clean up dependencies and reduce unnecessary library inclusion.
Reasons to Remove mockito-inline:
Redundant Dependency:
Inline mocking capabilities are now built directly into mockito-core, meaning mockito-inline no longer provides additional functionality. Maintaining both dependencies does not add any unique value and effectively makes mockito-inline a no-op in the current setup.
Simplified Dependency Management:
By removing mockito-inline, the dependency list becomes cleaner, making it easier to manage and understand the project’s dependencies. Simplified dependencies also make it easier for future contributors to understand the setup without questioning redundant inclusions.
Reduced Risk of Compatibility Issues:
Having only the necessary dependencies reduces the risk of conflicts or unexpected behavior due to redundant or unnecessary libraries. This is especially helpful when upgrading dependencies, as it limits potential issues to a single source.
Smaller Build and Faster Compilation:
Removing unused dependencies can marginally reduce the build size and may improve build times, especially in larger projects. While the impact may be small, it’s beneficial for optimizing the build process.
Alignment with Best Practices:
Avoiding unnecessary dependencies aligns with best practices in dependency management, making the project more maintainable, easier to audit, and less prone to dependency-related issues.
Additional Considerations:
To implement this change, mockito-inline should be removed from the dependency configuration. It’s advisable to run the tests after this change to verify that there are no unintended side effects or issues with inline mocking.
The text was updated successfully, but these errors were encountered:
Description:
The project currently includes both
mockito-core
andmockito-inline
dependencies. However, recent versions ofmockito-core
now include support for inline mocking, making themockito-inline
dependency redundant. This issue proposes removingmockito-inline
to clean up dependencies and reduce unnecessary library inclusion.Reasons to Remove
mockito-inline
:Redundant Dependency:
mockito-core
, meaningmockito-inline
no longer provides additional functionality. Maintaining both dependencies does not add any unique value and effectively makesmockito-inline
a no-op in the current setup.Simplified Dependency Management:
mockito-inline
, the dependency list becomes cleaner, making it easier to manage and understand the project’s dependencies. Simplified dependencies also make it easier for future contributors to understand the setup without questioning redundant inclusions.Reduced Risk of Compatibility Issues:
Smaller Build and Faster Compilation:
Alignment with Best Practices:
Additional Considerations:
To implement this change,
mockito-inline
should be removed from the dependency configuration. It’s advisable to run the tests after this change to verify that there are no unintended side effects or issues with inline mocking.The text was updated successfully, but these errors were encountered: