Paul, The good ol' close/open. That plus a clean checkout seems to have helped. Subclipse doesn't really like the way the Maven plugin nests the projects within each other. Unfortunatley there doesn't seem to be a good mapping between the Maven way and the Eclipse way when it comes to multi module projects.
Adam On Fri, May 9, 2008 at 11:59 AM, Paul G <[EMAIL PROTECTED]> wrote: > > Adam, > > We have the same issue, the only fix we can find is to close the root > project in the work space then close and open the sub-modules it all seems > to work then, if I remember correctly. > > Paul > > > Adam Lewis-7 wrote: > > > > Hi, > > I'm using the 0.9.3 release of the plugin and am trying to use the > > "Check > > out Maven Projects from SCM" feature. This is on a multi module project > > and > > I am using the default option to create separate Eclipse projects for > each > > module. The checkout works fine and everything builds, but the team > > plugin > > (Subclipse) is getting confused by the sub-modules. It only sees the > root > > module as being attached to the repo (which makes sense since the > > sub-modules are part of the root on the filesystem) but all submodule > > content is seen as unversioned. > > > > Is anyone else having issues with multi-module / multi-project SCM > > integration? What is the correct way to get a multi-module project > > checked > > out and working with version control? > > > > Thanks, > > Adam > > > > > >
