@James Everything works if I don't have a sub-class of WebPage outside the war project.
@Pedro >From command line or on the parent project I get the same error. Also deleted the org/apache/wicket directory out of my .m2 repository and re-downloaded. On Tue, Oct 13, 2009 at 4:19 PM, Pedro Santos <[email protected]> wrote: > Isn't it the case for you manually run mvn install on your parent project? > Your local repository may have old .class bytecodes > > On Tue, Oct 13, 2009 at 5:11 PM, Ben Tilford <[email protected]> wrote: > > > No base page is in a common module (probably will be used by more than 1 > > app > > in the end). > > > > The wicket dependency is declared in a parent project (I've tried moving > > thinking maybe there was something odd going on there). Using Netbeans I > > can > > see the dependency is resolved and on the classpath. Looking at the > > dependency graph there is only 1 version of wicket in any of the modules > > and > > they all have 1.4.2. I did see a conflict with log4j versions but after > > fixing that I'm still getting the same compilation error. > > > > To me its a bit odd that its the add method of WebPage that can't be > found. > > > > On Tue, Oct 13, 2009 at 4:00 PM, James Carman > > <[email protected]>wrote: > > > > > 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] > > > > > > > > > > > > -- > Pedro Henrique Oliveira dos Santos >
