|Publish to server does not build [message #1009224]
||Thu, 14 February 2013 12:47
| David Balažic
Registered: February 2013
I posted this to m2eclipse mail list, but was suggested to try here:
This is not related to maven nor m2e but is a WTP bug/feature. So the WTP forum is probably a more appropriate place to discuss that problem.
My original message:
Using m2eclipse 1.2.0 with Eclipse 3.7.2 I noticed this surprising behavior.
I have several projects in Eclipse, each a maven project.
I set up tomcat 6.0 in Eclipse for running the code.
Once for clean up purposes I disabled the "Project/Build Automatically" menu item and performad a Project/Clean...
After I while I forgot about this and tried to publish the code to the server and run it.
After the start it complained about not finding things on the classpath.
The reason is that the *.class files and the JAR files (the dependent projects) were missing.
I would expect either a build triggered before the deployment or an error dialog informing me that it can not deploy the project because it is not built.
Or am I missing something and this is the intended way of operation?
Eclipse Java EE IDE for Web Developers.
Version: Indigo Service Release 2
Build id: 20120216-1857
Eclipse Platform 3.7.2.M20120208-0800 org.eclipse.platform.ide null
Java EE IDE Feature 126.96.36.19920213-0813 org.eclipse.epp.package.jee.feature.feature.group Eclipse Packaging Project
m2e - Maven Integration for Eclipse 188.8.131.5220903-1050 org.eclipse.m2e.feature.feature.group Eclipse.org - m2e
Subclipse (Required) 1.8.18 org.tigris.subversion.subclipse.feature.group tigris.org
Subversion Client Adapter (Required) 1.8.3 org.tigris.subversion.clientadapter.feature.feature.group tigris.org
Subversion JavaHL Native Library Adapter 184.108.40.206 org.tigris.subversion.clientadapter.javahl.feature.feature.group tigris.org
Powered by FUDForum
. Page generated in 0.05551 seconds