Unlock opensaml-parent ?

[Tom Zeller]

> On Oct 23, 2015, at 6:11 AM, Ian Young <ian at iay.org.uk> wrote:
> 
>> On 23 Oct 2015, at 00:02, Tom Zeller <tzeller at dragonacea.biz> wrote:
>> 
>> I remember talking about this on a dev call, but I don’t remember the details. For an IdP release, should all of the projects in our stack have the same parent version ?
> 
> I don't see that buying us anything in general. What do you see as the benefit of such a requirement?

Consistency ? Weakly stated, though.

> 
>> i.e. should we unlock OpenSAML and java-support and spring-extensions ? They might be unlocked already at the moment, but I’m asking more in general. If so, then it seems that whenever we unlock the IdP we should unlock upstream projects too.
> 
> Forcing everything to have the same parent POM version seems equivalent to saying that we'd rebuild and release new versions of every component in the stack even if they have no functional changes. That sounds counter-intuitive to me, but maybe I'm missing the point.
> 
> I'd say no, don't rebuild and re-release things unless there are functional changes. I don't see that having different components built with different parent POM versions is a problem that needs to be solved.

Okay, I’m remembering what we said on the call better now. And how do we define “functional” changes ? Quickly and offhand, I would say : ultimately it boils down to the versions of the artifacts we ship in WEB-INF/lib.