MyBatis Generator Eclipse Feature Release Notes
Version 1.4.2
- Removed Log4J Version 1.x from the UI.
- The Generator feature now requires a Java 11
- The Java merger now supports up to Java 16
- The minimum Eclipse version is now 4.20 (2021-06)
Version 1.4.1
- Removed Log4J Version 1.x support in the Ant logger configuration.
- The Java merger now supports Java 11
- The minimum Eclipse version is now 4.10 (2018-12)
Version 1.4.0
- Added an environment tab to the launch configuration where properties can be set. Properties set on this tab will be available
for substitution into the generator configuration file.
- Eclipse Oxygen (platform version 4.7.3) or higher is required
- Java version 8 or higher is required
Version 1.3.6
- The popup menu item for running the generator is removed. The generator can be run with a launcher,
or via the integrated ant task.
- Support for generator logging has greatly improved, and the Ant task and the UI have been updated to allow selection
of a specific logging implementation if runtime classpath inspection yields a different implementation
than desired.
- The launch is more verbose in the console, so it will be easier to see what the results of the launch are
- New launch configurations will now include the enclosing Java project in the launch classpath. This is
in keeping with eclipse conventions
- Fixed bug where the DTDs were missing in the XML catalog
Version 1.3.5
Bug fix release in MyBatis Generator core only
Version 1.3.4
Important Note: After this release, we will remove the popup menu item for
running the generator. Please begin using the launch configuration support
instead.
- Add a launch configuration to run the generator
- Add the generator DTDs to the XML catalog
Version 1.3.3
- Update the feature build to run with Eclipse Tycho (Maven)
Version 1.3.2
- Issue #588 - support enums in the Java file merger
- Issue #607 - support generic types for rootInterface and rootClass
- Issue #453 - support Annotations in the Java merger. Thanks to Thomas Neuberg
for the awesome patch!
Version 1.3.1
- Renamed MyBatis Generator. Changed name of ant task. Removed classpath
variables.
Version 1.2.2
- Upgraded to Ibator Version 1.2.2
- Fixed divide by zero error when there are no tables that match
the configuration
- Changed build process to use PDE Headless build. The Ibator feature now includes source bundles
for all plugins! Also, the feature is now well behaved according to Eclipse
standards (no bundle is unpack upon install).
- Enhanced the classloading strategy for generating iBATIS artifacts from the popup menu.
Ibator will now find resources and JAR files in project where the configuration file
lives if that project is a Java project.
- Changed classpath variable IBATOR_JAR to IBATOR_HOME
- Changed classpath variable IBATOR_JAR_SRC to IBATOR_SRC_HOME
Version 1.2.1
- Upgraded to Ibator Version 1.2.1 - this will fix the issue where Ibator is ignroing
the Ant classpath set in Eclipse Ant launch configurations.
- Fixed an issue with the JavaFileMerger where it fails if the workspace
gets out of sync with the file system
- Added IBATOR_JAR classpath variable
- Added IBATOR_JAR_SRC classpath variable
- Added menu option to add Ibator to the build path of any Java project
- Added list of manual test scripts to the documentation to help in the
release process, and also to show the intended usage of the UI features.
Version 1.2.0
- As of version 1.2.0, Abator is renamed to Ibator
- Upgraded to Ibator Version 1.2.0
- Upgraded to Eclipse version 3.4.1
- Removed the integrated editor as far better XML editors are available for
free
- Removed the classpath variable for Ibator - use the Ibator JAR instead
- Restructured the plugins to separate UI from core function
Version 1.1.0
- Upgraded to Abator Version 1.1.0
- Upgraded to Eclipse Version 3.2
- The Java merge function will now use the code formatter options
from the workspace
- The integrated Ant task accepts additional properties to
match the Ant task in base Abator. See the
Using the Integrated Ant Task page for more
information.
- The integrated editor is now associated with any Abator configuration
file regardless of the filename.
Version 1.0.0
- Upgraded to Abator Version 1.0.0
- Upgraded to Eclipse Version 3.1
- The Java file merger now fully supports JSE 5.0
- Fixed bug where multi-segment source paths failed
- Use an adaptable type to associate Abator configuration files with the
popup menu items instead of content type. This should resolve conflicts
with other plug-ins like oXygen
- The built-in Ant task now accepts a nested Ant <propertyset>
to allow passing properties into an Abator configuration file.
Version 0.6.5
- Upgraded to Abator Version 0.6.5
- Changed EclipseShellCallback so that different source folders can be specified
Version 0.6.2
- Made our content type high priority to avoid conflicts with other XML
enabled plug-ins
Version 0.6.1
- Upgraded to Abator Version 0.6.1
- Added an Eclipse enabled Ant task