When you specify 'pom' as package type in a project you mostly konfigure the
lifecycle of that project.
When in your dependency, you need to specify the type as well ("pom"),
otherwise Maven is going to look for a jar dependency.
It's two different things. This is just how things work, you need to
appreciate that...:-)
/Anders
On Sat, Jan 30, 2010 at 17:39, tbee <[email protected]> wrote:
>
>
>
> Jörg Schaible-2 wrote:
> >
> > No, it cannot. If you omit the type, it defaults to "jar" and that is a
> > different artifact.
> >
>
> I understand that the PACKAGING type needs to be set to "pom", but I do not
> understand (and that was my error) that the DEPENDENCY type, so the other
> side of the relation, also must be set to "pom".
>
>
> --
> View this message in context:
> http://old.nabble.com/pom-without-artifacts--tp27381618p27385253.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]
>
>