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

Marek Novotny (Jira) issues at jboss.org
Fri May 22 15:31:08 EDT 2020


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

Marek Novotny commented on ELY-1971:
------------------------------------

and there is one hiccup in shaded, there is excluded wildfly-commons dependency so the wildcard exclusion will have possible issue with missing the wildfly-commons too.

> 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
>            Assignee: Darran Lofthouse
>            Priority: Major
>
> 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}
> which is just a hack for bad designed artifact IMHO.



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


More information about the jboss-jira mailing list