Does anyone have any experience with a distributed development
environment using Cruise Control to handle central builds? Our
application compiles fine in the IDE, however once we checkin our files
and Cruise takes over we start getting these errors:
"A file found in a source-path must have an externally visible
definition. If a definition in the file is meant to be externally
visible, please put the definition in a package."
The only substantial difference in environments is that the compiling
server is Linux and all the development environments are Windows. My
coworker Andrew just spent a lot of time trying to debug this, and has
narrowed down the following:
> We compared the JDK's on my machine and on Cruise. Mine is version
1.6_01, while Cruise's is 1.6_02. So that is probably not the issue. If
anything, mine should be having issues that Cruise does not. (Author's
note: Mine is 1.6_02 and it works fine)
> We compared the Flex SDK's on my machine and on Cruise, doing a
file-by-file comparison. There is no significant difference. Both of
them are the same version (2.0.1) and have the Hotfix patch.
> I transferred the Cruise Control ant script to my desktop, modified
the file paths appropriately, and ran the compile and compile_demo
targets, and it built successfully. This indicated to us that there is
no problem with the Cruise Control script. In fact, the point of failure
reported by the Cruise Control server is in the compile target.
> As a last resort, we exported the last successful build revision, and
modified the script to build it, and it succeeded. This just indicates
that no Cruise Control server changes have taken place since that
success, and that it is indeed due to the compiler.
I'm afraid the size of the codebase and our confidentiality agreements
prevents me from posting any example code. Nevertheless, I was wondering
if anyone has encountered something like this before: Any suggestions?
Michael Krotscheck
Senior Developer
RESOURCE INTERACTIVE
www.resource.com
[EMAIL PROTECTED]
