On Thu, 29 May 2008 23:52:35 Bracewell, Robert wrote: > This is roughly what I seem to be moving towards. Over the past couple > of days I have been converting a hierarchical project into an approach > similar to what you listed to get a feel for things One key thing is that my pom hierachy looks like this...
root -> jar -> service -> api -> model -> jaxb2 -> webapp -> abstract webapp -> assembly each of these parents contains the plugin configs needed for the particular artifact. Any given artifact would inherit from one of there functional parents. So a model project has standard jar plugins and very basic metrics and checks as its mostly just basic beans where as a service project would need to pass at least an 80/60 cobertura report for units tests. The groupId for me is related to the position in the source control hierarchy and maven reposititory but nothing else really. My biggest issue at the moment, although I have not tried to solve it is that I want the reactor to generate my docs and NOT use inheritance in any way for it just aggregation. I'm hoping thats what dashboard is for but time has not permitted research. I think I might need to figure out how to package up and deploy the xml report outputs so that any site aggregator can accumulate the site for a deliverable. As the site docs generally should accompany a released deliverable not the overall source tree, that always seemed backwards to me. -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
