Thanks John,
In this case I could use some help understanding. In every case, without
exception, when I add a "dependencies" section of a POM file whose
packaging is "pom," not once have I intended that POM files artifact to
be what is dependent on those items. In every case it's the children of
that POM file that I want to "include" those dependencies.
I cannot even envision a case where a dependency listed in a POM file
whose packaging is POM is actually a dependency on the building of the
POM artifact.
If possible, some clarification would be much appreciated.
Thanks,
Jim
John Tolentino wrote:
Hi Jim,
All POMs' dependencies needs to be validated regardless of its packaging.
Regards,
John
Jim Carroll wrote:
It appears that the transitive dependency mechanism is not sensitive
to the packaging. This seems odd to me and is causing me an
incredible amount of grief. I have a parent pom that defines a
dependency. I intend this parent pom to be used almost like an
"include." For example:
<project>
<modelVersion>4.0.0</modelVersion>
<groupId>mycompany.poms</groupId>
<artifactId>parentpom</artifactId>
<version>xxx</version>
<packaging>pom</packaging>
....
<dependencies>
<dependency>
<groupId>mycompany.lib</groupId>
<artifactId>utility</artifactId>
<version>xxx</version>
</dependency>
</dependencies>
....
The odd thing is, the installation and/or deployment of the parent
pom itself REQUIRES the lib. It's as if the dependency is a
dependency on the building of the POM and not a dependency on the
building of any OTHER poms that list this pom as a parent.
It seems to me that if the packaging of the artifact being built is
"pom" then dependencies ought to be ignored.
Am I missing something?
Thanks in advance.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
