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
> 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
Wayne
On Mon, Apr 16, 2012 at 7:10 PM, Wayne Fay wrote:
> > * 0.3 is Vaadin 6-based, 0.4 is Vaadin 7-based, 0.5 is Vaadin6-based,
> etc.:
> > It's weird because the features of the library should be exactly the
> same
> > (the only difference is the underlying API that is being used)
>
> How abo
> * 0.3 is Vaadin 6-based, 0.4 is Vaadin 7-based, 0.5 is Vaadin6-based, etc.:
> It's weird because the features of the library should be exactly the same
> (the only difference is the underlying API that is being used)
How about 0.7 becomes Vaadin 7-based?
Not sure what happens when Vaadin 10.x
Hi,
I am having this question for another project I am working on and since it
(obviously) uses Maven, I wonder if I could collect some feedback over
here. It's halfway between user and dev. Apologizes if I sent to the wrong
list :)
Assume a projet providing a library utility over a framework (he
