[
https://issues.apache.org/jira/browse/FINERACT-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17098597#comment-17098597
]
Michael Vorburger commented on FINERACT-919:
--------------------------------------------
Tip for anyone reading this due to hitting test failures in
the`ClasspathHellDuplicatesCheckRuleTest` which was introduced here (via
https://github.com/apache/fineract/pull/803/files): If that test fails, then it
means that your PR adds new or changes existing dependencies which will cause
duplicates on the classpath (which are a Bad Thing). You can easily see those
dupes if you run the`ClasspathHellDuplicatesCheckRuleTest` (locally). Also, run
{{./gradlew dependencies}} to understand what's coming from where.
> Detect, and fix, duplicate classes from similar JARs on the Fineract classpath
> ------------------------------------------------------------------------------
>
> Key: FINERACT-919
> URL: https://issues.apache.org/jira/browse/FINERACT-919
> Project: Apache Fineract
> Issue Type: New Feature
> Reporter: Michael Vorburger
> Assignee: Michael Vorburger
> Priority: Major
> Fix For: 1.4.0
>
>
> https://github.com/apache/fineract/pull/601/ proposed to detect, and fix,
> duplicate classes from similar JARs on the Fineract classpath. This should
> help to avoid weird problems.
> Alternatives achieving similar goals to the classes I will propose would be:
> * https://portingle.github.io/classpathHell/
> *
> https://plugins.gradle.org/plugin/net.idlestate.gradle-duplicate-classes-check
> * https://plugins.gradle.org/plugin/com.mobilesolutionworks.gradle.jacoco
> *
> https://plugins.gradle.org/plugin/io.fuchs.gradle.classpath-collision-detector
> *
> https://github.com/nebula-plugins/gradle-lint-plugin/wiki/Duplicate-Classes-Rule
> See also e.g.
> https://stackoverflow.com/questions/30648172/gradle-library-duplicates-in-dependencies
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
