You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/07/06 16:18:00 UTC
[jira] [Resolved] (SLING-10586) ArtifactManager getArtifactHandler
fails for remote repositories.
[ https://issues.apache.org/jira/browse/SLING-10586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus resolved SLING-10586.
-------------------------------------
Resolution: Fixed
> ArtifactManager getArtifactHandler fails for remote repositories.
> -----------------------------------------------------------------
>
> Key: SLING-10586
> URL: https://issues.apache.org/jira/browse/SLING-10586
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
> Affects Versions: Feature Model 1.2.26
> Reporter: Karl Pauls
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Feature Model 1.2.28
>
>
> After the migration to NIO, the ArtifactManager fails if repositories are configured (the default) that are not for the local disc (like e.g. maven central) and an artifact is not first found in a local repository.
> Looks like this:
> {noformat}
> #73 11.46 java.nio.file.FileSystemNotFoundException: Provider "https" not installed
> #73 11.46 at java.base/java.nio.file.Path.of(Unknown Source)
> #73 11.46 at java.base/java.nio.file.Paths.get(Unknown Source)
> #73 11.46 at org.apache.sling.feature.io.artifacts.ArtifactManager$DefaultArtifactHandler.getArtifact(ArtifactManager.java:383)
> #73 11.46 at org.apache.sling.feature.io.artifacts.ArtifactManager.getArtifactHandler(ArtifactManager.java:245)
> #73 11.46 at org.apache.sling.feature.launcher.impl.FeatureProcessor.createApplication(FeatureProcessor.java:143)
> #73 11.46 at org.apache.sling.feature.launcher.impl.Bootstrap.assemble(Bootstrap.java:208)
> #73 11.46 at org.apache.sling.feature.launcher.impl.Bootstrap.run(Bootstrap.java:123)
> #73 11.46 at org.apache.sling.feature.launcher.impl.Main.main(Main.java:402)
> {noformat}
> [~kwin], can you have a look and see if that is related to your NIO changes?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)