JavaRebel Devel Changelog
1.2.1 (24th September 2008)
- Missing dependencies are no longer logged to console to avoid confusion
- Fixed an issue with IBM J9 JVM that resulted in a StackOverflowException on some setups (mainly with IBM WebSphere)
- Fixed a regression on Java 1.4 that resulted in an ExceptionInInitializerError
- Fixed an issue with JAR relative paths
- Fixed an issue with OC4J system classloader
- Fixed an issue with -Drebel.packages loading JARs as (corrupted) classes, could cause ArrayIndexOutOfBoundsException
- SpringSource Application Platform is now supported (see instructions in the installation manual)
1.2-RC1 (15th August 2008)
- Fixed regression in accessing super methods
- Fixed broken setPrimitive() method behavior in java.lang.reflect.Field
- Fixed “native” methods causing a ClassFormatError
- Fixed a error occurring when super classes have a static and non-static field with the same name.
- Added support for time-limited licenses
1.2-M2 (30th July 2008)
- Spring dependency reloading is now available via an external plugin.
- Fixed Reloader.isReloadEnabled() returning true if agent wasn’t enabled, but JavaRebel was in classpath
- Fixed a Java 1.4 incompatibility in javarebel-bootstrap.jar generation logic
- Fixed an infinite recursion on some super calls (http://www.zeroturnaround.com/forum/topic.php?id=87).
- Fixed several possible MethodNotFoundErrors
- Fixed Method.getGenericParameterTypes() returning wrong signature (needed for Spring integration)
- Fixed wrong modifiers returned by Method.getModifier() causing problems with AspectJ (http://www.zeroturnaround.com/forum/topic.php?id=91)
- Fixed a race condition in core logics that could manifest as a NPE.
- Fixed CgLib proxies throwing exceptions on initialization. To enable CgLib proxy bypass “-Drebel.allow_bytecode_proxy=true” should be now added to the JVM command line.
- Fixed some JavaRebel messages (like monitored dirs) not showing up properly.
- Improved reflection correctness and performance.
1.2-M1 (9th June2008)
- JavaRebel SDK. The SDK has been refactored with added functionality for processing class bytecode and managing JavaRebel configuration.
- JavaRebel Plugins. It is now possible to register JavaRebel plugins that can make use of the SDK APIs to integrate with custom containers or frameworks.
- JavaRebel Integration Project. To test the new SDK APIs and plugins we created an open-source integration project and moved almost all of the custom container/framework integration processors there.
- Added support for filtering packages that will be managed by JavaRebel
- Full support for Eclipse plugins (and OSGi bundles generally)
- Initial support for IBM WebSphere, please check the installation manual included in the distribution.
- Integration with Commons-EL, to update metadata when classes change.
See stable changelog.