Hey Brian, Sorry for the short answer but I'm more the kind of early bird, so no longer in front of my PC.
Just one point here: y do you think that? The plain api in the api package does not really depends on wicket. The util and the internal part will be splitted into the impls (and the inject components). I have not tried by now but I don't see any problems. Afaik without the code in front of me the api is only dependent on the page class which is not likely to change and mount part will be splitted. Anything i've missed? Btw, no problem at picking it up! Just thought it would be easier after 0.8 is finished :-) I'll write a full answer in about 6 hours after a little bit of sleep :-) Kind regards, Andreas On Jul 27, 2011 9:18 PM, "Brian Topping" <[email protected]> wrote: > Hi Andreas, > > On Jul 27, 2011, at 1:03 AM, Andreas Pieber wrote: > >> wicket-bundle-parent as osginized wicket (removed from service) >> pw-api >> pw-14-impl >> pw-15-impl >> pw-spring >> pw-aries >> pw-osgi (to come) >> pw-geronimo (to come) > > Ok, unless I'm missing the boat, this won't work. Problem is a bunch of the API interfaces depend on Wicket, which of course is going to vary between implementations. > > Since it doesn't make a lot of sense to have separate API projects, I'm going to duplicate them across the implementation projects until we have a chance to consider it more completely. > > I just found the IRC channel, will be on there as I can... > > :B
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
