Hi Martin, thanks for your response and no need to apologize! It's good to have rcX candidate releases to play with so issues can be found.
For me a wicket-osgi dependency would be great! And I really don't care about where to download :) I don't think that providing it from wicketstuff would bother users... If you decide to not support osgi out-of-the-box, it's still no problem to create an aggregate jar myself. I'd think most osgi users have to do this (unfortunately) quite often to add other "no-bundle-jars". But with a distributed jar, it's of course a lot easier - I would appreciate it (as probably other osgi users would). regards, Eike On [Tue, 15.03.2011 20:43], Martin Grigorov wrote: > Hi Eike, > > Sorry that we broke OSGi support again. > The problem was that many users wanted -sources and -javadoc for the > aggregate .jar and it became a bit complex and confusing. > > I think we can add wicket-osgi project in wicketstuff/core repository that > will do the same we did initially in WICKET-3088 and then you will use > org.wicketstuff:wicket-osgi dependency instead. We release wicketstuff core > projects few days after Wicket releases. > > Other opinions/suggestions ? > > martin-g > > On Tue, Mar 15, 2011 at 3:05 PM, Eike Kettner <n...@eknet.org> wrote: > > > Hi, > > > > I'm using wicket 1.5-RC1 in an OSGi container. There was an issue when > > upgrading related to package names > > (https://issues.apache.org/jira/browse/WICKET-3088) > > > > Now I tried upgrading to 1.5-rc2 and found that there is no aggregate > > jar file anymore. I then read the discussion-thread "[discuss] How to > > resolve wicket aggregate classes / sources jar issues". > > (nabble: > > > > http://apache-wicket.1842946.n4.nabble.com/discuss-How-to-resolve-wicket-aggregate-classes-sources-jar-issues-td3234420.html) > > As it states, the aggregate jar has been removed from the wicket > > distribution. Now, this introduces the very same issues described in > > WICKET-3088 again. > > > > While I can just repackage wicket myself and create a aggregate jar to > > feed the osgi container, it is first more inconvenient :) and secondly, > > there is then no real reason to have the wicket-xxx jars export > > packages, as they won't work in an OSGi container one by one anyways. I > > cannot add all single jars to the osgi container, because of the clashes > > in export-package. > > > > so in summary, there is another use case where the aggregate jar is > > really helpful: when using wicket with osgi. But it only is, because > > the single wicket jars export the same packages (for example, > > wicket-request and wicket-core both export > > org.apache.wicket.request.handler). > > > > Are there any thoughts of adding this aggregate jar to the distribution > > back again? > > > > kind regards, > > eike > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > -- > Martin Grigorov > jWeekend > Training, Consulting, Development > http://jWeekend.com <http://jweekend.com/> -- email: e...@eknet.org https://www.eknet.org pgp: 481161A0 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
