upgrade common-collections / velocity?
Brent Putman
putmanb at georgetown.edu
Sat May 13 23:33:34 EDT 2017
On 5/13/17 1:29 PM, Cantor, Scott wrote:
> On 5/13/17, 1:15 PM, "dev on behalf of Brent Putman" <dev-bounces at shibboleth.net on behalf of putmanb at georgetown.edu> wrote:
>
> 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.
Just to be absolutely certain, I checked the POM schema [1]. Only 1
<parent> is allowed.
>
> 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.
>
Absolutely. But I think the issue is just whether Maven conveys the
transitive dependencies properly, from the perspective of the
dependency itself.
[1] http://maven.apache.org/xsd/maven-4.0.0.xsd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20170513/94bdcf17/attachment.html>
More information about the dev
mailing list