Looks like you have an project dependency compiled with other Wicket version. That can to be easy detected with eclipse maven pluging, using the hierarchy view
On Tue, Oct 13, 2009 at 4: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] > > > > > -- Pedro Henrique Oliveira dos Santos
