[jboss-jira] [JBoss JIRA] (ELY-1971) Bad designed wildlfy-elytron jar, shaded jar with dependencies

[Darran Lofthouse (Jira)]

    [ https://issues.redhat.com/browse/ELY-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14114996#comment-14114996 ] 

Darran Lofthouse commented on ELY-1971:
---------------------------------------

The boms don't yet exist but that is certainly the next stage we need to be looking into, after splitting the project into it's separate modules we still had some awkward inter dependencies which are not almost all cleaned up for WildFly Elytron 2.0 so that is where we need to define them.

> Bad designed wildlfy-elytron jar, shaded jar with dependencies
> --------------------------------------------------------------
>
>                 Key: ELY-1971
>                 URL: https://issues.redhat.com/browse/ELY-1971
>             Project: WildFly Elytron
>          Issue Type: Bug
>            Reporter: Marek Novotny
>            Priority: Minor
>
> Wildfly-elytron jar is shaded with all wildfly elytron modules + jboss-logging, but it keeps the shaded classes in jar in its dependency chain which makes duplicated classes in dependency tree when using the wildfly-elytron in maven project.
> Avoiding duplicates would effectively need to add exclusion dependency to wildfly-elytron like:
> {noformat}
> <dependency>
>     <groupId>org.wildlfy.security</groupId>
>     <artifactId>wildfly-elytron</artifactId>
>     <version>some-version</version>
>     <exclusions>
>         <exclusion>
>             <groupId>*</groupId>
>             <artifactId>*</artifactId>
>         </exclusion>
>     </exclusions>
> </dependency>
> {noformat}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)