A few suggestions, I'm sure there are other ways to do it too but these come to mind immediately:
1. Reorganize your generic library 2. Use dependency:unpack, find the problem classes, and replace them with ones from the WAR. You will probably also bundle the generic library directly in your WAR rather than a normal Jar <dependency> so unpack directly into target. 3. Use dynamic interfaces and load the proper (replacement) versions when you're in the WAR context rather than the default. Wayne On 1/24/08, footh <[EMAIL PROTECTED]> wrote: > I have a project that builds a jar that can be used in > another application which contains a couple classes > with default implementations. > > Then, I have an actual web application, which is > another project altogether, that uses this library, > EXCEPT that it alters two classes from their default > implementation. > > So, I'm trying to figure out a way in Maven to build > this web application without having to use another > copy of the entire codebase of the generic library > (with the two classes changed, of course). > > Does anyone have a way to do this in Maven or do I > have to look into reorganizing my generic library? > > Thanks, > > JF > > > > ____________________________________________________________________________________ > Be a better friend, newshound, and > know-it-all with Yahoo! Mobile. Try it now. > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ > > > --------------------------------------------------------------------- > 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]
