[jira] [Commented] (MNG-714) When artifact not found on mirror the real site isn't checked
[ https://issues.apache.org/jira/browse/MNG-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16683001#comment-16683001 ] Igor Dvorzhak commented on MNG-714: --- Why this issue is closed? Was something done to address failover to mirrored repository if mirror not accessible or artifact is not present in mirror. Looks like this is a must have feature taking into account that "mirroring the entire central repository is not allowed": https://maven.apache.org/guides/mini/guide-mirror-settings.html > When artifact not found on mirror the real site isn't checked > - > > Key: MNG-714 > URL: https://issues.apache.org/jira/browse/MNG-714 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.0-beta-1 >Reporter: Kenney Westerhof >Assignee: Jason van Zyl >Priority: Major > Attachments: MNG-714-maven-artifact-manager.patch > > Original Estimate: 3h > Remaining Estimate: 3h > > I'm using the settings.xml mirror feature as a local cache. Periodically I > upload my local repo > to the webserver specified as mirror. > When an artifact cannot be found on the mirror, the original site isn't > checked (and possibly the rest of the sites). > I'm not sure what the exact function of the mirror is (except caching?), but > repo1 is checked often regardless > of mirror presence, so I figure it's not meant to totally disable checking > the central repo's. > Simple reproduction: define a few mirrors in your settings.xml for central, > central-plugins and snapshots, pointing to > say file://tmp/empty/dir/. > Stacktrace: > [DEBUG] Error resolving artifact version from metadata. > org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate > resource in repository > at > org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:81) > at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:70) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:343) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:263) > at > org.apache.maven.artifact.metadata.AbstractVersionArtifactMetadata.retrieveFromRemoteRepository(AbstractVersionArtifactMetadata.java:93) > at > org.apache.maven.artifact.transform.AbstractVersionTransformation.retrieveFromRemoteRepository(AbstractVersionTransformation.java:171) > at > org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:96) > at > org.apache.maven.artifact.transform.SnapshotTransformation.transformForResolve(SnapshotTransformation.java:43) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:95) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63) > at > org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:290) > at > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:274) > at > org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:81) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:186) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:70) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:197) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:185) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:156) > at > org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComplete(DefaultPluginManager.java:544) > at > org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:479) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:334) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:378) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:351) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:337) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:229) >
[jira] Commented: (MNG-714) When artifact not found on mirror the real site isn't checked
[ http://jira.codehaus.org/browse/MNG-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=242062#action_242062 ] John Bäckstrand commented on MNG-714: - Is there any more long-winded explanation this is not fixed? How exactly would this break repository managers? -some folks from my company have to change the settings file every time they go home because at home they don't have proxy. Quite annoying... is my exact situation, too. When artifact not found on mirror the real site isn't checked - Key: MNG-714 URL: http://jira.codehaus.org/browse/MNG-714 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0-beta-1 Reporter: Kenney Westerhof Assignee: Jason van Zyl Attachments: MNG-714-maven-artifact-manager.patch Original Estimate: 3 hours Remaining Estimate: 3 hours I'm using the settings.xml mirror feature as a local cache. Periodically I upload my local repo to the webserver specified as mirror. When an artifact cannot be found on the mirror, the original site isn't checked (and possibly the rest of the sites). I'm not sure what the exact function of the mirror is (except caching?), but repo1 is checked often regardless of mirror presence, so I figure it's not meant to totally disable checking the central repo's. Simple reproduction: define a few mirrors in your settings.xml for central, central-plugins and snapshots, pointing to say file://tmp/empty/dir/. Stacktrace: [DEBUG] Error resolving artifact version from metadata. org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate resource in repository at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:81) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:70) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:343) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:263) at org.apache.maven.artifact.metadata.AbstractVersionArtifactMetadata.retrieveFromRemoteRepository(AbstractVersionArtifactMetadata.java:93) at org.apache.maven.artifact.transform.AbstractVersionTransformation.retrieveFromRemoteRepository(AbstractVersionTransformation.java:171) at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:96) at org.apache.maven.artifact.transform.SnapshotTransformation.transformForResolve(SnapshotTransformation.java:43) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:95) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:290) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:274) at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:81) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:186) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:70) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:197) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:185) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:156) at org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComplete(DefaultPluginManager.java:544) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:479) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:334) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:378) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:351) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:337) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:229) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:123) at
[jira] Commented: (MNG-714) When artifact not found on mirror the real site isn't checked
[ http://jira.codehaus.org/browse/MNG-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=204357#action_204357 ] Jason van Zyl commented on MNG-714: --- The real mirror is not checked on purpose. The way repository managers work these days would break severely if we started doing this. When artifact not found on mirror the real site isn't checked - Key: MNG-714 URL: http://jira.codehaus.org/browse/MNG-714 Project: Maven 2 3 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0-beta-1 Reporter: Kenney Westerhof Assignee: Jason van Zyl Attachments: MNG-714-maven-artifact-manager.patch Original Estimate: 3 hours Remaining Estimate: 3 hours I'm using the settings.xml mirror feature as a local cache. Periodically I upload my local repo to the webserver specified as mirror. When an artifact cannot be found on the mirror, the original site isn't checked (and possibly the rest of the sites). I'm not sure what the exact function of the mirror is (except caching?), but repo1 is checked often regardless of mirror presence, so I figure it's not meant to totally disable checking the central repo's. Simple reproduction: define a few mirrors in your settings.xml for central, central-plugins and snapshots, pointing to say file://tmp/empty/dir/. Stacktrace: [DEBUG] Error resolving artifact version from metadata. org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate resource in repository at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:81) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:70) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:343) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:263) at org.apache.maven.artifact.metadata.AbstractVersionArtifactMetadata.retrieveFromRemoteRepository(AbstractVersionArtifactMetadata.java:93) at org.apache.maven.artifact.transform.AbstractVersionTransformation.retrieveFromRemoteRepository(AbstractVersionTransformation.java:171) at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:96) at org.apache.maven.artifact.transform.SnapshotTransformation.transformForResolve(SnapshotTransformation.java:43) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:95) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:290) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:274) at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:81) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:186) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:70) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:197) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:185) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:156) at org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComplete(DefaultPluginManager.java:544) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:479) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:334) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:378) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:351) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:337) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:229) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:123) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:209) at org.apache.maven.cli.MavenCli.main(MavenCli.java:267) at
[jira] Commented: (MNG-714) When artifact not found on mirror the real site isn't checked
[ http://jira.codehaus.org/browse/MNG-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158471#action_158471 ] Szczepan Faber commented on MNG-714: There are number reasons this is a valuable feature: -ability to implement simple fail-over system with two mirrors mirroring the same repo(s) -currently, if there are mirrors with the same value of mirrorOf, last mirror wins and previous mirrors are silently ignored. Not very nice... -some folks from my company have to change the settings file every time they go home because at home they don't have proxy. Quite annoying... Is it going to be released into maven? Is improving maven in the agenda of maven roadmap? When artifact not found on mirror the real site isn't checked - Key: MNG-714 URL: http://jira.codehaus.org/browse/MNG-714 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0-beta-1 Reporter: Kenney Westerhof Assignee: Jason van Zyl Fix For: 3.x Attachments: MNG-714-maven-artifact-manager.patch Original Estimate: 3 hours Remaining Estimate: 3 hours I'm using the settings.xml mirror feature as a local cache. Periodically I upload my local repo to the webserver specified as mirror. When an artifact cannot be found on the mirror, the original site isn't checked (and possibly the rest of the sites). I'm not sure what the exact function of the mirror is (except caching?), but repo1 is checked often regardless of mirror presence, so I figure it's not meant to totally disable checking the central repo's. Simple reproduction: define a few mirrors in your settings.xml for central, central-plugins and snapshots, pointing to say file://tmp/empty/dir/. Stacktrace: [DEBUG] Error resolving artifact version from metadata. org.apache.maven.wagon.ResourceDoesNotExistException: Unable to locate resource in repository at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:81) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:70) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:343) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:263) at org.apache.maven.artifact.metadata.AbstractVersionArtifactMetadata.retrieveFromRemoteRepository(AbstractVersionArtifactMetadata.java:93) at org.apache.maven.artifact.transform.AbstractVersionTransformation.retrieveFromRemoteRepository(AbstractVersionTransformation.java:171) at org.apache.maven.artifact.transform.AbstractVersionTransformation.resolveVersion(AbstractVersionTransformation.java:96) at org.apache.maven.artifact.transform.SnapshotTransformation.transformForResolve(SnapshotTransformation.java:43) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:95) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:290) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:274) at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:81) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:186) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:70) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:197) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:185) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:156) at org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComplete(DefaultPluginManager.java:544) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:479) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:334) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:378) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:351) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:337)
