metamodel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (METAMODEL-191) Clean up dependency overlaps/conflicts
Date Fri, 02 Oct 2015 08:45:27 GMT

    [ https://issues.apache.org/jira/browse/METAMODEL-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14940914#comment-14940914
] 

ASF GitHub Bot commented on METAMODEL-191:
------------------------------------------

Github user kaspersorensen commented on the pull request:

    https://github.com/apache/metamodel/pull/51#issuecomment-144961462
  
    OK I believe that this fixes it all. But let's see Travis validate that first :-)


> 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)

Mime
View raw message