See also this link: http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Thu, Oct 1, 2009 at 7:28 PM, Nick Stolwijk <[email protected]> wrote: > From each module there will be one main artifact, ie a jar. Sometimes > there can be multiple artifacts, like javadoc or sources. If you say > that your ant script generates multiple jars, you will need to have > multiple modules. That can be child-parent relation, or just a > aggregator pom. > > Child parent relation: > Each module has a section <parent> which point to a pom with shared > configuration and/or dependency(management). > > Aggregator pom: > You have multiple modules in subdirectories. You create a pom file > with the modules tag to kick of all the builds with one command. > > These strategies can be combined. Your parent pom can also be your > aggregator pom. > > Hth, > > Nick Stolwijk > ~Java Developer~ > > IPROFS BV. > Claus Sluterweg 125 > 2012 WS Haarlem > http://www.iprofs.nl > > > > On Thu, Oct 1, 2009 at 7:14 PM, chicagopooldude > <[email protected]> wrote: >> >> Thanks for your reply I have already started to use the antrun plugin. I >> wanted to know if you can please share some documentation on using seperate >> modules. Should I use parent-child modules ? >> -- >> View this message in context: >> http://www.nabble.com/Ant-to-Maven-tp25696939p25703038.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> 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]
