+1 for option 2) with a note in the docs that it works only with Weld for now
On Mon, Apr 16, 2012 at 10:40 PM, Igor Vaynberg <igor.vaynb...@gmail.com> wrote: > we would like to merge wicket-cdi [1] into wicket-core. there is, > however, a problem. in its current version CDI does not provide an SPI > for controlling conversational scope, this will be part of the next > major version of CDI. for now, wicket-cdi depends on > seam-conversations JBOSS module which provides plugins for controlling > conversational scope across various CDI implementations. the problem > is that this module is not available in maven central, so we cannot > publish wicket-cdi there as well. > > when and if JBOSS decides to push this module into central is unknown. > > here are our options > > 1. do not merge wicket-cdi until seam-conversations is available in > central. may be never. currently wicket-cdi is available through a > custom groupid in central, but it is not exactly kosher because of the > same problem and can possibly be removed by maven folks in the future. > > 2. merge it into wicket and drop support for every CDI container other > than JBOSS Weld, which is the reference impl and is probably the most > widely used. > > 3. same as two, but rename the module to wicket-cdi-weld. when next > CDI version comes out, or when seam-conversations becomes available in > central we will rename the module back to wicket-cdi. > > -igor > > > [1] https://github.com/42Lines/wicket-cdi > [2] http://search.maven.org/#browse%7C-1741695030 -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
