Sorry if I didn't make myself clear enough :) I am talking about what should be a pretty common use case: A little class library which we call libX and one or more utilities that depend on that library. We call them UtilA and UtilB.
I would like to have maven powered project layout that covers all three project and which lets me build UtilA and UtilB independly, yet resolving the dependency on libX for both. Wendy Smoak-3 wrote: > > On Feb 9, 2008 7:41 AM, oliverw <[EMAIL PROTECTED]> wrote: > >> Let's say we have project A producing a class library consumed by >> projects B >> and C. Is there a way around making A the parent of B and C? > > In B and C, declare a dependency on A. > > If you give a more concrete example, you'll probably get better > advice. What are you building, and what made you think A should be > the parent? > > -- > Wendy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Library-Project-Confusion-tp15372038s177p15372935.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
