The modifications are committed to the trunk. We could not upgrade this
2.5.1, because OpenSAML2 2.5.1 artifacts are not yet published to their M2
repo. For the moment, I have upgraded it to 2.4.1 which is latest version
available in the M2 repo.
Anyway we will have to upgrade it to 2.5.1, once
Hi Folks,
We are planning to upgrade the OpenSAML2 version in trunk to 2.5.1 which
contains some critical security fixes. Anyway we will have to do a version
change for the OpenSAML2 orbit bundle after extracting out SLF4J to a
separate orbit. So the plan is to carry out both these changes at
Thilina, will this resolve the issue when building the 3.2.2 branch?
On Fri, Aug 19, 2011 at 10:05 AM, Thilina Buddhika thili...@wso2.comwrote:
Hi Folks,
We are planning to upgrade the OpenSAML2 version in trunk to 2.5.1 which
contains some critical security fixes. Anyway we will have to do
With this version upgrade for OpenSAML2, we are also upgrading the version
of OpenSAML2 orbit which should fix that issue as well.
Thanks,
Thilina
On Fri, Aug 19, 2011 at 10:44 AM, Isuru Suriarachchi is...@wso2.com wrote:
Thilina, will this resolve the issue when building the 3.2.2 branch?
