Hi!
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?
Version details:
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 1.4.2.20120213-0813
org.eclipse.epp.package.jee.feature.feature.group Eclipse Packaging
Project
m2e - Maven Integration for Eclipse 1.2.0.20120903-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 1.7.8.1
org.tigris.subversion.clientadapter.javahl.feature.feature.group
tigris.org
David Balažic
Software Engineer
ComTrade
Letališka cesta 29b, 1000 Ljubljana
Slovenia
phone: +386 81 60 8937
fax: +386 1 586 52 70
www.comtrade.com
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users
