On Fri, Sep 21, 2012 at 11:51 PM, Bruno Borges wrote:
> Well, can't tell that wicket-cdi is a "new feature" to Wicket, as it is a
> separate module, and I don't think there are dependent changes on Wicket's
> core.
>
> We can run wicket 6.0.0 with wicket-cdi. The only issue here is that it is
> in
Well, can't tell that wicket-cdi is a "new feature" to Wicket, as it is a
separate module, and I don't think there are dependent changes on Wicket's
core.
We can run wicket 6.0.0 with wicket-cdi. The only issue here is that it is
in a different groupId (thanks Igor and 42lines).
So how about that
6.0.1, if released, cannot contain any new features, only bugfixes, as
dictated by semver. wicket-cdi will be part of 6.1.0.
Best regards,
Emond
On Fri, Sep 21, 2012 at 10:41 PM, Bruno Borges wrote:
> I'd like to have a 6.0.1 release, just because of wicket-cdi officialy on
> its distribution.
>
Hi,
I just set several tickets to have Fix Version 6.1.0. I think they
deserve to be fixed before the next release.
Some of them are trivial and have either patches or proposed solutions.
On Fri, Sep 21, 2012 at 11:29 PM, Emond Papegaaij
wrote:
> Hi all, especially Martijn,
>
> Martijn, you prop
I'd like to have a 6.0.1 release, just because of wicket-cdi officialy on
its distribution.
*Bruno Borges*
(11) 99564-9058
*www.brunoborges.com*
On Fri, Sep 21, 2012 at 5:29 PM, Emond Papegaaij wrote:
> Hi all, especially Martijn,
>
> Martijn, you proposed to build 6.1.0 today. I know you p
Hi all, especially Martijn,
Martijn, you proposed to build 6.1.0 today. I know you probably won't
get to it today and I also think it's better to give people a few more
days to fix urgent tickets. 6.0.1 still has 2 major unresolved
tickets. Given the fact that everyone voted for 6.1.0 to be the ne
