On Sun, 30 Oct 2005, Pete wrote: Correct. If you run maven from a child project, only that project and its children are visible, so those are the only ones in the reactor. You'll still get references, but to the jars. You only get references to projects instead of jars if the projects are 'visible' from the reactor.
Maven only 'climbs' the project tree to find possible parent pom.xml files; it does not traverse down again to find possible projects and add those to the reactor. -- Kenney > I noticed that if you use the mvn eclipse:eclipse and execute from > the parent pom all works ok, in that the .project files have the > correct references to dependant Eclipse Projects e.g. > > my web app .project file has the follwoing :- > > <projects> > <project>Manager</project> > <project>Model</project> > </projects> > > showing the dependancies. > > However, strangely if I execute mvn eclipse:eclipse from the web apps > pom.xml , the .project file gets generated but without the above > section. > > I have checked that the web app pom.xml has a <parent> and it does. I > guess the reactor isn't working when used from the child ? > > > On 28/10/05, Srepfler Srgjan <[EMAIL PROTECTED]> wrote: > > Hi Brian, > > I'm writing in relation to the j2ee artifact that was released and the > > maven-eclipse-plugin patch that you wrote. If I didn't understand > > wrongly it might be possible to put all projects on one level and then > > reference the modules in the main pom in a relative way like: > > <modules> > > <module> > > ../child-project1 > > </module> > > <module> > > ../child-project2 > > </module> > > </modules> > > So perhaps the eclipse plugin should also have the role of flattening > > hierarchical projects? > > That way it would be unnecessary to fork the j2ee archetype and > > maven-eclipse-plugin would know what would it need to be done. > > > > > > Brian Bonner wrote: > > > > >Hi guys, > > > > > >I was able to get the project to install with the required > > >dependencies of servlet on primary-sources and logging. > > > > > >I'm not sure about the EAR because I haven't created an EAR project in > > >the WTP. I've mostly done dynamic web projects. I use > > >spring/hibernate and have stayed clear of the packaging. I haven't > > >used j2ee clients per se. > > > > > >To get the web side working, I needed to add a build section to the > > >j2ee web's POM and the patch to EclipsePlugin *was* required. > > > > > >It also needed a base web.xml included in the tree to get the project > > >to load in tomcat. I think this should be added anyway as part of > > >the archetype. > > > > > >Brian > > > > > >--------------------------------------------------------------------- > > >To unsubscribe, e-mail: [EMAIL PROTECTED] > > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
