On 12/4/06, Victor Okunev <[EMAIL PROTECTED]> wrote:
> What are you trying to do? It sounds like you have a pom with
> <modules> and you expect that declaring a dependency on that pom will
> add those modules as dependencies.
Yes, that's the idea. Is it possible or I misunderstand the purpose of
projects with pom packaging?
Pom packaging is typically used for
1) 'parent' poms (a list of modules, dependencyManagement, dependencies)
2) 'master' poms (organization level defaults, usually no modules)
3) overriding the default lifecycle by binding plugin executions
where you want them
(I'm probably missing something...)
Projects are usually split into modules and arranged in a hierarchy
with inherited dependencies. Or with <dependencyManagement> at the
top level to set the version numbers, and then dependencies declared
in the child poms.
It sounds like you either need the normal pom hierarchy so that your
dependencies will be inherited, or possibly some profiles if you're
trying to use different "sets" of dependencies.
Describe your project and I'm sure someone here can help.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
