2014-09-17 14:42 GMT+04:00 <build...@apache.org>:
> The Buildbot has detected a new failure on builder tomcat-7-trunk while
> building ASF Buildbot.
> Full details are available at:
> http://ci.apache.org/builders/tomcat-7-trunk/builds/296
>
> Buildbot URL: http://ci.apache.org/
>
> Buildslave for this Build: silvanus_ubuntu
>
Several notes
1. Tomcat 7 builds have been moved to a different slave, "silvanus_ubuntu"
2. I tested that I have commit right for buildbot configuration and
was able to fix misconfiguration of Ant.
The symptoms were that "ant release" command silently failed with exit
code 1 and no output.
I think the cause was that Buildbot configuration for Tomcat 7 used
tildes in the values of variables, e.g. "ANT_HOME=~/tools/ant/current"
and "JAVA_HOME=~/tools/java/latest1.6".
Replacing "~/" with "${HOME}/" helped.
My guess is tilde expansion is a feature of shell and is not supported
in the value of java CLASSPATH. So when Ant built classpath from those
values Java was not able to load those libraries. Though I wonder why
it failed with no error output.
> Build Reason: scheduler
> Build Source Stamp: [branch tomcat/tc7.0.x/trunk] 1625506
> Blamelist: violetagg
>
> BUILD FAILED: failed compile
3. Compiling of Tomcat code succeeded.
It fails at "extras-commons-logging" compiling step.
My guess is that using a relative path as "base.path=../basepath" is
no good for extras.
E.g. Avalon was downloaded, but then it failed to find it:
[[[
[echo] *** WARNING ***
[echo] Avalon-Framework not found: Cannot Build AvalonLogger
]]]
At the same time, Tomcat's own code did build successfully.
So either there is a way to fix extras to build with such paths, or
one needs to update Buildbot configuration to use an absolute path for
"base.path".
Best regards,
Konstantin Kolinko
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
