Summary: | -Xmx256M not implemented? | ||
---|---|---|---|
Product: | [Tools] AspectJ | Reporter: | Michael McConnell <mcconnellem> |
Component: | Compiler | Assignee: | Adrian Colyer <adrian.colyer> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | critical | ||
Priority: | P3 | ||
Version: | 1.2 | ||
Target Milestone: | 1.2.1 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Michael McConnell
2004-06-16 15:15:33 EDT
correction -- "-Xmn256M" WAS ACTUALLY SPECIFIED AS "-Xmx256M" sorry. -Michael For the AspectJ compiler in eclipse to have more memory available, you should start the eclipse jvm with more memory eclipse -vmargs -Xmx256M --- For the command line compiler, you should look in the script that kicks off the compiler, either 'aj.bat' on windows or 'aj' on unix. Inside the script you will see a call to java that sets Xmx to 64M, increase that to 256M. --- It wouldn't be any good for the compiler code to process it as an option because by then the JVM has started and Xmx has been decided. Hopefully the above info helps you get it going :) I believe I have had an email exchange with Michael confirming this worked for him (I just cant find it in my inbox - doh!). Fix released as part of AspectJ 1.2.1 |