version 1.0.2 Bugfixes for * lowercase class names, * merging of similar method names, * the use of filesets from within ANT and * run_junitdoclet_recursive.bat . Updated documentation, especially for integration with ANT and IntelliJ IDEA 3.0. version 1.0.1 Examples show how to add JUnitDoclet as an external tool to your favorite development environment such as Intellij IDEA and Eclipse both on Windows and Linux (please see doc/ide/*) . Accessor methods are handled more strictly to avoid combined test methods for uncommon method signatures that are not straight JavaBeans-type properties (e.g. 'void set()', 'void set(Object, String)', 'String getProperty(int)') Parameter check that source path must not contain output path if subpackage parameter is not set. (Added switch to override this.) Templates changed: createInstance now declares to throw an exception. version 1.0 considered to be the first stable release marker style changed (Now the name of the method under test is part of the marker instead of the test method name. This way tools like IDEA can help you to rename the markers as well when a method is renamed. It is less likely, that any test will be moved to testVault . We apologize for the inconvenience for people, who used a version prior to 1.0. We are sure, they will benefit from that decision soon as well.) loading templates from path (instead of class path) is finally working as well templates for type specific default tests fixed templates for TestCases and TestSuites include main method to execute TestCase or TestSuite template for TestCases contains a method createInstance to be used instead of new ClassUnderTest(); markers for methods to organize tests (like setUp, tearDown, createInstance, testVault or main) look slightly different than markers for ordinary test methods. This way, they don't interfere. unit tests for JUnitDoclet itself following the new style bug with negative index when calling substring is fixed. if the template changed, empty test methods can be overwritten (For example to insert "fail();" into all empty test methods at a time. If a test method should do nothing, type in a comment.) (known) typos in documentation fixed version 0.9.2 can generate tests to sub packages (like "test") now no tests for classes in a set sub package (see above) no tests for classes ending with "Test", "Suite" (even if no sub package is set) no tests for classes implementing junit.framework.Test either direct or in a super class no tests for inner classes at all minor changes in documentation version 0.9.1 new distribution structure handles missing property files correctly version class included is compilable / testable with JUnit 3.5 to 3.8 now (Some problems with String comparison in 3.8 are still unfixed, but there is a Workaround: all TestCases for JUnitDoclet itself are derived from CompatibilityTestCase. Note: This should not be required in your project since you are using one JUnit version only.) included article about JUnitDoclet version 0.9 first public version added parameter -buildall documentation added to few parts of the system (with more to come) version 0.8 added preservation an generation of javadoc comments. version 0.7 added configuration options to set each strategy version 0.6 made all strategies interfaces and provided default implementation for each of them bugfix in template based generation made template based generation the default (and for now only) way version 0.5 added template based generation version 0.4 prints a warning if a test vault method is not empty. version 0.3 markers "extends" and "implements" now melted to "extends_implements" javadocs for test methods are not generated by default version 0.2 markers do no longer include package names marker for "extends" added (therefore calling inherited setUp and tearDown as well) handling of test object moved to default code (so it can be changed) call of super constructor moved to default code (so it becomes modifiable) a few javadoc comments get generated as well version 0.1 initial launch