upgrade common-collections / velocity?

Etienne Dysli-Metref etienne.dysli-metref at switch.ch
Mon May 15 10:23:53 EDT 2017


On 15/05/17 16:03, Cantor, Scott wrote:
> To the latter, that was where my own practice was to just use the
> existing parent POM, but I can see the reasoning.

Yeah for Shibboleth projects it totally makes sense to use your parent
POM. For external developers however, doing that means their project
inherits all your project metadata (source code location, issue tracker
URL, etc.) which is probably meaningless for their project and prevents
them from using their own [organisation- or team-mandated] parent POM.
That's why I like the BOM approach. :)

  Etienne

-------------- 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/20170515/8cf58ab8/attachment.sig>


More information about the dev mailing list