The current packaging is designed to produce one Eclipse project, but to make sense of it you need the m2eclipse plugin (or MyEclipse with built in Maven support). When you check out, you get the main project with its POM and the subprojects with their POM. The .project file is already set up, and the .classpath file has a reference to the Maven dependencies as Eclipse libraries, but unless you already did a Maven build of this version on your machine you will not have downloaded these libraries to your local repository. So M2Eclipse can be told to run through the POMs, download the dependencies, and frequently it rebuilds the .classpath source and library configurations. The three M2Eclipse options you need to use from the menu (approximate wording) the manage subprojects check option that processes the subproject POMs mentioned in the top level POM, the reprocess dependencies action that downloads all missing dependencies, and the reprocess POM option that runs through all the POMs and rebuilds both the list of source files and the list of Maven dependency libraries.
Then you get one project with different source files for every subproject (and source, test, and sometimes resource per project). You can build and deploy from Eclipse, but you can also build and deploy with Maven (although I suggest using MVN in the directory because the actual Maven build from Eclipse seems to always have Mojo problems). -----Original Message----- No, it's more convenient to keep them as 15 projects. -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
