Re: build broken

I hacked around on the pluto build and got it to complete, see rev  
774969.

We may have introduced some problems with putting the assembly plugin  
configuration for the source distros into portals-pom  
pluginManagement.  We may also be able to fix the problems by  
requiring maven 2.1 or 2.0.10.  I'll investigate.

The m-r-r-p doesn't do too well with war files, it puts the license/
notice files in WEB-INF/classses/META-INF where they appear (to me at  
least) to apply to the classes in WEB-INF/classes rather than to the  
entire war.  We need to do something either to relocate the legal  
files or make the ianal plugin happier with their location.

I'm pretty confused by the intentions in the pluto build.  It  
certainly needs a __lot__ of cleanup if we use the portals-pom as  
parent, many many plugins are respecified.

The main non-straightforward-question for me is why the root pom that  
builds everything isn't also the parent pom.  I think the intention is  
to release all the pluto stuff at once at the same version; in this  
case I think the standard maven structure is to have the root pom be  
also the parent of all the modules.  If the intention is to make the  
modules independently releasable then the root pom needs a really  
prominent notice that it must not be used for releases.

thanks
david jencks


On May 14, 2009, at 3:42 PM, David Jencks wrote: