Stefano Mazzocchi wrote:
Mikhail Loenko wrote:
[exec] BUILD FAILED
[exec]
/home/hybld/continuum-working-directory/6/classlib/build.xml:113: The
following error occurred while executing this line:
[exec]
/home/hybld/continuum-working-directory/6/classlib/make/build-java.xml:276:
The following error occurred while executing this line:
[exec]
/home/hybld/continuum-working-directory/6/classlib/make/depends.xml:43:
The following error occurred while executing this line:
[exec]
/home/hybld/continuum-working-directory/6/classlib/make/depends.xml:332:
...
[exec] Missing dependency. The jar from:
[exec] http://www.bouncycastle.org/download/bcprov-jdk15-134.jar
how about "ant fetch-depends rebuild" ?
no, more.
"ant distclean fetch-depends build"
I think we need to use CC to do the *exact* steps that a new potential
committer would do.
Actually, not on in one shot, so we can measure the time of each section
over time.
geir
I've setup the harmony build on a lot of machines recently and I found
out that it's practically *never* works just by doing "ant fetch-depends
build". Sometimes it's a DLL missing, sometimes you have to copy a file
and rename it, sometimes you have to get up the chair and do a little
dance... it would be *very* nice if we could make sure the entire
operation, from start to finish, is smooth and works file (more
importantly, it breaks when the jars/dlls we depend on are not there).
Even better would be to install fresh OS images on an hypervisor every
night, test on those and throw away the changes to the OS (so that you
start afresh every night) but that's a story for another day.
Note: the "distclean" ant target does not currently exist, needs to be
implemented.
