joerghoh commented on PR #24: URL: https://github.com/apache/sling-org-apache-sling-feature-extension-apiregions/pull/24#issuecomment-6077649587
That does not really help, as this PR starts too high in the stack; at that point it's unclear if there as a network issue (timeout), and authentication problem or if the artifact does not exist. But we need these details for diagnosis, and I think this information as part of an exception message is already good enough. For that ``org.apache.sling.feature.io.artifacts.ArtifactManager.getArtifactHandler`` (where the current exception is thrown) also too high in the stack, as ``ArtifactManager.getArtifact()`` can only return a URL (or null), but neither throw an exception or an otherwise structured response (record/object) to better describe the problem. That means, we would need to change the interface of the ``ArtifactProvider`` and introduce a new method ``@NotNull URL getArtifact2(final String url, Stirng relativeCachePath) throws IOException``(better names welcome), which will never return null, but in case of problems throw an ``IOException``. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
