Dependency does not imply folder structure. Just the opposite. If each of these projects builds a jar, each is has the default packaging (jar). You indicate dependency by adding a <dependency> element to the pom.
You probably want a pom in the myComponents dir that has <packaging>pom</packaging> and lists all the subdirs as modules. On Wed, Jul 6, 2011 at 6:05 PM, kanesee <[email protected]> wrote: > Hello, > > I'm very new to Maven. > I'm trying to convert my company's build environment from a proprietary > configuration to Maven's. > > We components that are dependent on one another and they lie in sibling > folders. > e.g. We may have components > ./myComponents/A > ./myComponents/B > ./myComponents/C > ./myComponents/D > > Let's suppose component A depends on B and C. Component B depends on D. And > Component C depends on D. > > A couple of questions: > 1) How do I reference component D from B? > In the examples, it seems that the folder of component D has to be within > the folder of component B. But component B is also a module for component C > so I don't want to move it underneath B. > > 2) What should the <packaging> value of B be? Should it be pom since it > refers to submodule D? Or should it be a jar since it contains its own > classes and is referenced by A? > > Thanks in advance, > Kane > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Referencing-modules-in-a-sibling-folder-tp4559091p4559091.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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
