You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

README-1.6.10.adoc 2.1KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950
  1. = AspectJ 1.6.10
  2. _© Copyright 2010 Contributors. All rights reserved._
  3. The full list of resolved issues in 1.6.10 is available
  4. https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;bug_status=RESOLVED;bug_status=VERIFIED;bug_status=CLOSED;product=AspectJ;target_milestone=1.6.10;target_milestone=1.6.10M1;target_milestone=1.6.10M2;target_milestone=1.6.10RC1[here]
  5. _Release info: 1.6.10 available 17-Nov-2010_
  6. == Changes
  7. 1.6.10 is primilarily just bug fixes for AspectJ, mainly in the areas of
  8. ITDs and generic aspects. However, there are a couple of important
  9. changes that users ought to be aware of:
  10. === AJDT Memory usage
  11. Type demotion has been in use during loadtime weaving for a while now,
  12. this enables the load time weavers to discard state and recover it at a
  13. later time (and so generally run with a smaller memory footprint). Type
  14. demotion is now supported under AJDT in Eclipse and will enable AJDT to
  15. run with smaller heaps. This feature is still experimental and needs
  16. turning ON if you want to try it out. To turn it on, open your AspectJ
  17. project properties in eclipse and in the AspectJ Compiler section,
  18. scroll down to 'Other' and in the non-standard compiler options setting,
  19. specify:
  20. [source, text]
  21. ....
  22. -Xset:minimalModel=true,typeDemotion=true
  23. ....
  24. If I can get enough positive feedback about this option, it will be made
  25. the default. For a more detailed write up, check out the blog post:
  26. http://andrewclement.blogspot.com/2010/07/ajdt-memory-usage-reduction.html
  27. === Runtime changes
  28. A big thank you to Abraham Nevado and his team who have been working on
  29. some issues to optimize loadtime weaving and the code generated by
  30. AspectJ. 1.6.10 includes some new changes to the aspectjrt.jar. The
  31. changes are new methods that enable the woven code to be a little
  32. shorter/neater. As we want to continue to have compatibility with older
  33. aspectjrt.jar a user needs to choose to activate these optimizations by
  34. specifying the option: -Xset:targetRuntime1_6_10=true. With that option
  35. on you will need to ensure you run against the aspectjrt.jar from a
  36. 1.6.10 build.
  37. The changes are discussed in
  38. https://bugs.eclipse.org/bugs/show_bug.cgi?id=323438[bug 323438]