The goal of this project is to build a set of tools that makes it possible to move between a UML model and Java source code during development without having to update duplicated information by hand.
Be the first to post a text review of Java Roundtrip Engineering. Rate and review a project by clicking thumbs up or thumbs down in the right column.
Java Roundtrip Engineering Toolkit Release Notes RELEASE 0.3.1 ============= Improvements - No improvements. Fixed Bugs - The reserved word strictfp is parsed, but still ignored. Known Bugs See Bug Tracking at SourceForge. RELEASE 0.3.0 ============= Improvements - Modeling and generation of javadoc comments. They are modelled ArgoUML style, with a tagged value named "javadocs". Fixed Bugs - Generation of duplicated abstractions for classes that implements more than one interface fixed. Known Bugs See Bug Tracking at SourceForge. RELEASE 0.2.0 ============= Improvements - Alpha release of the tool UML2Java. This tool can generate and update java source code from an UML model. Fixed Bugs - Anonymous inner classes inside other inner classes was searched for with the wrong classname when modelling. - Abstract classes was not modelled as such. - Inner classes was not removed from the model when removed from the source. - The parser could fail on array initialization code. Known Bugs - The "strictfp" keyword is not recognized by the parser. - The reserved words "goto" and "const" are parsed as identifiers. - Import statements are not generated. - If a class is moved from the package with no name to a package with name, the package statement will not be inserted in the sourcefile, nor will the sourcefile be moved in the filesystem. - Updating code where multiple attributes are declared in the same statement does not work properly. Write each attribute declaration in a separate statement. - If one type is fully qualified in an operation declaration, all types in that operation are generated fully qualified when updating. - JavaRE works best if only one class exists in a file. - Methods with the same name have to be in the same order in the model and in the source code. (No parameter signatures are checked.) - If the superclass or interface of an anonymous inner class is changed in the model, the source code is not updated to reflect this. RELEASE 0.1.5 ============= Improvements - Modelling inner classes correctly. Fixed Bugs - The parser can now handle calls to outer classes. - The parser can now handle boolean.class.equals(). - The false reserved word "threadsafe" removed. Known Bugs - The "strictfp" keyword is not recognized by the parser. - The reserved words "goto" and "const" are parsed as identifiers. - Even though some code in the package uml2java exists, it is not finished and is not expected to be usable for anything. RELEASE 0.1.4 ============= Improvements - No improvements. Fixed Bugs - Modelling of method overloading fixed. - No return parameter set for constructors. Known Bugs - Even though some code in the package uml2java exists, it is not finished and is not expected to be usable for anything. RELEASE 0.1.3 ============= Improvements - Constructors are modelled. Fixed Bugs - No more problems with ArgoUML diagrams, since UUID is added to packages. Known Bugs - Even though some code in the package uml2java exists, it is not finished and is not expected to be usable for anything. RELEASE 0.1.2 ============= Improvements - The model generation is more complete. - It is possible to build with Ant. - Javadoc documentation is available. Fixed Bugs - Generalizations and abstractions<<realize>> are not duplicated anymore. Known Bugs - If a model is created from scratch, it is not possible to add diagrams in ArgoUML. Solve it by starting with an empty model created by ArgoUML. - Even though some code in the package uml2java exists, it is not finished and is not expected to be usable for anything. RELEASE 0.1.1 ============= Improvements - Minor Makefile updates. - Removed unneccessary printout. Fixed Bugs - No fixed bugs. Known Bugs - If a model is created from scratch, it is not possible to add diagrams in ArgoUML. Solve it by starting with an empty model created by ArgoUML. - Generalizations and Abstractions are only identified by name. They can be duplicated in the model. RELEASE 0.1.0 ============= Improvements - The tool Java2UML converts Java source code to UML models. Fixed Bugs - No fixed bugs. Known Bugs - If a model is created from scratch, it is not possible to add diagrams in ArgoUML. Solve it by starting with an empty model created by ArgoUML. - Generalizations and Abstractions are only identified by name. They can be duplicated in the model.
Be the first person to add a text review.
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?