10-07-2011 11:14 AM
I have a very large project that I'm trying to compile, but it's failing because the command line when rapc invokes javac is too long. I'm getting an IOException from rapc, which goes away if I remove a small number of source files or make the paths to the source files shorter (eg, by shortening a package name)
My ant build script uses the generateSourceList="true" attribute for the <rapc> task, which means that instead of passing a huge command line to rapc, only an @sources.txt file is included, which contains a list of all the source files. However, when rapc invokes javac, it does not use a sources file; it always puts the source files on the command line, which causes it to fail.
Has anyone come across this before? Any workarounds? I've tried compiling my source manually via javac and jar before passing it in to rapc, so that I wouldn't have to use a long list of sources in rapc, but since I use resource files I can't call javac before rapc does its code generation stage.
10-11-2011 10:24 AM
03-23-2012 07:03 PM
I am also having the exact same problem. By turning on the verbose option for rapc, I can see that it's just generating a command line with absolute paths to each one of my source files. Which, since I have a couple hundred source files, and they're pretty deep in my file structure (thanks ClearCase!), means that this command line is something like 10K long, which Windows is just unwilling to deal with.
If it matters I'm using version 5 of the component pack, where rapc is coming from; upgrading to version 7 is not an option right now.
03-23-2012 11:47 PM