Re: [GUMP@vmgump]: Project smartfrog-components (in module smartfrog) failed

Hal wrote:
> Not irritated by the emails :)  Was just worried that something was amiss...
> 
> Thanks.
> 
> -----Original Message-----
> From: smartfrog-developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org [mailto:smartfrog-developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Goldsack, Patrick
> Sent: Friday, October 14, 2005 7:51 AM
> To: Hal; Smartfrog; smartfrog-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> Subject: RE: [Smartfrog-developer] [GUMP@vmgump]: Project smartfrog-components (in module smartfrog) failed
> 
> 
> Yes, this is in the minor (:-)) component CDDLM which is under
> development.... This does not affect the core.
> 
> Steve is, I am sure, on the case...!?
> 
> I agree that the email is very irritating. So apologies for that.
> 
> Patrick

It aint the CDDLM thing itself, and no I havent sat down to fix it.

What is going on is that we now have components that depend on other 
components, and the build files do not hard code the locations, but 
instead use the maven2 repository to synchronise stuff.

Only classloaders in gump override everything, so that the files arent 
being picked up.

the sole solution is to split up the component build from one big 
target, and actually describe in gump the full dependency graph of the 
more complex bits, including their output and their dependencies.

CDDLM is failing for another reason, but you aint getting that mail, and 
it is related to the version of xmlbeans on Gump, and the apparent 
absence of xmlbeans in the usual gump clean build process.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl