[Building Sakai] Nightly2 trunk build broken?

[csev]

I doubt that it is size related.  I agree that it is likely the  
inheritance of some context - perhaps something that even changes the  
definition os "what should be built".

I notice that some poms have precious little in the build section -  
for example site-manage-api only has this:

   <build>
     <resources/>
   </build>

If perhaps the only reason it worked in the first place was because it  
inherited the urge to compile java from some higher level pom - and  
somehow that inheritance is a different path - mvn might conclude  
"nothing to build here..."

Now I figured I would try this hypothesis by putting a meatier <build/ 
 > in - but it did not fix the problem.

But I too am thinking inheritance..

/Chuck

On Oct 2, 2009, at 10:30 AM, David Horwitz wrote:

> Hmm A possible suspect. My testing seems to suggest something to do  
> with plugin inheritance, brought in by search (which now inherits  
> from standard-tool pom rather than master) Removing search seems to  
> lead to predictable builds. So I have:
>
> 1) Removed search as a built module
> 2) Added a deployer to deploy the new search assembly (similar to  
> the kernel deployer)
>
> We where going to do this anyway and it should have the affect of  
> significantly improving build times.
>
> I suspect the culprit is a plugin definition getting pulled in from  
> kernel. For some reason this is not triggered by the commons project  
> but is by search. I'll investigate and probably switch to dependency  
> import on the standard-tool pom once we have a more up to date  
> version of maven.
>
> D