upgrade common-collections / velocity?

[Etienne Dysli-Metref]

On 16/05/17 01:38, Brent Putman wrote:
> So if I'm understanding correctly, this is essentially introducing a
> layer of indirection, by 1) creating a POM-only project that contains a
> dependencyManagement section 2) including that dependency in your own
> POM's dependencyManagement section.  So sort of declaring the
> dependencies by reference rather than by value.

Yes, except the importing project does not actually depend on all this
imported stuff. It must still declare its <dependencies> to get them.

> Can BOM POMs be layered like regular POMs (that is, inherit from other
> BOM POMs)?  Just wondering about avoiding duplicating common versions
> all over the place.

I don't have a working example on hand, but since the
dependencyManagement section is inherited [1] it should work.

> If so, seems like we might factor the
> java-parent-v3 dependencyManagement out to a parent-bom, from which we
> then inherit for the opensaml-bom, and idp-bom.  So sort of a parallel
> inheritance hierarchy as currently exists for the regular POMs.  Or
> maybe it's slightly different, depending on how it all works, but you
> get the basic idea of why I'm asking.

Yes, then extension developers who only want dependencyManagement can
import idp-bom instead of inheriting from idp-parent. :)

  Etienne

[1] https://maven.apache.org/pom.html#Inheritance


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://shibboleth.net/pipermail/dev/attachments/20170517/25636da2/attachment.sig>