m2e

How can I reference another workspace project using Eclipse m2e ? Do I have to add a project dependency in the project setting? But in that case the dependency is not shown in the pom. If I set them in the pom, it will not reference the project in workspace but reference the jar in the local repository. Quite annoying, anyone can help? nwinkler The correct way to do this is the following: Use the dependencies section in the POM file exclusively, don't fiddle with the Eclipse project references. Right-click the project, then select Maven > Update Project Configuration to reset the project to

I'm trying to automatically deploy a Maven webapp from Eclipse Java EE to my local Tomcat server. I'm using Windows XP. This is the error: [ERROR] Failed to execute goal org.codehaus.mojo:tomcat-maven-plugin:1.1:deploy (default-cli) on project practicaIW: Cannot invoke Tomcat manager: Server returned HTTP response code: 403 for URL: http://127.0.0.1:8080/manager/deploy?path=%2Fpractica-3&war= -> [Help 1] I think I know the reason of this error: If I run the Tomcat server inside eclipse, 127.0.0.1:8080 is my workspace/target. There is any manager folder and rest of classes on it, so it does not

I am trying to get setup to use Maven and pom.xml files in Eclipse for my Android projects. I have Eclipse Indigo setup (m2e included), Android SDK installed, ADT installed. I am struggling to understand what it means to "Install the m2e-android-plugin" (I am always taken to this page which provides instructions on installing it, but which I cannot follow) Specifically, when I go through the instruction on that page, after I complete all the steps in part 2, my structure does not have "Maven Dependencies" and my pom.xml file shows the following error: Project build error: Unresolveable build

I am working on maven 2 project on eclipse, and I have the m2e plugin, and I am getting the following error in Eclipse: Failure to transfer com.thoughtworks.xstream:xstream:pom:1.3.1 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 com.thoughtworks.xstream:xstream:pom:1.3.1 from/to central (http:// repo1.maven.org/maven2): Failed to create a selector. to http://repo1.maven.org/maven2/com/thoughtworks/xstream/ xstream/1.3.1

I'm attempting to add a source folder for maven java project to Eclipse using a maven plugin. When trying to use the org.codehaus.mojo plugin I receive the following error Failed to execute goal org.codehaus.mojo:build-helper-maven-plugin:1.7:add-source (default-cli) on project application-framework: The parameters 'sources' for goal org.codehaus.mojo:build-helper-maven-plugin:1.7:add-source are missing or invalid -> [Help 1] From reading the docs on http://mojo.codehaus.org/build-helper-maven-plugin/usage.html this should be correct ? The folder target/sources/mygeneratedfiles on exists.

I'm having a weird configuration problem with Maven in Eclipse. Although I can build the project and deploy it to tomcat without any errors, The Marker tab keeps showing the following message: [-] Maven Java EE Configuration Problem (x) JavaServer Faces 1.2 can not be installed : One or more constraints have not been satisfied. (x) JavaServer Faces 1.2 requires Dynamic Web Module 2.5 or newer. I am in fact using Dynamic Web Module 2.4, which would be the source of the message. I would need to change it to at least 2.5 to work with JSF. Problem is, I'm not even using JSF. So, probably one of

For my team, I'd like to configure maven/eclipse build to automatically generate Java code from *.proto files (in a project that uses gRPC ). Currently one needs to run mvn generate-source or mvn protobuf:compile (as in plugin usage page ). Or what is the same add Run configuration to invoke maven goal compile . Whenever Eclipse Maven project is refreshed ( Alt + F5 ) or IDE is restarted, project is rebuilt but without what should appear in target/generated , thus turning project into red. So one need to generate and refresh project ( F5 ). UPDATE Eclipse has needed source folders configured