You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Pilgrim, Peter" <pe...@csfb.com> on 2005/11/01 14:05:58 UTC
Understanding Multi-modules ( was RE: [m2] Eclipse webapp lib )
I am trying to understand the multi-module in m2.
In the the sub module how does m2 actually know
about the parent module. I see in the pom.xml
that there is a parent XML tag element, but it does
not have a reference back direct to the parent, that
I can see. How does it actually work?
e.g
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<parent>
<artifactId>CSFB Cashflow IT</artifactId>
<groupId>com.csfb.cashflow.support</groupId>
<version>0.9.8-SNAPSHOT</version>
</parent>
...
</project>
--
Peter Pilgrim :: J2EE Software Development
Operations/IT - Credit Suisse First Boston,
Floor 15, 5 Canada Square, London E14 4QJ, United Kingdom
Tel: +44-(0)207-883-4497
> -----Original Message-----
> From: Srepfler Srgjan [mailto:srgjan.srepfler@lnksystem.com]
> Sent: 28 October 2005 22:50
> To: Maven Users List
> Subject: Re: [m2] Eclipse webapp lib
>
>
> 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: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
==============================================================================
Please access the attached hyperlink for an important electronic communications disclaimer:
http://www.csfb.com/legal_terms/disclaimer_external_email.shtml
==============================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Understanding Multi-modules ( was RE: [m2] Eclipse webapp lib )
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/1/05, Pilgrim, Peter <pe...@csfb.com> wrote:
>
>
> I am trying to understand the multi-module in m2.
> In the the sub module how does m2 actually know
> about the parent module. I see in the pom.xml
> that there is a parent XML tag element, but it does
> not have a reference back direct to the parent, that
> I can see. How does it actually work?
http://maven.apache.org/maven-model/maven.html#class_parent
The <parent> tag can contain <relativePath>. It's not documented there, but
the default must be ../ since that's what works with no configuration.
--
Wendy