[
https://jira.codehaus.org/browse/MOJO-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282905#comment-282905
]
Robert Scholte commented on MOJO-1773:
--------------------------------------
I don't think we should add such an option, especially not as a boolean.
IMO such usecases should be resolved by the exclusion of the superset
dependency.
for example:
{code:xml}
<dependency>
<groupId>org.twitter4j</groupId>
<artifactId>twitter4j-stream</artifactId>
<version>2.2.5</version>
<exclusions>
<exclusion>
<groupId>org.springframework</groupId>
<artifactId>spring</artifactId>
</exclusion>
</exclusions>
</dependency>
{code}
With Maven there's no reason to use the superset. Such projects should be
encouraged to do so.
> BanDuplicateClasses should have option to allow identical duplicates
> --------------------------------------------------------------------
>
> Key: MOJO-1773
> URL: https://jira.codehaus.org/browse/MOJO-1773
> Project: Mojo
> Issue Type: Bug
> Components: extra-enforcer-rules
> Affects Versions: extra-enforcer-rules-1.0-alpha-2
> Reporter: Ian Robertson
>
> An unfortunate trend in some projects is to have two versions of a module,
> one marked -core, and one marked -all. The -all module is a strict superset
> of the -core. I would like to add an option that would allow byte-for-byte
> identical duplicates if none of the packages in questio are sealed. To
> minimize overhead, sameness checks would be performed only after duplicates
> were detected.
> I would propose that the property name be:
> private boolean allowIdenticalyDuplicates
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
