You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@metamodel.apache.org by "Kasper Sørensen (JIRA)" <ji...@apache.org> on 2015/10/01 13:56:26 UTC

[jira] [Created] (METAMODEL-191) Clean up dependency overlaps/conflicts

Kasper Sørensen created METAMODEL-191:
-----------------------------------------

             Summary: Clean up dependency overlaps/conflicts
                 Key: METAMODEL-191
                 URL: https://issues.apache.org/jira/browse/METAMODEL-191
             Project: Apache MetaModel
          Issue Type: Improvement
            Reporter: Kasper Sørensen


In another project I've just started using the Maven plugin by JBoss called "tattletale". It allows us to detect when any class is represented in multiple JAR files in our build. This was extremely useful for us to clean up some of the complex dependencies that we have and that sometimes are in conflict with one another.

I suggest to do the same in MetaModel as I could see some of the conflicts originated from here. For instance using older versions of commons-beanutils together with commons-collections. Or using apache-log4j-extras but relying on slf4j for logging.

In MetaModel we can apply the tattletale plugin in the "full" module and apply it to the "target/lib" folder. Should be very easy and beneficial.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)