Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8215991

Stop hiding exception from ArtifactResolver failures in tests

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Fixed
    • P4
    • 13
    • 13
    • infrastructure
    • None
    • b03

    Description

      In the test lib, we have an ArtifactResolver which is used by tests that need external resources. Internally at Oracle we hook Jib into this to provide such dependencies. For other users, it's possible to specify the path to such a dependency using a system property.

      If something goes wrong while resolving the dependencies, the ArtifactResolver currently swallows the exception and falls back on the default property based resolver, making it hard to figure out the problem.

      If the user provided the environment for calling Jib, I don't think we should try to revert to the default resolver on exception, but instead the exception should be propagated to the test.

      Attachments

        Activity

          People

            erikj Erik Joelsson
            erikj Erik Joelsson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: