that's because mvn compile ends on compile phase of maven's default lifecycle. do mvn package and check then. and by the way, default maven output directory is target so rather check it instead of kind of wtp temporary dirs.


it is necessary to clarify the role of the commands you used and their impact on eclipse.

the mvn eclipse:eclipse command creates the eclipse project files, in order to save you the hassle of configuring a new project and identifying all the sources for it. this command is also equivalent to creating a new eclipse project from an existing maven project using the m2e eclipse plugin. see also this page regarding the eclipse:eclipse command. that being said, you only need to run such command once, and then import the resulting project into eclipse.

secondarily, mvn compile builds your source files into the target directory of your nomemiaapplicazione root folder. this command does not involve eclipse in any way. also, web resources are still not packaged. to package them, you need to issue mvn package: you will then find the <artifact>-<version>.war file again under target, and the pre-packaged content under target\<artifact>-<version>. beware that, in order to account for the webapp content, your maven packaging must be of type war. check the pom.xml for the <packaging> tag.

finally, deployment is still another issue. if you actually need to move your .war file from the target directory to somewhere else (namely, an autodeploy folder of a servlet container), you can configure the maven deploy plugin and issue mvn deploy. i'd rather suggest you to search so for deploy war eclipse and/or deploy war maven, since there's plenty of related stuff. in the first case, you will find how to use eclipse as a facility for deployment, while the second case leverages the command line to provide a more portable/flexible deployment procedure.

Related Query

More Query from same tag