Skip to content

Some way not to rely on this maven library com.sun.activation? #1589

Description

@nddipiazza

When i migrated from 2.4.7 to 2.5.4 I noticed that the transitive dependency pulls incom.sun.activation.

This is not desirable as this causes errors with many libraries until you add an exclusion on com.sun.activation.

Can we shade this dependency?

Activity

  1. slandelle commented on Oct 20, 2018

    @slandelle
    Contributor

    I'm afraid that's neither possible nor desirable, see https://stackoverflow.com/questions/46493613/what-is-the-replacement-for-javax-activation-package-in-java-9.

    This is not desirable as this causes errors with many libraries

    What happens exactly? Have you reached out maintainers of those other libraries? Are they even maintained?

  2. nddipiazza commented on Oct 20, 2018

    @nddipiazza
    Author

    ahhh i see now. thanks for that link it educated me.

  3. slandelle commented on Oct 20, 2018

    @slandelle
    Contributor

    You're welcome :)

    Long story short: javax.activation packake shipped in JDK is going away and pulling com.sun.activation:javax.activation:1.2.0 is the proper long term way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions