aspose file tools*
The moose likes IDEs, Version Control and other tools and the fly likes About maven Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » IDEs, Version Control and other tools
Bookmark "About maven" Watch "About maven" New topic
Author

About maven

Singh Harmeet
Ranch Hand

Joined: Aug 05, 2011
Posts: 115

when i use springsource tool suite , for create the spring program , when to create first spring project using new - > spring template project after this the tool want to download some files from internet , but after the file downloading the tool unable to download some maven plugins , and the error is not resolve. there is following error in pom.xml :-

1. Failure to transfer org.apache.maven.plugins:maven-compiler-plugin:jar:2.3.2 from http://repo1.maven.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.apache.maven.plugins:maven-compiler-plugin:jar:2.3.2 from/to central (http://repo1.maven.org/maven2): No response received after
60000

2. ArtifactTransferException: Failure to transfer org.springframework:spring-core:jar:3.0.6.RELEASE from http://repo1.maven.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.springframework:spring-core:jar:3.0.6.RELEASE from/to central (http://repo1.maven.org/maven2): No response received after
60000

3. ArtifactTransferException: Failure to transfer log4j:log4j:jar:1.2.14 from http://repo1.maven.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 log4j:log4j:jar:
1.2.14 from/to central (http://repo1.maven.org/maven2): Write error

4. Multiple annotations found at this line:
- Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution: default-
compile, phase: compile)
- CoreException: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-compiler-plugin:2.3.2 or one of its dependencies
could not be resolved: Failure to transfer org.apache.maven.plugins:maven-compiler-plugin:jar:2.3.2 from http://repo1.maven.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.apache.maven.plugins:maven-compiler-plugin:jar:2.3.2 from/to central (http://repo1.maven.org/maven2): No response received
after 60000
- Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (execution:
default-testCompile, phase: test-compile)


how to resolve this error?


With Regards :-
Harmeet Singh
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5843
    
    7

Run a build from the command line adding the -U option:

mvn -U

That will force Maven to reattempt to download the plugins. Apparently, you tried earlier and the connection was not up. When that happens, there is a timeout (usually 24 hours) that prevents Maven from attmepting to access the the artifacts from the remote repository. The -U will force Maven to ignore the timeout. By the way, this all assumes that you now have access the http://repo1.maven.org/maven2.

By the way, do you use a proxy to access the net? If so, you will first have to configure Maven to use the proxy.


JBoss In Action
 
Don't get me started about those stupid light bulbs.
 
subject: About maven