After following the instructions, and trying to run the AopC ant task, I constantly get the following error:
BUILD FAILED: C:\eclipse\workspace\myproject\build.xml:309: java.io.IOException: CreateProcess: <lots removed> After much debugging, I have come to the conclusion that the issue stems from a physical limit to the length that a forked-java command can be. See, when I run the command at the command line with my src dir of my classes being './bin' -- it works fine. However, looking at the code for the AopC and task, it walks through every single directory and appends every single class to compile at the end of the command. Well, it my case, that generates a String that is ~40k chars long (~200 classes with fullpaths is long!) -- and that is *after* the java command. That is just the length of all of the files it wants to AopCompile. In fact, the command is so long, that I cannot run it at a command promt (WinXP), as it truncates there as well. Now, when stepping through the debugger for the ant task, and telling it to not fork the command, it works fine as well. So, is there a reason why the Ant task must list every single file, when the Aop standalone compiler is happy to except a directory? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3851780#3851780 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3851780 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
