Hi Chamath,

Please find in [1].

thanks
Eranda

[1]. https://github.com/wso2/wso2-rampart


On Mon, Mar 10, 2014 at 12:29 PM, Chamath Gunawardana <[email protected]>wrote:

> Hi Eranda,
>
> Please create a repo for wso2-rampart in git.
>
>
>
>
> On Wed, Mar 5, 2014 at 8:01 PM, Chamath Gunawardana <[email protected]>wrote:
>
>> I will move rampart to git EOD next Monday. If you need it sooner please
>> proceed and I'm happy to assist on it.
>>
>>
>> On Wed, Mar 5, 2014 at 5:46 PM, Sagara Gunathunga <[email protected]>wrote:
>>
>>>
>>>
>>>
>>> On Wed, Mar 5, 2014 at 5:38 PM, Vanjikumaran Sivajothy 
>>> <[email protected]>wrote:
>>>
>>>> When we requested, we have been asked to use the existing rampart in
>>>> the nexus.
>>>>
>>>
>>> It was OK during the initial stages where  we focused on cleaning POMs
>>> and restructuring activities but now we are building product packs and we
>>> can't depend further on released Rampart version. The rational here is what
>>> ever the changes available on Axis2, Axiom and WSS4J should validate with
>>> Rampart codes and tests but right now it's not happening.
>>>
>>> Thanks !
>>>
>>>>
>>>> Thanks you,
>>>> Best Regards,
>>>> Vanji
>>>>
>>>>
>>>> On Wed, Mar 5, 2014 at 5:30 PM, Sagara Gunathunga <[email protected]>wrote:
>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Mar 5, 2014 at 5:22 PM, Punnadi Gunarathna 
>>>>> <[email protected]>wrote:
>>>>>
>>>>>> hi All,
>>>>>>
>>>>>> I got the following exception while i was building App Factory
>>>>>> p2-profile-gen module.
>>>>>>
>>>>>> Cannot complete the install because one or more required items could
>>>>>> not be found.
>>>>>>  Software being installed: WSO2 Carbon - Registry WS API Feature
>>>>>> 4.3.0.SNAPSHOT (org.wso2.carbon.registry.ws.feature.group 4.3.0.SNAPSHOT)
>>>>>>  Missing requirement: org.wso2.carbon.registry.ws.api 4.3.0.SNAPSHOT
>>>>>> (org.wso2.carbon.registry.ws.api 4.3.0.SNAPSHOT) requires 'package
>>>>>> org.apache.rampart.policy.model 1.6.1.wso2v9' but it could not be found
>>>>>>  Cannot satisfy dependency:
>>>>>>   From: WSO2 Carbon - Registry WS API Feature 4.3.0.SNAPSHOT
>>>>>> (org.wso2.carbon.registry.ws.feature.group 4.3.0.SNAPSHOT)
>>>>>>   To: org.wso2.carbon.registry.ws.api [4.3.0.SNAPSHOT]
>>>>>> Application failed, log file location:
>>>>>> /home/punnadi/.m2/repository/org/eclipse/tycho/tycho-p2-runtime/0.13.0/eclipse/configuration/1394016997349.log
>>>>>>
>>>>>> I found that it was configured in [1] as [2]. This has to be
>>>>>> corrected by adding the rampart project to GitHub and change the version 
>>>>>> to
>>>>>> -SNAPSHOT.
>>>>>>
>>>>>> [1]https://github.com/wso2/carbon-registry/blob/master/pom.xml
>>>>>> [2]<rampart.wso2.version>1.6.1.wso2v9</rampart.wso2.version>
>>>>>>
>>>>>
>>>>>
>>>>> 1. We should have wso2-rampart project on GitHub by now I'm not sure
>>>>> why it is not there, any idea ?
>>>>>
>>>>> 2. As we already depend on SNAPSHOT versions of Axiom, Axis2 and WSS4J
>>>>> we can't depend on released version of Rampart even though there is no
>>>>> Rampart changes. There should be a Rampart SNAPSHOT  version which depends
>>>>> on Axiom, Axis2 and WSS4J SNAPSHOT versions.
>>>>>
>>>>> Someone from IS team please look into this.
>>>>>
>>>>> Thanks !
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Thanks and Regards,
>>>>>>
>>>>>> Punnadi Gunarathna
>>>>>> Senior Software Engineer,
>>>>>> WSO2, Inc.; http://wso2.com <http://wso2>
>>>>>> Blog: http://hi-my-world.blogspot.com/
>>>>>> Tel : 94 11 214 5345
>>>>>> Fax :94 11 2145300
>>>>>>
>>>>>>
>>>>>>
>>>>>>  <http://lalajisureshika.blogspot.com/>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sagara Gunathunga
>>>>>
>>>>> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
>>>>> V.P Apache Web Services;    http://ws.apache.org/
>>>>> Linkedin; http://www.linkedin.com/in/ssagara
>>>>> Blog ;  http://ssagara.blogspot.com
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Dev mailing list
>>>>> [email protected]
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Sivajothy Vanjikumaran
>>>> *Senior Software Engineer*
>>>> *Integration Technologies Team*
>>>> *WSO2 Inc. http://wso2.com <http://wso2.com/>*
>>>> *Mobile:(+94)777219209*
>>>> *Mobile USA:**(+1)918 813 2403*
>>>> [image: Facebook] <https://www.facebook.com/vanjikumaran> [image:
>>>> Twitter] <https://twitter.com/vanjikumaran> [image: 
>>>> LinkedIn]<http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293> 
>>>> [image:
>>>> Blogger] <http://vanjikumaran.blogspot.com/> [image: 
>>>> SlideShare]<http://www.slideshare.net/vanjikumaran>
>>>>
>>>> This communication may contain privileged or other
>>>> confidential information and is intended exclusively for the addressee/s.
>>>> If you are not the intended recipient/s, or believe that you may
>>>> have received this communication in error, please reply to the
>>>> sender indicating that fact and delete the copy you received and in
>>>> addition, you should not print, copy, re-transmit, disseminate, or
>>>> otherwise use the information contained in this communication.
>>>> Internet communications cannot be guaranteed to be timely, secure, error
>>>> or virus-free. The sender does not accept liability for any errors
>>>> or omissions
>>>>
>>>
>>>
>>>
>>> --
>>> Sagara Gunathunga
>>>
>>> Senior Technical Lead; WSO2, Inc.;  http://wso2.com
>>> V.P Apache Web Services;    http://ws.apache.org/
>>> Linkedin; http://www.linkedin.com/in/ssagara
>>> Blog ;  http://ssagara.blogspot.com
>>>
>>>
>>
>>
>> --
>> Thanks,
>> Best Regards,
>> Chamath Gunawardana
>> Technical Lead; WSO2 Inc.
>> Mobile : +94776322240
>>
>
>
>
> --
> Thanks,
> Best Regards,
> Chamath Gunawardana
> Technical Lead; WSO2 Inc.
> Mobile : +94776322240
>



-- 

*Eranda Sooriyabandara*Senior Software Engineer;
Integration Technologies Team;
WSO2 Inc.; http://wso2.com
Lean . Enterprise . Middleware

E-mail: eranda AT wso2.com
Mobile: +94 716 472 816
Linked-In: http://www.linkedin.com/in/erandasooriyabandara
Blog: http://emsooriyabandara.blogspot.com/
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to