On Aug 16, 2011 6:11 PM, "Charles Moulliard" <[email protected]> wrote: > > Hi Andreas, > > From an OSGI perspective, the approach option 3 (and also for J2EE users) is > the best as it simplifies the build, release and deployment process and > avoid dependencies issues.
I also think so. > Additional question : In which bundle will be packaged the wicket-extensions They could be either in the wicket-core bundle, an own bundle or in the bundle created by option three. All three options has there advantages and disadvantages. IMHO this depends on the package solution. In case of option 1 or 2 wicket-core makes sense. In case of option 3 I think wicket-osgi makes most sense. Kind regards, Andreas > ? > > Regards, > > Charles > > -- > View this message in context: http://apache-wicket.1842946.n4.nabble.com/Restructure-Packaging-for-OSGi-tp3746217p3746435.html > Sent from the Forum for Wicket Core developers mailing list archive at Nabble.com.
