Dependencies are also used for interdependencies of your components.
It's common to see
<dependency><groupId>my.group.id</groupId>
<artifactId>my.sibling</artifactId>
<version>${project.version}</version>
</dependency>
modules are only used in a project of packaging 'pom' to tell Maven to
include a collection of other projects into the reactor. Those
projects are ordinary and relate to each other via dependencies.
On Wed, Jul 6, 2011 at 6:37 PM, kanesee <[email protected]> wrote:
> I thought the <dependency> section was just for artifacts that are located in
> the repository.
> For artifacts that consist of my own code, aren't those modules? I may be
> confusing the two.
>
> Our code base actually contains several different products, so I don't think
> it makes sense to have one pom that lists all of the subdirs as modules. My
> understanding is that I would have a pom-package for each of our products,
> which references only the subdirs (modules or dependencies) that it needed.
>
> Is my understanding correct?
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Referencing-modules-in-a-sibling-folder-tp4559091p4559177.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]
