Looking at the latest gump run results I'm seeing that even if dependent build are not successful, gump is still attempting to build dependees and in the process assigning and passing invalid property values to the build target. For example - avalon-http-impl dependency jasper-runtime is not available, however gump is supplying jasper-runtime outputs as a property value and continuing with the build.
http://brutus.apache.org/gump/public/avalon-trunk/avalon-http-impl/gump_ work/build_avalon-trunk_avalon-http-impl.html BUILD FAILED /usr/local/gump/public/workspace/avalon-trunk/central/system/build/stand ard.xml:11: Gump source resource override for resource [artifact:jar:tomcat/jasper-runtime#27082004] references a non-existant path [/usr/local/gump/public/workspace/jakarta-tomcat-5/dist/common/lib/jaspe r-runtime.jar]. Seems to me that Gump should *not* attempt to execute a project unless it can assure that the values it is assigning are in fact valid. Stephen. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
