Once the Eclipse m2e plugin imports a Maven project, it will create for you a .project file, a .classpath file and possibly a .settings folder. Those are your Eclipse artifacts.
Gary On Mon, Dec 27, 2021 at 10:30 AM Ed Dowgiallo <[email protected]> wrote: > Slawomir, > > Yes, all works fine at command line. All 31 modules work for mvn clean, and > I currently get a package not found in module 25 which is my bug. > > It is not publicly accessible. > > Is this supposed to work strictly off the pom.xmls? Or are there eclipse > configuration files involved? > > Ed > > On Mon, Dec 27, 2021 at 10:17 AM Slawomir Jaranowski < > [email protected]> > wrote: > > > Hi, > > > > Does your fresh project after git checkout build correctly with all > modules > > by standard Maven command, like > > mvn clean verify > > from command line? > > > > Is your project accessible publicly? > > > > > > pon., 27 gru 2021 o 15:56 Ed Dowgiallo <[email protected]> > napisał(a): > > > > > Hi, > > > > > > First time poster. > > > > > > I like the Maven approach to modules and am using it for my projects > with > > > the Eclipse IDE. Not quite getting something right though. After I have > > > committed a project to git and do a fresh checkout of it on a different > > > computer, it appears to forget all the module structure. The child > > projects > > > disappear and the main project changes the module source folders to > > regular > > > folders. > > > > > > Is there a configuration file other than pom.xml missing from my git > > > commits? > > > > > > Is it possible for me to restore the lost module structure? > > > > > > Thank you, > > > Ed > > > > > > > > > -- > > Sławomir Jaranowski > > >
