[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18128: ------------------------------------- Sorry but your test project is borked, which explains why the jars are not deployed properly : - the main issue is your web.xml says servlet 2.5 but the project's Web Facet was set to 3.0. m2e-wtp tries to set the Web Facet from the web.xml level, so tries to downgrade it from 3.0 back to 2.5. Unfortunately, WTP throws an Exception when downgrading Facet. This prevents m2e-wtp from completing your project configuration, notably the Maven Classpath library is not onfigured for deployment, hence no jar is deployed. - Another issue is maven/m2e/JDT use target/classes to generate class files, but your project is configured to deploy build/classes instead, that's why many of your classes are missing from deployment The simplest solution is to delete your project from your workspace, then delete all .project, .classpath and .settings/ resources and finally reimport your project as a Maven project. Another alternative is to : - either change the servlet version in web.xml to use 3.0 or edit .settings/org.eclipse.wst.common.project.facet.core.xml and use <installed facet="jst.web" version="2.5"/> to downgrade from 3.0 - edit org.eclipse.wst.common.component and change <property name="java-output-path" value="/TestJboss/build/classes"/> to <property name="java-output-path" value="/TestJboss/target/classes"/> - Right-click on project and Maven> Update Configuration (or use the Alt-F5 shortcut) - force clean publish on your server -- This message was sent by Atlassian JIRA (v6.3.1#6329)