Just a note so that folks know what's coming. The maven-eclipse-plugin will not work with M2Eclipse anymore. If M2Eclipse sees projects generated with the maven-eclipse-plugin it won't import them. M2Eclipse works by creating the necessary projects files by inspecting the POM and doesn't expect the Eclipse project files to have been created by an external third party.
If you use the maven-eclipse-plugin your projects will not be supported in M2Eclipse. You will need to pick one mode, either use the maven-eclipse-plugin and stock Eclipse or import your projects using M2Eclipse. Just a heads up. On Mar 15, 2010, at 12:58 PM, Martin Schayna wrote: > Hi, > > after some by-hand editing of configuration files, that have been mentioned > here, it works. > But when I try to run eclipse:eclipse goal of maven-eclipse-plugin again, it > breaks and I have > to revert changes. We can live with that :) > > Martin > > > On 15.3.2010 17:23, Michel Pawlak wrote: >> Hi >> >> I have the same issue, have you found a solution or reported a bug ? >> >> Thank you in advance >> >> >> Martin Schayna-2 wrote: >> >>> Hi all, >>> >>> we have pretty large project, successfully "mavenized" with Maven 2, >>> split into several module projects under one parent pom. We are using >>> m2eclipse plugin in Eclipse 3.5. >>> >>> Project tree looks like: >>> >>> parent/ (pom project) >>> +-- lib-core/ (jar project) >>> +-- lib-web/ (jar project, with shared webapp folder) >>> +-- app1/ (war project) >>> +-- app2/ (war project) >>> +-- app3/ (war project) >>> >>> parent project serves as agregator, its pom.xml defines common settings. >>> lib-web project depends on lib-core project, application projects depend >>> on both lib projects. All projects share same version, we are releasing >>> all applications at once through parent pom. >>> >>> For everyday develepment we use SNAPSHOT postfix in version, dependecies >>> on module projects are specified as "project dependencies", so changes >>> in library projects in Eclipse cause rebuild dependent application >>> projects. Snapshots are disabled in our repository (Archiva). >>> >>> But when I try setup WTP support through maven-eclipse-plugin goal >>> "eclipse:eclipse" and some necessary changes in Eclipse, publishing to >>> Tomcat creates only WEB-INF/lib folder with (correct) out-of-project >>> jar dependencies and WEB-INF/classes folder with CURRENT project >>> classes. No binaries from "project dependencies" lib-core and lib-web. >>> >>> I have tried to change org.eclipse.wst.common.component file in many ways, >>> e.g.<dependent-module>, but without success. >>> >>> Another weird thing: when I try to include resources from shared webapp >>> folder from lib-web project and use relative source-path like this: >>> >>> <wb-resource deploy-path="/" >>> source-path="../lib-web/src/main/webapp"/> >>> >>> publish can't copy subfolders content to Tomcat. Must explicitly >>> specified: >>> >>> <wb-resource deploy-path="/btns" >>> source-path="../lib-web/src/main/webapp/btns"/> >>> <wb-resource deploy-path="/icons" >>> source-path="../lib-web/src/main/webapp/icons"/> >>> <wb-resource deploy-path="/imgs" >>> source-path="../lib-web/src/main/webapp/imgs"/> >>> ... >>> >>> Please, what is the right WTP setup for multi modules configuration with >>> "project >>> dependencies" and shared resources? Or is there any documentation for file >>> org.eclipse.wst.common.component? >>> >>> I'm going little bit crazy... thank God debugging with Jetty works like >>> a charm, >>> either with shared resources (must hack with >>> WebAppContext.setResourceBase() in >>> starter class). >>> >>> Thanks a lot. >>> >>> Martin Schayna >>> >>> >>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl ----------------------------------------------------------
