On Fri, 04 Jul 2008 18:37:14 [EMAIL PROTECTED] wrote: > 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. firstly there is this magic default relationship between a project and its parent esp if you put the parent in the parent directory... which means that end not having a consistent pom... it can inherit from the one on disk not the one specified... this might no longer be a problem but I had all sorts or problems and the user list it littered with them going back a long time
and it just smells bad... it seems like with people are doing all sorts of nasty things to make the two work together... property interpolation.. snapshots... and you really don't need it... we just use release dependencies os there is no need to release a bunch of things in one go... i do use modules to generate docs and continuous integration but they are isolated and only aggregate for that purpose... i might be tempted to release more that one thing at a time with an aggregation but it has too many shortcuts based ont he bad smell of inheritance + aggregation gotta sleep more later -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
