Eduardo- AFAIK, the behavior you are seeing is the behavior of javac, not Maven. As you note, the Eclipse compiler does something different, so if that's the behavior you want, use the Eclipse compiler.
Justin On Fri, Jan 29, 2010 at 8:21 AM, Eduardo M KALINOWSKI < [email protected]> wrote: > On Sex, 29 Jan 2010, Christoph Kutzinski wrote: > >> Sounds to me like you should modularize the application, make a >> multi-module project of it (if not already) and then add only those modules >> on which you're working currently to the <modules> section of the parent POM >> and leave out all the others for the moment. >> Just a quick idea from the top of my head. >> > > It is already a multi-module application. Some modules are OK, but the > problems I'm referring to happen in only one of the modules (well, two > actually). > > > The alternative you mentioned - try to compile everything and just hope at >> runtime that all currently needed functionality is working - sounds >> inherently dangerous to me. >> > > Yes, it is dangerous. But it works fine when building with Eclipse. > Apparently Eclipse does just that, compiling what can be compiled and > including that in the final war (or whatever else is being generated). > > > > -- > Your mileage may vary. > > > Eduardo M KALINOWSKI > [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
