wicket-cdi is more mature, imo it may be included directly with 6.x version
but I think that new modules like wicket-atmo can have their own release cycle until they are included in the big group. there is no reason why wicket-atmo:0.2 should wait for 6.0.0-beta3 but of course this will add some more pain in the release process On Tue, May 15, 2012 at 4:30 PM, Igor Vaynberg <[email protected]> wrote: > if the whole idea is to release these modules why move wicket-cdi in > there and disable its releasing? > > -igor > > On Tue, May 15, 2012 at 12:51 AM, Martijn Dashorst > <[email protected]> wrote: >> On Tue, May 15, 2012 at 9:43 AM, Martin Grigorov <[email protected]> >> wrote: >>> the broken module is not in the staging repo. i.e. there wont be >>> 0.1-SNAPSHOT in Maven central >> >> The whole idea is that we release these modules as part of our normal >> releases to give them exposure. Therefore rerolling the release with >> proper 0.1 versioning for the experimentals is necessary IMO. >> >> Martijn -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
