[
https://issues.redhat.com/browse/ELY-1971?page=com.atlassian.jira.plugin....
]
Darran Lofthouse commented on ELY-1971:
---------------------------------------
The wildfly-elytron artefact is really only an intermediate artefact kept around for
backwards compatibility as the project was split into individual modules but we kept the
original artefact around for situations that already depended upon it.
If anything which is not a part of the Elytron project is shaded into the jar then that is
in general a bug as it's only intent was to aggregate the WildFly Elytron classes into
a single jar.
We probably should also look at the exclusions as this artefact should not need the
Elytron artefacts a second time but I also expect this artefact to have a limited life and
be removed in the next major version. Instead of shaded jars we probably should instead
be looking at a small set of boms for some of the most common use cases.
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)