Is BasePage in your webapp module and you have other pages in other modules? If so, you're going to have a circular dependency. What you could do is set up a web-commons module which contains stuff like BasePage and have your other modules use that. Then, your web module declares all of them as dependencies. That's what we do.
On Tue, Oct 13, 2009 at 3:36 PM, Ben Tilford <[email protected]> wrote: > Something other than? > <dependency> > <groupId>org.apache.wicket</groupId> > <artifactId>wicket</artifactId> > <version>${wicket.version}</version> > </dependency> > > > > On Tue, Oct 13, 2009 at 3:30 PM, Igor Vaynberg <[email protected]>wrote: > >> your module still needs a wicket dependency >> >> -igor >> >> On Tue, Oct 13, 2009 at 12:20 PM, Ben Tilford <[email protected]> >> wrote: >> > Are there any examples of a modular wicket application? I'm specifically >> > having trouble getting maven to compile a jar which contains a sub-class >> of >> > WebPage. >> > >> > Using 1.4.2 and have attempted with 1.4.1/1.4.0, packaging a Panel etc... >> > all seems to work fine. >> > >> > demo/locator/web/components/BasePage.java:[17,8] cannot find symbol >> >> symbol : method add(org.apache.wicket.markup.html.basic.Label) >> >> location: class demo.locator.web.components.BasePage >> >> >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
