And also following modification should be applied to the bin.xml, so that it will copy the correct OpenSAML jar to the distribution.
Hi Shankar,We can replace the OpenSAML 1.1 dependency with the following entry and remove the WSO2 M2 repo from the root pom.xml.<dependency><groupId>org.opensaml</groupId><artifactId>opensaml1</artifactId><version>1.1</version></dependency>Thanks,ThilinaThilina Mahesh Buddhika
On Thu, Dec 30, 2010 at 10:42 AM, Selvaratnam Uthaiyashankar <firstname.lastname@example.org> wrote:
On Wed, Dec 29, 2010 at 9:37 PM, Thilina Mahesh Buddhika
Thilina, AFAIK this particular version (opensaml-1.1.40) is needed> On Wed, Dec 29, 2010 at 12:20 PM, Ruwan Linton <email@example.com>
>> Hi Andreas,
>> Please see my comments inline;
>> On Tue, Dec 28, 2010 at 5:48 PM, Andreas Veithen
>> <firstname.lastname@example.org> wrote:
>>> There is another issue with that release caused by the change in
>>> r1051839, which adds http://dist.wso2.org/maven2 as a repository. The
>>> problem is that this repository is not properly managed.
>> Well as of what you have found this statement seems to be correct, but it
>> is a mistake that we have done, and we are managing the WSO2 m2 repo
>>> It contains
>>> artifacts with the same groupId, artifactId and version as Maven
>>> central, but with different content. Example:
>> Regarding this particular issue, if you carefully have a look, the pom on
>> the WSO2 m2 repo points to the 1.5-wso2v4 as it's parent, and the mistake
>> there was that the addressing version has not been updated and it is
>> deployed as a 1.5 version. I guess this happened because Axis2 fails to
>> resolve the module version with letters in the trailing part like wso2v4.
>>> This threatens the stability of the build of the Rampart project as
>>> well as downstream projects. We had lots of issues with the java.net
>>> repository, which is also not managed properly, and Axis2 now no
>>> longer relies on this repository. We should not make the same mistake
>> I am not quite sure why the WSO2 m2 repo is being added to rampart as I do
>> not see any specific WSO2 dependency being added to rampart.
> Sorry for being late to reply. We had to add this repository in order to get
> opensaml-1.1.406 artifacts which contains a bug fix which is required for
> certain WS-Trust related scenarios to work out of the box.
> Rampart 1.5  was also released with having WSO2 M2 repo listed as a
> repository due to some issues we had (I can't recall the exact reason). So
> we added WSO2 M2 repo, which contains this patched version of OpenSAML 1.1
only for some features demonstrated in sample 5 right? How about if we
ask users to download this version of opensaml as part of sample
configuration procedure? I can see that the instructions are already
available in . In that case, can we remove the repo and have the
dependency to opensaml 1.1, which is available in ?
> If we can push these OpenSAML-1.1.406 related artifacts into an Apache repo,
> this we can remove the newly added repository entry.
>> Being said that we are managing the repository properly and we are in the
>> process of getting Nexus or some infrastructure inplace for managing the
>> repo decently.
>>> Therefore my vote is -1.
>>> On Thu, Dec 23, 2010 at 05:37, Selvaratnam Uthaiyashankar
>>> <email@example.com> wrote:
>>> > Devs,
>>> > This is the vote for Apache Rampart 1.5.1 release.
>>> > Please review the signed artifacts:
>>> > http://people.apache.org/~shankar/rampart/1.5.1/dist/
>>> > The m2 repository is available at:
>>> > http://people.apache.org/~shankar/rampart/1.5.1/m2_repo/
>>> > The site is temporarily hosted at:
>>> > http://people.apache.org/~shankar/rampart/1.5.1/site/
>>> > SVN Info:
>>> > https://svn.apache.org/repos/asf/axis/axis2/java/rampart/tags/v1.5.1
>>> > It was tested against Axis2 release candidates hosted in:
>>> > http://people.apache.org/~veithen/1.5.4/
>>> > Here's my +1 (binding) to declare the above dist as Apache Rampart
>>> > 1.5.1
>>> > thanks,
>>> > Shankar
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: firstname.lastname@example.org
>>> > For additional commands, e-mail: email@example.com
>>> To unsubscribe, e-mail: firstname.lastname@example.org
>>> For additional commands, e-mail: email@example.com
>> Ruwan Linton
>> Software Architect & Product Manager
>> WSO2 Inc.; http://wso2.org
>> Lean . Enterprise . Middleware
>> phone: +1 408 754 7388 ext 51789
>> email: firstname.lastname@example.org; cell: +94 77 341 3097
>> blog: http://blog.ruwan.org
>> linkedin: http://www.linkedin.com/in/ruwanlinton
>> google: http://www.google.com/profiles/ruwan.linton
>> tweet: http://twitter.com/ruwanlinton
Senior Architect & Senior Manager
http://wso2.com/ - "lean . enterprise . middleware"