spring-web-2.5.6.jar in IdP 2.3.4

[Bart Ophelders]

Hello,

 

Is there a reason why spring-web-2.5.6 is not upgraded to spring-web-3.0.5 while the other spring libraries are?

 

Kr,

Bart

[Chad La Joie]

Because it was missed in the upgrade.

> --
> To unsubscribe from this list send an email to
> users-un...@shibboleth.net
>

--
Chad La Joie
www.itumi.biz
trusted identities, delivered
--
To unsubscribe from this list send an email to users-un...@shibboleth.net

[Bart Ophelders]

Ok, thanks.

[Etienne Dysli]

On 04/11/11 12:21, Chad La Joie wrote:
> Because it was missed in the upgrade.

Are you going to repackage release 2.3.4?
Also the POM files for shibboleth-common and shibboleth-identityprovider
[1,2] still require Spring Framework version 2.5.6.SEC02. Should we use
that one or 3.0? (to be precise that would be 2.5.6.SEC03 or
3.0.6.RELEASE with the latest versions)

Regards,
Etienne

[1]
https://shibboleth.net/nexus/content/repositories/releases/edu/internet2/middleware/shibboleth-common/1.3.4/shibboleth-common-1.3.4.pom
[2]
https://shibboleth.net/nexus/content/repositories/releases/edu/internet2/middleware/shibboleth-identityprovider/2.3.4/shibboleth-identityprovider-2.3.4.pom

[Cantor, Scott]

On 11/8/11 8:59 AM, "Etienne Dysli" <etienn...@unil.ch> wrote:

>On 04/11/11 12:21, Chad La Joie wrote:
>> Because it was missed in the upgrade.
>
>Are you going to repackage release 2.3.4?
>Also the POM files for shibboleth-common and shibboleth-identityprovider
>[1,2] still require Spring Framework version 2.5.6.SEC02. Should we use
>that one or 3.0? (to be precise that would be 2.5.6.SEC03 or
>3.0.6.RELEASE with the latest versions)

I would not use anything other than what was in there before, and what the
POM says, which is 2.5.6.SEC02.

The conflict is because there's a parent POM that has 3.x in it and it's
getting in the way.

A patch release shouldn't be bumping major Spring versions, and I don't
think that was intended.

-- Scott