The project that depends on pom artifact will be depending on all this pom's
dependencies. The pom dependency can be a replacement of a group of other
dependencies. I've tried this two years back and I guess this behavior
didn't change in maven 2.0.4

-Jiaqi

-----Original Message-----
From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
Sent: Monday, December 04, 2006 11:13 AM
To: Maven Users List
Subject: Re: setting dependency to a project with pom packaging?

On 12/4/06, Victor Okunev <[EMAIL PROTECTED]> wrote:

> Can I create a dependency to a project with pom packaging? This would 
> be convenient rather than creating separate dependencies on each 
> module it contains. I tried but unsuccessfully, it seems that Maven is 
> looking for a jar.  Perhaps I am missing something?

The default <type> is jar.  You could try <type>pom</type> but I don't think
it's going to do what you want.

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.

--
Wendy

---------------------------------------------------------------------
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]

Reply via email to