Uploaded image for project: 'WSS4J'
  1. WSS4J
  2. WSS-496

"tests" classifier artifacts dependencies should not have compile scope

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.0.0
    • WSS4J Core
    • None

    Description

      On trunk (2.0.0-SNAPSHOT), there're some maven artifacts which are built with "tests" classifier and look to be used for tests.
      Unfortunately, the ws-security-stax/pom.xml is not setting the scope for one of them (org.apache.wss4j:wss4j-ws-security-dom:tests), resulting in polluted transitive dependencies trees in any project that consumes Apache WSS4J.
      This is a problem for example because the CryptoFactory uses the classloader for resolving crypto properties and can hence end up reading from the test artifact while that has nothing to do with the final user application.

      Attachments

        Activity

          People

            coheigea Colm O hEigeartaigh
            asoldano Alessio Soldano
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: