Re: repository problems (ibiblio.org) - redirections , HTTP response codes
Am 2018-07-05 um 16:24 schrieb David Balažic: Hi! During a clean build (we wiped the local repository cache) we encountered a problem with one artefact. We used the latest maven version 3.5.4 with Java 8u171. The error reported by maven is: Downloading from central: http://mirrors.ibiblio.org/pub/mirrors/maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.pom There is no reason to use ibiblio or alike anymore. Central these days is backed by several machines as well as people use repo managers. Go to TLS-enabled Central only. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: repository problems (ibiblio.org) - redirections , HTTP response codes
Hi, my first questions is: Why do you use ibiblio ? And not central ? Kind Regards Karl Heinz Marbaise On 05/07/18 16:24, David Balažic wrote: Hi! During a clean build (we wiped the local repository cache) we encountered a problem with one artefact. We used the latest maven version 3.5.4 with Java 8u171. The error reported by maven is: Downloading from central: http://mirrors.ibiblio.org/pub/mirrors/maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.pom [WARNING] Checksum validation failed, expected but is b113767b47336dcc165c5ddb5df4cb86b7ce from central for http://mirrors.ibiblio.org/pub/mirrors/maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.pom [WARNING] Could not validate integrity of download from http://mirrors.ibiblio.org/pub/mirrors/maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.pom: Checksum validation failed, expected but is b113767b47336dcc165c5ddb5df4cb86b7ce [WARNING] Checksum validation failed, expected but is b113767b47336dcc165c5ddb5df4cb86b7ce from central for http://mirrors.ibiblio.org/pub/mirrors/maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.pom Downloaded from central: http://mirrors.ibiblio.org/pub/mirrors/maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.pom (101 kB at 25 kB/s) [WARNING] The POM for org.springframework.roo:org.springframework.roo.annotations:jar:1.0.2.RELEASE is invalid, transitive dependencies (ifany) will not be available, enable debug logging for more details [WARNING] The POM for com.caucho:hessian:jar:4.0.7 is invalid, transitive dependencies (if any) will not be available, enable debug loggingfor more details [WARNING] The POM for commons-fileupload:commons-fileupload:jar:1.2.2 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [WARNING] The POM for javax.xml.bind:jaxb-api:jar:2.1 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [WARNING] The POM for org.codehaus.jackson:jackson-core-asl:pom:1.6.4 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details [WARNING] The POM for org.codehaus.jackson:jackson-mapper-asl:pom:1.6.4 is invalid, transitive dependencies (if any) will not be available,enable debug logging for more details Downloading from central: http://mirrors.ibiblio.org/pub/mirrors/maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.jar [WARNING] Checksum validation failed, expected but is b113767b47336dcc165c5ddb5df4cb86b7ce from central for http://mirrors.ibiblio.org/pub/mirrors/maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.jar [WARNING] Could not validate integrity of download from http://mirrors.ibiblio.org/pub/mirrors/maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.jar: Checksum validation failed, expected but is b113767b47336dcc165c5ddb5df4cb86b7ce [WARNING] Checksum validation failed, expected but is b113767b47336dcc165c5ddb5df4cb86b7ce from central for http://mirrors.ibiblio.org/pub/mirrors/maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.jar Downloaded from central: http://mirrors.ibiblio.org/pub/mirrors/maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.jar (101 kB at 28 kB/s) The core reason is the fact, that the mirrors.ibiblio.org site does not have this artefact but does not return a 404 HTTP response code, but a regular HTML page (after two redirects). Details: - first maven fetches this URL: http://mirrors.ibiblio.org/pub/mirrors/maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.pom the response is a 301 (Moved Permanently) with the header: Location: /maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.pom - the maven fetches http://mirrors.ibiblio.org/maven2/org/springframework/roo/org.springframework.roo.annotations/1.0.2.RELEASE/org.springframework.roo.annotations-1.0.2.RELEASE.pom which also returns 301 with Location: http://maven.ibiblio.org/maven2/ - maven finally fetches http://maven.ibiblio.org/maven2/ which returns code 200 OK , with a HTML file listing (ind
RE: Repository problems
I have the same problem... Occurs on maven 2.1.0 and 2.2.0. Do you have any solution? mgainty wrote: > > > looks like the HttpWagon saw an EOF.. > > can you post the pom.xml > also I would validate the pom.xml for well-formed > > Martin > __ > Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte > Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht > dient lediglich dem Austausch von Informationen und entfaltet keine > rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von > E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le > destinataire prévu, nous te demandons avec bonté que pour satisfaire > informez l'expéditeur. N'importe quelle diffusion non autorisée ou la > copie de ceci est interdite. Ce message sert à l'information seulement et > n'aura pas n'importe quel effet légalement obligatoire. Étant donné que > les email peuvent facilement être sujets à la manipulation, nous ne > pouvons accepter aucune responsabilité pour le contenu fourni. > > > > > > > >> Date: Tue, 7 Apr 2009 11:56:33 -0400 >> Subject: Re: Repository problems >> From: j...@strayer.org >> To: users@maven.apache.org >> >> Here is what I'm seeing now: >> >> [DEBUG] Retrieving parent-POM: org.apache.commons:commons-parent::5 for >> project: commons-logging:commons-logging:jar:1.1.1 from the repository. >> [DEBUG] commons-logging:commons-logging:jar:1.1.1:compile (range >> restricted from: [1.0,) and: 1.1 to: 1.1 ) >> [INFO] artifact com.lowagie:itext: checking for updates from central >> [WARNING] repository metadata for: 'artifact com.lowagie:itext' could not >> be >> retrieved from repository: central due to an error: Error transferring >> file >> [DEBUG] Exception >> org.apache.maven.wagon.TransferFailedException: Error transferring file >> at >> org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:104) >> at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68) >> at >> org.apache.maven.artifact.manager.DefaultWagonManager.verifyChecksum(DefaultWagonManager.java:654) >> at >> org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:485) >> at >> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:370) >> at >> org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:97) >> at >> org.apache.maven.project.artifact.MavenMetadataSource.retrieveAvailableVersions(MavenMetadataSource.java:404) >> at >> org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:346) >> at >> org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:408) >> at >> org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) >> at >> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300) >> at >> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288) >> at >> org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1415) >> at >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:405) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) >> at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) >> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) >> at org.apa
RE: Repository problems
looks like the HttpWagon saw an EOF.. can you post the pom.xml also I would validate the pom.xml for well-formed Martin __ Verzicht und Vertraulichkeitanmerkung / Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Date: Tue, 7 Apr 2009 11:56:33 -0400 > Subject: Re: Repository problems > From: j...@strayer.org > To: users@maven.apache.org > > Here is what I'm seeing now: > > [DEBUG] Retrieving parent-POM: org.apache.commons:commons-parent::5 for > project: commons-logging:commons-logging:jar:1.1.1 from the repository. > [DEBUG] commons-logging:commons-logging:jar:1.1.1:compile (range > restricted from: [1.0,) and: 1.1 to: 1.1 ) > [INFO] artifact com.lowagie:itext: checking for updates from central > [WARNING] repository metadata for: 'artifact com.lowagie:itext' could not be > retrieved from repository: central due to an error: Error transferring file > [DEBUG] Exception > org.apache.maven.wagon.TransferFailedException: Error transferring file > at > org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:104) > at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68) > at > org.apache.maven.artifact.manager.DefaultWagonManager.verifyChecksum(DefaultWagonManager.java:654) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:485) > at > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:370) > at > org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:97) > at > org.apache.maven.project.artifact.MavenMetadataSource.retrieveAvailableVersions(MavenMetadataSource.java:404) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:346) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:408) > at > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300) > at > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288) > at > org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1415) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:405) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) >
Re: Repository problems
Here is what I'm seeing now: [DEBUG] Retrieving parent-POM: org.apache.commons:commons-parent::5 for project: commons-logging:commons-logging:jar:1.1.1 from the repository. [DEBUG] commons-logging:commons-logging:jar:1.1.1:compile (range restricted from: [1.0,) and: 1.1 to: 1.1 ) [INFO] artifact com.lowagie:itext: checking for updates from central [WARNING] repository metadata for: 'artifact com.lowagie:itext' could not be retrieved from repository: central due to an error: Error transferring file [DEBUG] Exception org.apache.maven.wagon.TransferFailedException: Error transferring file at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:104) at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68) at org.apache.maven.artifact.manager.DefaultWagonManager.verifyChecksum(DefaultWagonManager.java:654) at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:485) at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:370) at org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:97) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveAvailableVersions(MavenMetadataSource.java:404) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:346) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:408) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:76) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1415) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:405) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: java.io.EOFException at java.util.zip.GZIPInputStream.readUByte(GZIPInputStream.java:202) at java.util.zip.GZIPInputStream.readUShort(GZIPInputStream.java:192) at java.util.zip.GZIPInputStream.readHeader(GZIPInputStream.java:131) at java.util.zip.GZIPInputStream.(GZIPInputStream.java:58) at java.util.zip.GZIPInputStream.(GZIPInputStream.java:68) at org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputData(LightweightHttpWagon.java:88) ... 30 more On Tue, Apr 7, 2009 at 10:26 AM, Brett Porter wrote: > Maven 2.1.0+ shows the error inline, but you can run with -X to see the > cause of the transfer error. It's likely not a content problem. > > - Brett > > > On 08/04/2009, at 12:17 AM, Jon Strayer wrote: > > After building correctly 28 times since I added at dependency on iText, my >> build just stared failing with this error message: >> >> [INFO] artifact com.lowagie:itext: checking for updates from central >> [WARNING] repository metadata for: 'artifact com.lowagie:itext' could not >> be >> retrieved from repository: central due to an error: Error transferring >> file >> [INFO] Repository 'central' will be blacklisted >> >> iText is still on the central repository. None of the files have changed >> this year, let alone today. >> >> Is anyone else seeing anything like this? >> >> What is Maven trying to tell me? >> >> -- >> All religions ar
Re: Repository problems
I ran mvn dependency:tree and it didn't list itext 1.02 (we use 2.08). After that the build worked. It's very strange. Is dependency information cached somewhere? That can't be it because it failed on the build server and on my laptop. After I ran dependency:tree on my laptop it worked there but still failed on the server until I ran dependency:tree there. On Tue, Apr 7, 2009 at 10:26 AM, Brett Porter wrote: > Maven 2.1.0+ shows the error inline, but you can run with -X to see the > cause of the transfer error. It's likely not a content problem. > > - Brett > > > On 08/04/2009, at 12:17 AM, Jon Strayer wrote: > > After building correctly 28 times since I added at dependency on iText, my >> build just stared failing with this error message: >> >> [INFO] artifact com.lowagie:itext: checking for updates from central >> [WARNING] repository metadata for: 'artifact com.lowagie:itext' could not >> be >> retrieved from repository: central due to an error: Error transferring >> file >> [INFO] Repository 'central' will be blacklisted >> >> iText is still on the central repository. None of the files have changed >> this year, let alone today. >> >> Is anyone else seeing anything like this? >> >> What is Maven trying to tell me? >> >> -- >> All religions are Scientology complete >> > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- All religions are Scientology complete
Re: Repository problems
Maven 2.1.0+ shows the error inline, but you can run with -X to see the cause of the transfer error. It's likely not a content problem. - Brett On 08/04/2009, at 12:17 AM, Jon Strayer wrote: After building correctly 28 times since I added at dependency on iText, my build just stared failing with this error message: [INFO] artifact com.lowagie:itext: checking for updates from central [WARNING] repository metadata for: 'artifact com.lowagie:itext' could not be retrieved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted iText is still on the central repository. None of the files have changed this year, let alone today. Is anyone else seeing anything like this? What is Maven trying to tell me? -- All religions are Scientology complete - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
