Michael McCallum <[EMAIL PROTECTED]> wrote on 03/07/2008 14:05:09: > 11) don't mix inheritance and aggregation. that means a parent pom NEVER ever > has modules, if you think about the concept for a minute - or longer - there > will be a moment of enlightenment
Sorry for jumping in here, but wehy not? The only time (admitedely) I use this is for a multi module J2EE project, where each module (WAR, EAR, EJB, JAR etc) all have the multi module pom as their parent, and the multi module pom has the corporate one as it's parent. I was told to do this, and in fact, if you you use archetype:create-from-project (?) that is how it generates the pom structure of the generated archetype. So, I'm curious as to why you would say not to do this. -Chris ********************************************************************** CAUTION - This message is intended for the addressee named above. It may contain privileged or confidential information. If you are not the intended recipient of this message you must: - Not use, copy, distribute or disclose it to anyone other than the addressee; - Notify the sender via return email; and - Delete the message (and any related attachments) from your computer immediately. Internet emails are not necessarily secure. Australian Associated Motors Insurers Limited ABN 92 004 791 744 (AAMI), and its related entities, do not accept responsibility for changes made to this message after it was sent. Unless otherwise stated, views expressed within this email are the author's own and do not represent those of AAMI. ********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
