On Wed, Mar 20, 2013 at 11:19 AM, Ian Young <span dir="ltr"><<a href="mailto:ian@iay.org.uk" target="_blank">ian@iay.org.uk</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
On 20 Mar 2013, at 14:59, Michael Schwartz <<a href="mailto:mike@gluu.org">mike@gluu.org</a>> wrote:<br>
<br>
> He raises an issue of<br>
> upgrading the commons-codes library from 1.4 to 1.5 in order to fix a bug.<br>
> Any thoughts if that is possible? I think we are going to patch our own<br>
</div>> war, but we'd like to be aligned with the main distribution…<br>
<br>
I can note that although the V2.3.8 IdP shipped with V1.4 of commons-codec (typo, right?), the V2.4.0 IdP development has brought that dependency forward to V1.6 of commons-codec. So unless something fails along the way, the *next* IdP will ship with at least that one. I see that there's a V1.7 available now too, though.<br>
<br>
None of which is to say whether dropping in V1.5 over V1.4 would work or not; I don't think there's any easy way to know the answer to that.<br></blockquote><div><br></div><div>vt-ldap depends on version 1.4, but it compiles with 1.5, 1.6 and 1.7.</div>
<div>I don't expect any compatibility problems.</div><div><br></div><div>--Daniel Fisher</div><div> </div></div>