<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 5/13/17 1:29 PM, Cantor, Scott
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:F408F0C5-6F13-4EA7-8DD4-C03F89226821@osu.edu">
<pre wrap="">On 5/13/17, 1:15 PM, "dev on behalf of Brent Putman" <a class="moz-txt-link-rfc2396E" href="mailto:dev-bounces@shibboleth.netonbehalfofputmanb@georgetown.edu"><dev-bounces@shibboleth.net on behalf of putmanb@georgetown.edu></a> wrote:
</pre>
<pre wrap="">
I didn't realize it was single inheritance, I never looked. I figured there'd be a chain of parents with precedence implied and so forth, but I hadn't thought much about it.</pre>
</blockquote>
<br>
Just to be absolutely certain, I checked the POM schema [1]. Only 1
<parent> is allowed.<br>
<br>
<blockquote type="cite"
cite="mid:F408F0C5-6F13-4EA7-8DD4-C03F89226821@osu.edu"><br>
<pre wrap="">I don't think we would ever know. If we thought to check, it would be to verify something, and if we knew what needed to be used, we'd probably have put it into our parent to lock it, and so we're back where we started. If we don't lock the version of something, we're basically stipulating that the transitively included version must be acceptable.
</pre>
</blockquote>
<br>
Absolutely. But I think the issue is just whether Maven conveys the
transitive dependencies properly, from the perspective of the
dependency itself.<br>
<br>
<br>
[1] <a class="moz-txt-link-freetext" href="http://maven.apache.org/xsd/maven-4.0.0.xsd">http://maven.apache.org/xsd/maven-4.0.0.xsd</a><br>
</body>
</html>