Uploaded image for project: 'Seam 3 Distribution'
  1. Seam 3 Distribution
  2. SEAM-94

Shaded jars like seam-solder instead of seam-solder-api and seam-solder-impl result in the same classes twice in the classpath (possibly different versions)

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 3.1.0.Beta3
    • Component/s: None
    • Labels:
      None

      Description

      Shaded jars (like seam-solder) are highly problematic in itself, see WELD-935.

      Trying to avoid the shaded jars, is impossible, as this example shows:

      $ mvn dependency:tree
      ...
      [INFO] +- org.jboss.seam.solder:seam-solder-api:jar:3.0.0.Final:compile ===========> my compile dependency on solder-api (the non-shaded jar)
      [INFO] +- org.jboss.seam.solder:seam-solder-impl:jar:3.0.0.Final:runtime ==========> my runtime dependency on solder-impl (the non-shaded jar)
      [INFO] +- org.jboss.seam.security:seam-security-api:jar:3.0.0.Final:compile
      ...
      [INFO] +- org.jboss.seam.security:seam-security-impl:jar:3.0.0.Final:compile
      [INFO] |  +- org.jboss.seam.solder:seam-solder:jar:3.0.0.Final:compile ============> transitive dependency on solder (the shaded jar) which shades the classes of solder-api
      

      Now suppose I depend on solder-api 3.0.1.Final instead (still with seam-security-impl 3.0.0.Final): I 'd have 2 different versions of solder in my classpath.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  ge0ffrey Geoffrey De Smet
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: