Or you could try something total different like providing a stable API of your library while providing two adapters for Vadin6 and Vadin7, so you have myvadin-api -> myvadin6-impl -> myvadin7-impl and let the user of your library choose during runtime whether they want to use vadin 6 or 7. This is an approach used by slf4j, e.g.
Regards Mirko On Mon, Apr 16, 2012 at 20:12, Wayne Fay <[email protected]> wrote: >> Eventually, I'd like to release a proper 1.0. That's the whole idea. How >> can we keep a consistent version scheme in such a case? > > Another approach I've seen (and generally like) incorporates the API > number in the artifact id itself and not as part of the version. I see > this as being a superior option to the 0.6 vs 0.7 option. > > Then you could have util_vaadin6 version 1.1 and util_vaadin7 version > 0.9 and could release bug fixes as needed. > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
