Develop Reference

Project facet Dynamic Web Module 4.0 is not supported by this server

When, in Spring Tool Suite, I try to run my project with Weblogic 12 I get this error:
Project facet Dynamic Web Module 4.0 is not supported by this server
Inside org.eclipse.wst.common.project.facet.core.xml I turned <installed facet="jst.web" version="4.0"/> into <installed facet="jst.web" version="3.1"/> but after doing maven->update project the version came back to 4.
I tried also to change the version here, but I get the error: Cannot change version of project facet Dynamic Web Module to 3.1
I even tried to uncheck Dynamic Web Module (as suggested in another post) but I get the error: Dynamic Web Module 4.0 cannot be uninstalled
Does anybody know how to solde the problem?

I just recently had the same problem. The Dynamic Web Module is set by Maven according to your version of javax.servlet-api. Since Spring Boot 2.1.x imports Servlet-API version 4.0, Maven changes the project facet to match it.
Set Spring Boot's version to 2.0.8 or newer, which uses Servlet-API 3.1, and you'll be able to deploy your app to Weblogic 12c via Eclipse.

Maven jersey artifact create a project with no target runtime options

I'm trying to build a restful api using a Maven project and tomcat in eclipse.
in the maven project wizard i am using 'org.glassfish.jersey.webapp.archetypes' 'jersey-quickstart-webapp' version 2.26:
the problem is - after the project is build, tomcat dosn't recognize the
maven project as a resource:
I'v tried to add the target runtime in the project properties but it won't
show up:
How can i correct this? (preferably using a maven)

Found the solution: I was missing m2e-wtp - JAX-RX configurator for WTP plugin in my eclipse:
To fix this issue:
1) Go to help->install new software
2) Select eclipse repository (I'm using Oxygen this will be different for another eclipse version)
3) Under: Web, XML, Java EE and OSGi Enterprise Development
select: m2e-wtp - JAX-RX configurator for WTP
4) Proceed Installation and restart eclipse
Note that an existing maven project will not automatically be fixed but a new project will be set correctly

Do i need to use embedded maven for m2e workspace resolution to work?

In my previous pc I was working with linux, eclipse Indigo, m2e (I suppose v1.2 or v1.3) and maven 2.
I had configured m2e to use my external maven 2 installation, had projectA depend on projectB and without the need to install any of the projects to the maven local repository I could execute an Eclipse Maven Build (e.g: compile or dependency:tree) configured to use the external maven installation and to Resolve artifacts in workspace. That worked.
Now, I 'm using win7, eclipse kepler, m2e 1.4.1 and maven 3. I configured all in the same fashion (use external maven installation), create the same projects, use the same eclipse Maven build (run configuration) with workspace artifact resolution enabled and it don't work.
Right now it only works if i configure the maven build to use the internal eclipse embedded maven installation.
I 'd really like to always use my external instalation, does anyone knows if this feature was removed from m2e or should this scenario work as I expected and maybe it's a bug thats happening in my specific environment?

It's worth checking that the settings.xml for your external maven makes sense, and eclipse is configured to use it.

I 've tested in other similar environments obtaining same results but, when
upgraded to Eclipse Luna problem was solved.
If you 're facing similar problem, then upgrade to Eclipse Luna.

How do I set up a new Java project with Eclipse, Maven, Grails and git?

I'm new to Grails development and would like to set up a new project, so I can use Eclipse as IDE and build it on my CI (Jenkins) with Maven. This is my environment:
Java 1.6.0
Grails 2.1.0
Maven 2.2.1
Eclipse Juno with the m2e and egit plugins
I used the following commands from
http://grails.org/doc/latest/guide/commandLine.html#antAndMaven:
mvn archetype:generate -DarchetypeGroupId=org.grails \
-DarchetypeArtifactId=grails-maven-archetype -DarchetypeVersion=2.1.0 \
-DgroupId=com.company.dep -DartifactId=project
mvn initialize
But after importing it as a maven project in Eclipse, there were erros about slf4j and com.sun.tools not found and lifecycle phases not mapped.
What steps are necessary to get this running in Eclipse?

Plugins, Plugins, Plugins... you can add the maven plugin / Grails plugin for eclipse and just build a new project.
Select the option to create a maven project (it will auto generate the pom files for you) then you can add Grails to it...
Similarly you can start a new grails project and then add maven to it. It will download all the dependencies automatically.
Most plugins are free to download from : http://marketplace.eclipse.org

com.sun.tools error is commonly caused when Eclipse uses a JRE and not JDK.

Grails has its own mechanism for creating projects, use it. Since Grails 2.1 you can generate the maven stuff afterwards.
You can follow this proces:
Get STS - Springsrouce Tool Suite (actual 3.0), based on Eclipse
Install the Grails plugin into STS.
Get the Grails FW, unpack it and configure the path to it in STS.
Create new project via Grails command: grails create-app
Import it into Git.
About maven integration, there is a good article:
http://www.znetdevelopment.com/blogs/2012/07/11/grails-2-1-and-maven-integration-simple-project/

spring mvc test using eclipse and maven2

So I created a simple web app using maven, the pom.xml is setup in Eclipse just fine.
I added apache commons, spring 3.0 as a dependancy.
I created a test controller using annotations, and a jsp file.
In eclipse, I only see a Run option, and no build option. With maven2 pom.xml setup etc., is just clicking on Run enough to build the project?

If you have m2eclipse installed and if your project is recognized as a "Maven project", then you should have more entries in the Run As... and Debug As... menus allowing to run a Maven build within Eclipse:
(source: theserverside.com)
And if you don't have m2eclipse installed, either install it(!) or launch Maven as External Tools (but this won't provide "real" integration).