Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

2011-04-27 Thread Eike Kettner
Hi Daniele, sorry for answering this late, anyways, inline reply. On [Fri, 22.04.2011 16:09], Daniele Dellafiore wrote: Hi, sorry I read your reply only today... I got basically to the same results yesterday, but I've some problem which I summarized in the last message in this thread on

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

2011-04-22 Thread Daniele Dellafiore
Hi, sorry I read your reply only today... I got basically to the same results yesterday, but I've some problem which I summarized in the last message in this thread on felix mailing list: http://old.nabble.com/A-better-life%3A-quick-webapp-deploy-to31334158.html I'll go into details point by

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

2011-04-08 Thread Eike Kettner
Hi Daniele, I might have not understood your concern well enough... But here is what I do: I deploy a really small war file (without any deps of course) into the osgi container (I use felix...). There is another bundle from pax, called pax-web-extender, that listens for war files coming into the

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

2011-04-06 Thread Daniele Dellafiore
I'd really like to start my wicket app in a osgi (karaf) container. My app uses also wicket-spring. What is the best way to do that now, with wichet 1.5 rc3? Thanls. On Wed, Mar 16, 2011 at 2:25 PM, Michael O'Cleirigh michael.ocleir...@rivulet.ca wrote: Hello, The way releases have been

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

2011-04-06 Thread Martin Grigorov
See RC1 o.a.w:wicket:pom.xml You'll need to create your own project that will combine the all needed .jars as we did in RC1. On Wed, Apr 6, 2011 at 2:51 PM, Daniele Dellafiore dani...@dellafiore.netwrote: I'd really like to start my wicket app in a osgi (karaf) container. My app uses also

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

2011-04-06 Thread Daniele Dellafiore
mmm, can't really understand. Anyway, I wanted to add that the point here is to deploy a jar on karaf, not a war. To be honest, the real advantage is to deploy a small jar on karaf that is far better than a heavy war on a jee container. My idea is to have karaf with all the wicket, spring and

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

2011-04-06 Thread Martin Grigorov
I'm not an OSGi user but here is what I'll do. 1) create a new Maven project with packaging type 'pom' 2) combine all wicket jars in one (uber-jar) there are several approaches here: 1) maven-shade-plugin 2) the way we did it in RC1 with maven-dependency-plugin: see

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

2011-04-06 Thread Daniele Dellafiore
yes the idea is not to have the huber jar, it's all about this, is the main feature :) some guys in the felix maling list suggested me that's actually possible and supported, it's called WAB, that's a war without /lib (a partially reverse recursive achronim for A Better War)

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

2011-03-16 Thread news
ok, I can take the pom from rc1 and adopt it for rc2 - shouldn't be problem since you did the work already. If it works and I find some time I'll try with github thanks and regards, eike On [Tue, 15.03.2011 22:10], Martin Grigorov wrote: Well, wicketstuff is hosted at GitHub and any user can

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

2011-03-16 Thread Michael O'Cleirigh
Hello, The way releases have been working is that I take the current HEAD and then change the wicket.version to the current stable and the pom version to the next release. If you can commit your changes onto the master branch (wicket 1.5-SNAPSHOT) then I can create a new 1.5-rc2.1 point

Fwd: wicket 1.5-rc2 and aggregate jar for osgi

2011-03-15 Thread Martin Grigorov
Well, wicketstuff is hosted at GitHub and any user can contribute. If you have some time and willing to share your work with the community you can do it yourself. Otherwise just create a ticket in wicketstuff's issue tracking system and someone of us will do it when we have some time. Thanks for