Hey Paul, > On 11 Nov 2014, at 8:55 am, Paul Bakker <[email protected]> wrote: > > One thing to consider is that although DM 4 is a major version bump, it so > far seems to be very close to a drop-in replacement of DM 3. Changing the > API itself would break all existing code. This is technically ok for a > major version, but will make adoption of the new version a lot slower.
So far our approach has been to fix the things we really wanted to fix but leave everything we don’t need to change as is, exactly because of the reason you mention. We want people to move to the new release as painless as possible. > On the other hand, I do like the proposal :-) Maybe it's possible to add a > new API, while keeping the existing one. E.g. introduce a builder class > specifically for this reason, user can than gradually move towards the new > API. Potentially there could even be builders for multiple JVM languages, > leveraging the DSL functionality of language Groovy etc. I like this suggestion, like I stated in my previous mail it might require wrapping a few classes but it’s definitely doable and probably a good way to get some experience under our belts with this approach. Greetings, Marcel
