Results 1 to 2 of 2
  1. #1
    esolve is offline Member
    Join Date
    Mar 2015
    Posts
    56
    Rep Power
    0

    Default Failure to transfer problem

    I'm dealing with a project written by other people
    I notice there is a problem in resolving org.icepdf
    and I notice there is no icepdf item in pom.xml

    so I added the following dependency

    Java Code:
    		<dependency>
    			<groupId>org.icepdf.os</groupId>
    			<artifactId>icepdf-core</artifactId>
    			<version>6.1.2</version>
    		</dependency>
    but after adding it, I get about 15 " Failure to transfer " errors, like

    Java Code:
    Failure to transfer org.bouncycastle:bcpkix-jdk15on:jar:1.54 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.bouncycastle:bcpkix-jdk15on:jar:1.54 from/to central (https://repo.maven.apache.org/maven2): The operation was cancelled.
    
    org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.bouncycastle:bcpkix-jdk15on:jar:1.54 from https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced. Original error: Could not transfer artifact org.bouncycastle:bcpkix-jdk15on:jar:1.54 from/to central (https://repo.maven.apache.org/maven2): The operation was cancelled.
            at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
            at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
            at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
            at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
            at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
            at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
            at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:367)
            at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:205)
            at org.apache.maven.project.DefaultProjectBuilder.resolveDependencies(DefaultProjectBuilder.java:215)
            at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:188)
            at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:119)
            at org.eclipse.m2e.core.internal.embedder.MavenImpl.readMavenProject(MavenImpl.java:636)
            at org.eclipse.m2e.core.internal.project.registry.DefaultMavenDependencyResolver.resolveProjectDependencies(DefaultMavenDependencyResolver.java:63)
            at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refreshPhase2(ProjectRegistryManager.java:530)
            at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager$3.call(ProjectRegistryManager.java:492)
            at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager$3.call(ProjectRegistryManager.java:1)
            at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
            at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
            at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:496)
            at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:351)
            at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:298)
            at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.getProjectFacade(MavenBuilder.java:154)
    this is strange, what can i DO?

  2. #2
    benji2505 is offline Senior Member
    Join Date
    Sep 2014
    Location
    MA, USA
    Posts
    398
    Rep Power
    5

    Default Re: Failure to transfer problem

    If it is a local repository you have to update the pom.xml file with the updated repo info.
    If it is a Maven repository you have to delete the .lastupdated files and then have Maven update the dependencies by right clicking the project -> Maven -> update project -> click Update Dependencies.

Similar Threads

  1. Failure of Preferences API under OSX
    By JerryAgin in forum Advanced Java
    Replies: 2
    Last Post: 02-29-2012, 10:20 AM
  2. Replies: 6
    Last Post: 02-24-2012, 11:11 AM
  3. Transfer int to string type problem!
    By mjzhaochenyi in forum New To Java
    Replies: 1
    Last Post: 10-02-2011, 05:27 PM
  4. Junit 4. failure(s)
    By sonny in forum New To Java
    Replies: 4
    Last Post: 08-03-2010, 04:35 PM
  5. Animation failure...
    By lordbob75 in forum New To Java
    Replies: 10
    Last Post: 05-11-2009, 02:06 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •