On Tue, October 16, 2007 3:44 pm, Saloucious wrote: > Ok refactoring projects has been validated !!! > > Thanks for your reply > > So, it will be easy now to follow conventions ;-)
Yay! > Is it a good solution to split project with a dedicated one for each > artifacts produced by ANT ? > > eg: a project for EJB , another for SAR ... Where it makes sense, yes. Maven can be configured to produce multiple artifacts per project, but generally you need to have a deep understanding of the maven lifecycle and what gets built when and in what order, leading to headaches. It is way simpler just to follow the one-artifact-per-project convention. An example of where it may not be necessary is where maven produces two artifacts from the same code, such as an EJB client side interface alongside the EJB implementation. Here maven cannot help but create two artifacts from one project, because the same source code can be used for both. What you'll find is that some of the projects will be very simple. In our case, our ear projects just contain a pom.xml, and nothing else. Regards, Graham -- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
