[jira] Created: (AXIS2C-1129) Processing requests by modules, handlers

Processing requests by modules, handlers Key: AXIS2C-1129 URL: https://issues.apache.org/jira/browse/AXIS2C-1129 Project: Axis2-C Issue Type: Wish Components: documentation Affects

[jira] Commented: (AXIS2C-1129) Processing requests by modules, handlers

[ https://issues.apache.org/jira/browse/AXIS2C-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594512#action_12594512 ] Malinda Kaushalye Kapuruge commented on AXIS2C-1129: Hi, You can have

[jira] Commented: (AXIS2C-1129) Processing requests by modules, handlers

[ https://issues.apache.org/jira/browse/AXIS2C-1129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594528#action_12594528 ] Damitha Kumarage commented on AXIS2C-1129: -- Hi, We have a Axis2/C module called

Re: [VOTE][Axis2]Apache Axis2/C 1.4.0 Release - Take3

Hi all, This vote thread open for 72 hours to vote. We got 10 votes including 5 PMC votes. Therefore release artifacts are ready for release and I am closing this vote thread. Vote Summery --- PMC Votes 5 Non-PMC Votes 5 Total Votes10 -1's

[Vote][Rampart-C] Vote for Apache Rampart/C 1.2.0 Release - Take 1

Hi Devs, I have uploaded the Apache Rampart/C 1.2.0 release artifacts here http://people.apache.org/~kaushalye/release/rampart-c/1.2.0 The key to verify the release artifacts can be found at http://people.apache.org/~kaushalye/release/KEYS Please test and review with Apache Axis2/C 1.4.0

Re: [Vote][Rampart-C] Vote for Apache Rampart/C 1.2.0 Release - Take 1

Hi Kaushalye , Seems like docs/index.html has a problem it has a the release data as *25th Apr 2008 - Apache Rampart/C Version 1.2.0 Released*. I think you need to update that, Thank you! Deepal Hi Devs, I have uploaded the Apache Rampart/C 1.2.0 release artifacts here

Re: [Vote][Rampart-C] Vote for Apache Rampart/C 1.2.0 Release - Take 1

Deepal jayasinghe wrote: Hi Kaushalye , Seems like docs/index.html has a problem it has a the release data as *25th Apr 2008 - Apache Rampart/C Version 1.2.0 Released*. I think you need to update that, Thanks for pointing this out. But this is the date when we packed the RC2, which turned

Missing libaxis2_receivers.so

Hi, In the logs I can see, [Tue May 6 17:40:59 2008] [error] class_loader.c(161) dlerror reason: /opt/wso2/wsf_c/lib/libaxis2_receivers.so: cannot open shared object file: No such file or directory [Tue May 6 17:40:59 2008] [error] class_loader.c(161) dlerror reason:

[Sandesha2/C] Linking to libaxutil.la

Hi, Although Sandesha2/C includes axutil_*.h and uses functions defined there I can't see libaxutil.la being linked anywhere (except for Sandesha2/* samples). This resulted in the following error, [Tue May 6 17:40:59 2008] [error] class_loader.c(161) dlerror reason:

Estimated Complexity field in Jira

I find that we have a field called Estimated Complexity in our Jira. I propose that we use this field to mark issues to help people pick what to fix based on their expertise. Specially helps with new contributions. I find that the Harmony project is using this. The possible values are: *

Re: Estimated Complexity field in Jira

Hi, I know we traverse through Jiras before a release to pick what we want to fix. We can also take a moment to mark this field as well. Thoughts please... Yes, it will be good step. +1 thanks, Dinesh -- http://nethu.org/

Re: Estimated Complexity field in Jira

+ 1 for this. thanks, -Manjula. On Wed, 2008-05-07 at 08:40 +0530, Dinesh Premalal wrote: Hi, I know we traverse through Jiras before a release to pick what we want to fix. We can also take a moment to mark this field as well.