hi this might be also interesting. I once started a thread in wicket-user mailing list about this problem. (the thread is http://apache-wicket.1842946.n4.nabble.com/wicket-1-5-rc2-and-aggregate-jar-for-osgi-td3356667.html)
I think the conclusion was to build your own wicket bundle as it was distributed with wicket-1.5-rc1. in this release the wicket team created one jar out of core, util and request (as i remember). but future releases won't distribute this anymore. the idea was then to distribute it with the wicket-stuff project... regards, Eike On [Mon, 25.04.2011 18:13], Daniele Dellafiore wrote: > On Mon, Apr 25, 2011 at 5:07 PM, Allen Lau <[email protected]> wrote: > > > I'm jumping in a bit late, but in order to build our wicket app without > > dependencies, we use both the maven-bundle-plugin to generate the manifest > > file first and then have the maven-war-plugin do the packaging of the > > actual > > war. > > > > we use the following lines in the war plugin > > > > <configuration> > > <archive> > > > > > > > > <manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile> > > </archive> > > <packagingExcludes>WEB-INF/spring/**, > > WEB-INF/lib/*.jar</packagingExcludes> > > </configuration> > > > > > > This can works, thanks. > Maybe there is no bnd specific solution for this and we have to use a > "trick" like this one. -- email: [email protected] https://www.eknet.org pgp: 481161A0 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
