Hi Daniele, Me and later Eike explained to you in the other thread you started few months ago how to solve exactly this problem. It seems you didn't read it at all. Please read again the part mentioning Wicket 1.5 RC1.
On Mon, Apr 25, 2011 at 6:30 PM, Daniele Dellafiore <[email protected]> wrote: > I did it. Yes, the tough way but I did it. > Now the 1.5RC3 quickstart app just started on my karaf 2.2 with the > 1.5-SNAPSHOT I built. > > Basically I renamed the .util and .request packages in -core bundle to be > .core.util and .core.request. > I had to make a class public in another package under -request bundle to > make it visible, but it's a minor thing. > > I open a bug on jira now... wow, is down :) well, as soon as it get back > online. > > On Mon, Apr 25, 2011 at 4:03 PM, Daniele Dellafiore > <[email protected]>wrote: > >> it is not. >> >> I'm hacking on the trunk to make that work. >> Maybe a quick solution is just change org.apache.wicket to >> org.apache.wicket.core in the -core bundle. >> >> Of course there are some default scope classes that works through different >> packages but I can just make them public for now. >> >> On Mon, Apr 25, 2011 at 3:18 PM, James Carman >> <[email protected]>wrote: >> >>> On Mon, Apr 25, 2011 at 10:15 AM, Daniele Dellafiore <[email protected]> >>> wrote: >>> > >>> > I think that the wicket package layout should be changed now that -util >>> and >>> > -request bundles have been detached from -core. >>> > >>> >>> From an OSGi perspective, we should probably try to make sure that >>> packages don't span jar files. Everything in >>> org.apache,wicket.request should be in wicket-request.jar, for >>> example. I don't know if that's the case, currently or not. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
