Re: GUMP: Anyone know what is going on?

there is a "path-like structure" definition in the buildfile, which is 
referencing a directory outside of the project scope of the gump 
definition coupled to that buildfile. This results in an error. Its been 
happening all over avalon wrt to ${jakarta-site.dir}, where the problem 
first appeared because gump is checking out jakarta-site2, and we are 
depending on jakarta-site (same module, symlinked). The solution is to 
have the variable that references tools/lib (ie ${tools.dir}) set in the 
gump descriptor. Lots of examples for that available.

If you want nagging on prereq failures or stuff like that, you can 
simply craft a regular expression to capture the problem. See docs on 
the <nag/> tag at http://jakarta.apache.org/gump/project.html. Ie you 
could add

<nag>
   <regexp pattern="/BuildException/"
           from="Gump Integration Build <[email protected]>"
           to="Avalon Development List <[email protected]>"
           subject="[GUMP] Build Warning - a BuildException happened"/>
</nag>

The current setup is that we only get an e-mail when ant reports a build 
failure, ie the pattern is /BUILD FAILED/i.

cheers,

- Leo

Berin Loritsch wrote:
> Buildfile: build.xml Caught exception 
> (org.apache.tools.ant.BuildException) while expanding tools.class.path: 
> /home/rubys/jakarta/avalon/tools/lib not found. dependencies: 
> check-environment: framework-warning: compile: [mkdir] Created dir: 
> /home/rubys/jakarta/avalon-excalibur/lifecycle/build/classes [javac] 
> Compiling 4 source files to 
> /home/rubys/jakarta/avalon-excalibur/lifecycle/build/classes 
> prepare-conf: [mkdir] Created dir: 
> /home/rubys/jakarta/avalon-excalibur/lifecycle/build/conf [copy] Copying 
> 1 file to /home/rubys/jakarta/avalon-excalibur/lifecycle/build/conf jar: 
> [mkdir] Created dir: 
> /home/rubys/jakarta/avalon-excalibur/lifecycle/build/lib [jar] Building 
> jar: 
> /home/rubys/jakarta/avalon-excalibur/lifecycle/build/lib/excalibur-lifecycle-20030312.jar 
> main: BUILD SUCCESSFUL Total time: 3 seconds
> 
> Build was successful, but a BuildException happened.
> 
> We were not nagged or notified.  :/