I'm trying to add guice to my Google App Engine project. I'm using Maven and Eclipse. In Eclipse, I modified my pom.xml by adding the following to the <dependencies> element as per http://mvnrepository.com/artifact/com.google.inject/guice/3.0:
<dependency>
<groupId>com.google.inject</groupId>
<artifactId>guice</artifactId>
<version>3.0</version>
</dependency>
However, Eclipse has raised four errors:
Description Resource Path Location Type
ArtifactTransferException: Failure to transfer com.google.inject:guice:jar:3.0 from http://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 com.google.inject:guice:jar:3.0 from/to central (http://repo.maven.apache.org/maven2): connect timed out pom.xml /audiencemarketing-backend line 123 Maven Dependency Problem
Description Resource Path Location Type
Missing artifact com.google.inject:guice:jar:3.0 pom.xml /audiencemarketing-backend line 1 Maven Dependency Problem
Description Resource Path Location Type
The container 'Maven Dependencies' references non existing library '/Users/mosofsky/.m2/repository/com/google/inject/guice/3.0/guice-3.0.jar' audiencemarketing-backend Build path Build Path Problem
Description Resource Path Location Type
The project cannot be built until build path errors are resolved audiencemarketing-backend Unknown Java Problem
I have tried right-clicking my project and choosing Maven => Update Project. But I still get the same 4 errors. I also tried Project => Clean and same thing.
How do I correctly add Guice given my setup?
I was able to resolve this error by going to my command line and issuing the command mvn clean install. Maven had no trouble obtaining the guice library from the Maven Central Repository. Then I went back into Eclipse and right-clicked my project and choose Maven => Update Project.
This resolved all the errors I was seeing and made Eclipse happy.
Related
I am trying to create new connector using mulesoft sdk. The connector has been successfully created and and loaded into the internal maven repository. When I try to reference the connector in the anypoint project, I get
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure to find org.demo.cloud:mule-connector:pom:1.0.0 in https://maven.anypoint.mulesoft.com/api/v2/maven was cached in the local repository, resolution will not be reattempted until the update interval of anypoint-exchange-v2 has elapsed or updates are forced
When I run the maven cmd in the command line, there are no errors. But as soon as I add dependency in the anypoint project pom file, I get the error. What could be wrong?
It looks like the Mule application project is trying to reference the connector reference with an incorrect Maven classifier. It should be a mule-plugin but the error message implies it is pom.
Example:
<dependency>
<groupId>org.demo.cloud</groupId>
<artifactId>mule-connector</artifactId>
<version>1.0.0</version>
<classifier>mule-plugin</classifier>
</dependency>
I faced similar issue before. I would like to add some extras to the existing answer.
The misuse of classifiers can happen when you try to pull artifacts from maven central without knowing what type of packaging type the artifact is made of during its maven release phase.
mvn release:clean
mvn release:prepare
mvn release:perform
Observe that when you add something as mule-plugin as a classifier in your dependency. It will add the connector plugin in your mule package explorer on the left hand side. This may not still resolve the pom unavailability problem you have pasted in the question.
I also believe that org.demo.cloud is an groupId not an artifact ID. Nevertheless, your application might not be a true mule-plugin based on its pom declaration.
Try packaging your main APP-1 (in maven central) as a mule-plugin in the APP-1 pom file. If not, simply put the packaging as jar type and republish your artifacts. Later, don't mention the classifier section in your APP-2. Simply call the direct dependency.
Check my other answer in here.:Unable to reference to DWL script files in Mule 4 dataweave from Project Libraries(jar)
I got the "Archive for required library cannot be read or is not a valid ZIP file" error for my maven project I imported in Eclipse. I read some posts about this and suggested is to delete the faulty directory like in my case:
~.m2\repository\com\cogentex\rpw\2.2 and
~.m2\repository\com\cogentex\rpw-lkb\2.2
Then you should update the project via Eclipse: Maven>Update project and click force update of snapshots/releases.
I followed these steps and the directory looks like this now:
So the correct .jar files are still missing and it also results in more erorrs now:
1: Missing artifact com.cogentex:rpw-lkb:jar:2.2
2: Missing artifact com.cogentex:rpw:jar:2.2
3: The container 'Maven Dependencies' references non existing library '~.m2\repository\com\cogentex\rpw\2.2\rpw-2.2.jar'
Here is the snippet from the pom.xml which throws the first two errors:
<dependency>
<groupId>com.cogentex</groupId>
<artifactId>rpw</artifactId>
<version>2.2</version>
</dependency>
<dependency>
<groupId>com.cogentex</groupId>
<artifactId>rpw-lkb</artifactId>
<version>2.2</version>
</dependency>
What do I have to do to make maven download the correct .jar files? I already tried running maven cleanor maven install and restarting Eclipse.
What you see in the folder is some files that indicate the artifact was not found and when was the last time Maven checked.
Whatever com.cogentex:rpw is, it's not in Maven Central so Maven will not find it there. You need to tell Maven where to get it from by providing the URL to a repository that contains it. If/when your POM has the repository, make sure
you do have access to the reposiory from the environment you run your build in (check proxies, firewalls, ...)
the GAV coordinates (groupId, artifactId, version) are correct and match the one in the repository.
the artifact type in the repository is jar. If it is not, provide the correct type in the dependency
the artifact is not deployed to the repository with classifier. If it is, provide the classifier in the dependency
I have a jar file which I need to include in my project.
I am using eclipse with Maven
I created the following folder in my project on my computer:
/home/robert/eclipse/BobProjects/BobDiary/in_project_maven_repository/metcarob.com.lib/nachocalendar/0.23
and I placed a file there called:
nachocalendar-0.23.jar
I then added the dependancy to my POM file:
<dependency>
<groupId>metcarob.com.lib</groupId>
<artifactId>nachocalendar</artifactId>
<version>0.23</version>
<scope>compile</scope>
</dependency>
I also added the Repo into my pom file:
<repository>
<id>in-project</id>
<name>In Project Repo</name>
<url>file:///home/robert/eclipse/BobProjects/BobDiary/in_project_maven_repository</url>
</repository>
from what I understand this should work.
When I right click on my project select run as and maven install I get the following error:
[ERROR] Failed to execute goal on project BobDiary: Could not resolve dependencies for project metcarob.com.BobDiary:BobDiary:jar:0.0.1-SNAPSHOT: Failure to find metcarob.com.lib:nachocalendar:jar:0.23 in file:///home/robert/eclipse/BobProjects/BobDiary/in_project_maven_repository was cached in the local repository, resolution will not be reattempted until the update interval of in-project has elapsed or updates are forced -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project BobDiary: Could not resolve dependencies for project metcarob.com.BobDiary:BobDiary:jar:0.0.1-SNAPSHOT: Failure to find metcarob.com.lib:nachocalendar:jar:0.23 in file:///home/robert/eclipse/BobProjects/BobDiary/
I have followed all the steps I can see for creating an in project repository but it still seems to not be able to find the file.
Does anyone know of a step I am missing?
Thanks
Robert
Update:
I must have made mutiple mistakes. Akber found my first mistake:
I have changed the folder so the group ID is in seperate folders:
(metcarob.com.lib is now metcarob.com.lib) The jar file is now in:
/home/robert/eclipse/BobProjects/BobDiary/in_project_maven_repository/metcarob/com/lib/nachocalendar/0.23
I have verified this because the following directory exists in my machine:
~/.m2/repository/metcarob/com/lib/nachocalendar/0.23
I have moved the file, restarted eclipse and re-ran maven clean and maven install.
The error is now:
[ERROR] Failed to execute goal on project BobDiary: Could not resolve dependencies for project metcarob.com.BobDiary:BobDiary:jar:0.0.1-SNAPSHOT: Failure to find metcarob.com.lib:nachocalendar:jar:0.23 in file:///home/robert/eclipse/BobProjects/BobDiary/in_project_maven_repository was cached in the local repository, resolution will not be reattempted until the update interval of in-project has elapsed or updates are forced -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project BobDiary: Could not resolve dependencies for project metcarob.com.BobDiary:BobDiary:jar:0.0.1-SNAPSHOT: Failure to find metcarob.com.lib:nachocalendar:jar:0.23 in file:///home/robert/eclipse/BobProjects/BobDiary/in_project_maven_repository was cached in the local repository, resolution will not be reattempted until the update interval of in-project has elapsed or updates are forced
However I also put this project into gitlab and use CI to compile it there with the command mvn install -B
My project now finds the dependency and compiles on the gitlab CI server.
Most likely, one of two problems:
Each part of the group id needs to be its own folder.
The pom.xml of the dependency should exist int the same folder in the repo.
you need to install the jar via maven into your local repo. maven does other things too except for just placing the jar into the respective folder.
please see here
To fix this I had to:
Change the directory structure. I had the group ID of "metcarob.com.lib" and had that as a single directory. I had to change that to 3 directories. metcarob/com/lib
I quit eclipse, deleted the directory ~/.m2 and restarted eclipse. When I did a build it built fine.
Akber's comment was the key but I can't mark a comment as correct to give him credit.
Thanks everyone for the help
I have started working on a new project using Maven, and I'm unable to have it work properly on eclipse. I have multiples of this error :
ArtifactTransferException: Failure to transfer com.caucho:hessian:jar:3.1.5 from <repository> was cached in the local repository, resolution will not be reattempted until the update interval of Archiva SIVPN Internal has elapsed or updates are forced. Original error: Could not transfer artifact com.caucho:hessian:jar:3.1.5 from/to Archiva SIVPN Internal (<repository>): No response received after 60000 pom.xml /<file> line 2 Maven Dependency Problem
Description Resource Path Location Type
Missing artifact com.caucho:hessian:jar:3.1.5 pom.xml / line 2 Maven Dependency Problem
After doing some research, I found that it was probably either the pom.xml that's wrong, or that I have proxy problems.
I checked that the resource was available on our repository, and that the pom snippet is the same as declared in my code :
<dependency>
<groupId>com.caucho</groupId>
<artifactId>hessian</artifactId>
<version>3.1.5</version>
</dependency>
My proxy works just fine for the trunk of the project, and there is no other proxy I'm aware of.
I thought it was maybe a one-time connection problem, but making a new maven build with -U didn't resolve the problem.
I also found https://stackoverflow.com/questions/6111408/maven2-missing-artifact-but-jars-are-in-place
with several I-don't-know-what-else-to-do solutions, but it didn't work for me...
Since the lead developer is on vacation and I have little experience on mvn, could someone tell me other potential problems that could be responsible for this ?
Thanks in advance for answers :)
Open a command prompt, go to your project directory and run: mvn eclipse:eclipse -DdownloadSources=true -DdownloadJavadocs=true
The eclipse:eclipse portion will regenerate your project files etc, the last 2 properties are more for convenience but I like downloading the sources and javadoc.
After a failed attempt, maven will leave a small file in your local .m2 repository that will prevent any attempt to re-download the file unless the update interval has elapsed or you force the updates using the maven -U switch described in other answers.
Just delete the folder for that artifact in your local m2 repository and update you project; a new download attempt will trigger.
rm -rf ~/.m2/repository/com/caucho/hessian/3.1.5
I was hoping someone might be able to help.
On a brand new windows machine. I've downloaded and installed java jdk before downloading and running the latest version of eclipse (indigo).
From there I have installed the maven integration plugin from the marketplace and created a new maven projected.
The project has a ton of errors mainly to do with missing dependencies or life cycle management.
When I do maven-clean I get the following error message:
[ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1: Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.4.1 from/to central (http://repo1.maven.org/maven2): Invalid argument: getsockname to http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom -> [Help 1]
I am not behind a firewall and I do not use a proxy. My maven settings.xml is completely default as is my maven project. No classes added, nothing added to the pom.
Can anyone help?
All the best.
p.s here are the errors shown in the pom:
1:
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: Failed to read artifact descriptor for org.apache.maven.plugins:maven-compiler-plugin:jar:2.3.2: ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-compiler-plugin:pom: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:pom:2.3.2 from/to central (http://repo1.maven.org/maven2): Invalid argument: getsockname to http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.3.2/maven-compiler-plugin-2.3.2.pom
2:
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (execution: default-testCompile, phase: test-compile)
3:
Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution: default-compile, phase: compile)
4:
Failure to transfer org.apache.maven.plugins:maven-resources-plugin:pom:2.4.3 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-resources-plugin:pom:2.4.3 from/to central (http://repo1.maven.org/maven2): Invalid argument: getsockname to http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.4.3/maven-resources-plugin-2.4.3.pom
Furthermore i recommend to test the configuration etc. first with command line client of Maven (Maven 3.0.X) and not within Eclipse.
The 1./4. shows that you have tried to download some artifact which has failed for whatever reasons. The simple solution for that is to delete the local repository and retry the build. But i recommend to do that first on command line to check if everything is fine.
The 2./3. are indications that the project you are trying to compile does not contain a correct plugin coverage for m2e which can be read in the docs how to solve that.
Problem:
You are missing an artefact in Your maven repository.
How to verify:
If You will browse Your repository You will find out that under .m2/repository/org/apache/maven/plugins/maven-clean-plugin/2.4.1/ artefact will have lastUpdated suffix - maven attempted to download this artefact but failed.
How to solve:
Just add an appropriate artefact into Your maven repository:) There are several ways how to do that but the simplest one will be dropping the folder with the missing artefact. Add since You can build Your project from the CMD just add missing artefact as a dependency into Your project. Build the project from the CMD.
Add dependency is not working through eclipse IDE(JUNO 4.2). Fixed the issue by manually adding dependencies with the below command on command prompt
go to the location where your pom.xml is located
mvn install
once you see status BUILD success from now onwards we can proceed with IDE.
Clearly this is an issue of proxy. Either use VPN or edit procy setting in setting.xml. I searched lot about this error. Finally, I used VPN(Virtual private network ) to disable the proxy and was able to use cetral repository of Maven.
IF you dont want to USE VPN just change Settings.xml host address with proxy address of ur company(which is available in IE->tools->connection->LAN settings->advanced->http. )
This is a proxy problem:
add your proxy config in your setting.xml
remove .m2 folder from your home directory
run any maven command in interactive mode from command line, for example try to create a project
mvn archetype: generate -DarchetypeGroupId=org.apache.maven.archetypes -DarchetypeArtifactId=maven-archetype-webapp -DgroupId=com.mycompany.app -DartifactId=my-webapp
that's all
I had the same problem. It was because I configured the repository in the settings.xml of my Maven Installation. But this in not used by Eclipse as it comes with its own Maven implementation. You need to configure the repositories (mirror section) in the settings.xml in your profile (.m2/settings.xml).