Re: [Vote][Rampart-C] Vote for Apache Rampart/C 1.0.0 Release - Take 2

+1 asankha Nandika Jayawardana wrote: +1 Thanks Nandika On 10/3/07, *Ruchith Fernando* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: +1 Thanks, Ruchith On 10/1/07, Kaushalye Kapuruge [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Devs, I have

Re: [Vote][Rampart-C] Vote for Apache Rampart/C 1.0.0 Release - Take 2

Tested on Ubuntu 7.04 +1 Milinda.. On 10/3/07, Asankha C. Perera [EMAIL PROTECTED] wrote: +1 asankha Nandika Jayawardana wrote: +1 Thanks Nandika On 10/3/07, Ruchith Fernando [EMAIL PROTECTED] wrote: +1 Thanks, Ruchith On 10/1/07, Kaushalye Kapuruge [EMAIL PROTECTED]

[jira] Created: (AXIS2C-713) Use macros for server log file names

Use macros for server log file names Key: AXIS2C-713 URL: https://issues.apache.org/jira/browse/AXIS2C-713 Project: Axis2-C Issue Type: Improvement Affects Versions: 1.1.0 Reporter:

[Axis2] Next release 1.1.1 or 1.2.0?

We just released 1.1.0, but I think we also have to look forward and see what should be next. I need this info to update the Jira etc. Ideally it should be a 1.1.1 but if there are API additions we should go for 1.2 Thoughts? Samisa... -- Samisa Abeysinghe : WSO2 WSF/PHP

Re: [Vote][Rampart-C] Vote for Apache Rampart/C 1.0.0 Release - Take 2

Here is my +1 Thanks, Supun.. On 10/3/07, Milinda Pathirage [EMAIL PROTECTED] wrote: Tested on Ubuntu 7.04 +1 Milinda.. On 10/3/07, Asankha C. Perera [EMAIL PROTECTED] wrote: +1 asankha Nandika Jayawardana wrote: +1 Thanks Nandika On 10/3/07, Ruchith Fernando

Re: [Axis2] Next release 1.1.1 or 1.2.0?

Hi, Samisa Abeysinghe [EMAIL PROTECTED] writes: We just released 1.1.0, but I think we also have to look forward and see what should be next. I need this info to update the Jira etc. Ideally it should be a 1.1.1 but if there are API additions we should go for 1.2 I also think it should be

[jira] Created: (AXIS2C-714) Use macros for server port

Use macros for server port -- Key: AXIS2C-714 URL: https://issues.apache.org/jira/browse/AXIS2C-714 Project: Axis2-C Issue Type: Improvement Affects Versions: 1.1.0 Reporter: Samisa Abeysinghe

[Axis2] Port numbers for tcp and http servers

We use 9090 as the default for both. Should be not use unique ones, in case someone wants to run both at the same time with default settings? I propose that to 9091 as the default for TCP server. Samisa... -- Samisa Abeysinghe : WSO2 WSF/PHP

[jira] Resolved: (AXIS2C-713) Use macros for server log file names

[ https://issues.apache.org/jira/browse/AXIS2C-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-713. -- Resolution: Fixed Fix Version/s: 1.1.1 Used macros for lo files names in place

[jira] Resolved: (AXIS2C-714) Use macros for server port

[ https://issues.apache.org/jira/browse/AXIS2C-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-714. -- Resolution: Fixed Fix Version/s: 1.1.1 Added macros to hold the port in simple

[jira] Resolved: (AXIS2C-712) Use different log file names for simple tcp and http hervers

[ https://issues.apache.org/jira/browse/AXIS2C-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-712. -- Resolution: Fixed Fix Version/s: 1.1.1 Used the log file names

Re: Log file names for tcp and http servers

Done. Samisa... Dinesh Premalal wrote: +1 thanks, Dinesh Samisa Abeysinghe [EMAIL PROTECTED] writes: We use the same default log file names for both servers. Should use unique names, else they would be overwritten when the two servers are up. Propose to use axis2_http_server.log and

Re: [Vote][Rampart-C] Vote for Apache Rampart/C 1.0.0 Release - Take 2

+1 for 1.0.0 Thanks -sahan On 10/3/07, Supun Kamburugamuva [EMAIL PROTECTED] wrote: Here is my +1 Thanks, Supun.. On 10/3/07, Milinda Pathirage [EMAIL PROTECTED] wrote: Tested on Ubuntu 7.04 +1 Milinda.. On 10/3/07, Asankha C. Perera [EMAIL PROTECTED] wrote: +1

Re: [Axis2] Next release 1.1.1 or 1.2.0?

Dinesh Premalal wrote: Hi, Samisa Abeysinghe [EMAIL PROTECTED] writes: We just released 1.1.0, but I think we also have to look forward and see what should be next. I need this info to update the Jira etc. Ideally it should be a 1.1.1 but if there are API additions we should go for 1.2

[Axis2] Are we really binary compatible?

I have doubts on our binary compatibility. Anyone has any thoughts on this? Samisa... -- Samisa Abeysinghe : WSO2 WSF/PHP

Re: [Axis2] Next release 1.1.1 or 1.2.0?

On Thu, 2007-10-04 at 08:54 +0600, Samisa Abeysinghe wrote: Dinesh Premalal wrote: Hi, Samisa Abeysinghe [EMAIL PROTECTED] writes: We just released 1.1.0, but I think we also have to look forward and see what should be next. I need this info to update the Jira etc. Ideally it

Re: [Axis2] Next release 1.1.1 or 1.2.0?

+1 for 1.2 I think it's inevitable when Neethi/C is getting matured. Unless Neethi/C become a separate project. (Which I don't see as an important step at this moment). Cheers, Kau Manjula Peiris wrote: On Thu, 2007-10-04 at 08:54 +0600, Samisa Abeysinghe wrote: Dinesh Premalal wrote:

Re: [Vote] [Sandesha2/C] For Apache Sandesha2/C 0.91 Release - Take 3

+1. Cheers, Kaushalye Chamikara Jayalath wrote: +1 Chamikara On 10/2/07, *Dushshantha Chandradasa* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: here is my +1 Regards, Dushshantha and uploaded the second set of Apache Sandesha2/C 0.91 release artifacts

Re: [Axis2] Are we really binary compatible?

Hi, I think we need to check whether we have replaced or removed any API function or constant since 1.0 release. Accoarding to [1] adding new functions or constants should not affect the binary compatibility when minor version is upgraded. [1] http://apr.apache.org/versioning.html#strategy

Re: [Axis2] Are we really binary compatible?

Manjula Peiris wrote: Hi, I think we need to check whether we have replaced or removed any API function or constant since 1.0 release. Accoarding to [1] adding new functions or constants should not affect the binary compatibility when minor version is upgraded. Agreed, but aparently there