This was the first distributed release. It's was usable only from ant. It's core implemnetation was using jmock. The interface was unstable. purpose was to allow the user community to evalute the potential of nextMock, and to provide early feed back. It will be usuable in a limited set of configuration (ant). We hope to receive feedback on its interface.
The major changes are : - Maven integration. - Usage of .nextMock property files instead of having the information into the build script
The core implementation still rely on jmock. The complete API is not yet finalyzed.
Depending on the received feedback we will release one or more 0.x version to test adaptation to the API.
This release should incorporate the final API, the ant task and the maven plugin should be finilized.
We will decide to have one ore more alpha-x releases in function of the stability.
This version will be the stable release that includes the final API, the ant task and the maven plugin.
This version will be the base of the simple IDE plugins suportting the code generation but not yet the refactoring.
This version will includes some generic suport for refactoring. To suport refactoring, we need a series of classes adapting user refactoring request on a mock into a real refactoring performed on the mockable class.
The path to go from 1.0 to 2.0 is not yet defined. It will probably be done in parallel with IDE plugins development.
The IDE plugins will be released independently of the nextMock core.
However, both IDE plugins and nextMock version should be linked. We will take the convention that the IDE plugins with version number 1.x use the 1.0 (or 1.y) core version. Those versions will suport the mock generation, but not yet the refactoring.
The IDE plugins that suport refactoring will have to use the 2.0 (or 2.y), and will be numbered 2.x.