Re: [MINA] 2.0 Milestone 1 ?
On Sun, 27 Jan 2008 20:24:07 +0900 Trustin Lee [EMAIL PROTECTED] wrote: On Jan 26, 2008 5:09 PM, Emmanuel Lecharny [EMAIL PROTECTED] wrote: Trustin Lee wrote: I forgot to mention that we need to move transport-serial to sandbox temporarilly due to the LGPL issue. I guess we need to wait for the result of the board meeting which is going to be held on Feb 20. Yes, very true ! I thought about it yesturday too, but I also forgot to mention it... Hopefully, the [EMAIL PROTECTED] will define a clear position soon :) (This license stuff is by no mean easy...) But we may deliver a milestone without the serial subproject, can we ? Sure. That's what I meant. :) Trustin Hi, sorry for the lack of support on this issues I was on winter holidays. Those LGPL issues start to give me serious headache. I'll propose something I wanted to avoid, but it looks likes the bureaucratic issues have win. The serial connector can be modified to depend on a old Sun's comm.jar (2.X) in place of RXTX directly (you will anyway plug rxtx behind) which work on windows not like the 3.X release (who said Sun sucks ?:D). And the license terms are probably less irritating. You will still be able (anyway I seriously encourage you :D) to use rxtx2.0 (not 2.1) as the comm API implementation. By placing a javax.comm.properties files in your JDK lib directory containing the line : Driver=gnu.io.RXTXCommDriver. What will lose : - RXTX 2.0 in place of RXTX 2.1 - depending on comm.jar, add another dependency - serial comm user will need to download an old version of Sun Communication API, and modify their JRE Lib directory for change the implementation (Sun comm API V2 doesn't work on Linux). What we win : - no more LGPL dependency - directly integrated serial communication in the MINA default build Julien
Re: [MINA] 2.0 Milestone 1 ?
On Jan 26, 2008 5:09 PM, Emmanuel Lecharny [EMAIL PROTECTED] wrote: Trustin Lee wrote: I forgot to mention that we need to move transport-serial to sandbox temporarilly due to the LGPL issue. I guess we need to wait for the result of the board meeting which is going to be held on Feb 20. Yes, very true ! I thought about it yesturday too, but I also forgot to mention it... Hopefully, the [EMAIL PROTECTED] will define a clear position soon :) (This license stuff is by no mean easy...) But we may deliver a milestone without the serial subproject, can we ? Sure. That's what I meant. :) Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
Re: [MINA] 2.0 Milestone 1 ?
Trustin Lee wrote: I forgot to mention that we need to move transport-serial to sandbox temporarilly due to the LGPL issue. I guess we need to wait for the result of the board meeting which is going to be held on Feb 20. Yes, very true ! I thought about it yesturday too, but I also forgot to mention it... Hopefully, the [EMAIL PROTECTED] will define a clear position soon :) (This license stuff is by no mean easy...) But we may deliver a milestone without the serial subproject, can we ? -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org
Re: [MINA] 2.0 Milestone 1 ?
Emmanuel Lecharny-3 wrote: 2.0.0-M1 is a milestone, not a release. We can wait forever until the last bug has been fixed, but this does not help a lot projects using MINA ! I see, seems I'm confused by the milestone and release concepts, sorry for that and thanks for your clarification! -- View this message in context: http://www.nabble.com/-MINA--2.0-Milestone-1---tp15081795s16868p15108456.html Sent from the Apache MINA Support Forum mailing list archive at Nabble.com.
Re: [MINA] 2.0 Milestone 1 ?
He will not mind (TM) :D So... now we can start to drop IoSessionLogger and you could add JUL MDC formatter into org.apache.mina.util, right? Trustin On Jan 25, 2008 6:10 PM, Maarten Bosteels [EMAIL PROTECTED] wrote: On Jan 25, 2008 10:08 AM, Maarten Bosteels [EMAIL PROTECTED] wrote: Hello all, On Jan 25, 2008 9:56 AM, Trustin Lee [EMAIL PROTECTED] wrote: I'd wait for a new SLF4J release that enables MDC for java.util.logging and consequently simplifies MINA Logging dramatically. That is the only issue to be resolved before we release 2.0.0-M1. Maarten and Ceki is working on it, so let's wait a little bit more for him and Ceki. Maarten By the way, any idea when the next version of SLF4J will be released ? Ceki Real soon now (TM). Once slf4j-converter run properly and a remaining few bugs in SLF4J get fixed, I'll make a release. It should be this month or early February. Note that this wasn't an official announcement by Ceki in any way. I copy-pasted it from a private message, I hope Ceki doesn't mind :-) I will try to add some MDC-aware jukl formatters over the weekend. If the new release of SLF4J is getting late, we can just do what we planned to do; just drop IoSessionLogger and support MDC for JDK later when the new SLF4J is released. We could already start replacing usage of IoSessionLogger with plain SLF4J Logger instances on the trunk ? And once the new SLF4J is released, we can release the milestone. WDYT ? Emmanuel, you said There are no roadmap atm. Two versions are expected (2.0.0-M1 and 2.0.0-M2), but they barely contains any issue. I don't understand ? According to JIRA 99 of 102 issues have been resolved for 2.0.0-M1 regards, Maarten Other unscheduled issues are mostly feature addition, unreproduceable bugs or bug reports for the trunk, so we will have to schedule it as soon as 2.0.0-M1 is released. Trustin On Jan 25, 2008 4:13 PM, Emmanuel Lecharny [EMAIL PROTECTED] wrote: Alex Karasulu wrote: Hi all, What does everyone think about a 2.0 milestone release in the near future? After a convo on IRC many feel that milestone releases do not guarantee API stability. If this is the case we could get a milestone out so users can kick the tires on the API changes and give feedback so we can adjust. I would like to see some 2.0 milestones soon There are a few things to work out though : - There are no roadmap atm. Two versions are expected (2.0.0-M1 and 2.0.0-M2), but they barely contains any issue. - There are 44 unscheduled issues. It would be good to schedule those issues into the created milestones - There are only 6 open bugs, so I guess we are close to a milestone, as soon as thise bug are fixed. Now, a lot of improvements are expected to be made, but we don't know which version they are targeting. Generally speaking, it might be a good thing to use JIRA roadmap management a bit more. Hope it helps. -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6 -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
Re: [MINA] 2.0 Milestone 1 ?
On Jan 25, 2008 10:24 AM, Trustin Lee [EMAIL PROTECTED] wrote: He will not mind (TM) :D So... now we can start to drop IoSessionLogger and you could add JUL MDC formatter into org.apache.mina.util, right? sure. I am willing to do both. Maarten Trustin On Jan 25, 2008 6:10 PM, Maarten Bosteels [EMAIL PROTECTED] wrote: On Jan 25, 2008 10:08 AM, Maarten Bosteels [EMAIL PROTECTED] wrote: Hello all, On Jan 25, 2008 9:56 AM, Trustin Lee [EMAIL PROTECTED] wrote: I'd wait for a new SLF4J release that enables MDC for java.util.logging and consequently simplifies MINA Logging dramatically. That is the only issue to be resolved before we release 2.0.0-M1. Maarten and Ceki is working on it, so let's wait a little bit more for him and Ceki. Maarten By the way, any idea when the next version of SLF4J will be released ? Ceki Real soon now (TM). Once slf4j-converter run properly and a remaining few bugs in SLF4J get fixed, I'll make a release. It should be this month or early February. Note that this wasn't an official announcement by Ceki in any way. I copy-pasted it from a private message, I hope Ceki doesn't mind :-) I will try to add some MDC-aware jukl formatters over the weekend. If the new release of SLF4J is getting late, we can just do what we planned to do; just drop IoSessionLogger and support MDC for JDK later when the new SLF4J is released. We could already start replacing usage of IoSessionLogger with plain SLF4J Logger instances on the trunk ? And once the new SLF4J is released, we can release the milestone. WDYT ? Emmanuel, you said There are no roadmap atm. Two versions are expected (2.0.0-M1 and 2.0.0-M2), but they barely contains any issue. I don't understand ? According to JIRA 99 of 102 issues have been resolved for 2.0.0-M1 regards, Maarten Other unscheduled issues are mostly feature addition, unreproduceable bugs or bug reports for the trunk, so we will have to schedule it as soon as 2.0.0-M1 is released. Trustin On Jan 25, 2008 4:13 PM, Emmanuel Lecharny [EMAIL PROTECTED] wrote: Alex Karasulu wrote: Hi all, What does everyone think about a 2.0 milestone release in the near future? After a convo on IRC many feel that milestone releases do not guarantee API stability. If this is the case we could get a milestone out so users can kick the tires on the API changes and give feedback so we can adjust. I would like to see some 2.0 milestones soon There are a few things to work out though : - There are no roadmap atm. Two versions are expected (2.0.0-M1and 2.0.0-M2), but they barely contains any issue. - There are 44 unscheduled issues. It would be good to schedule those issues into the created milestones - There are only 6 open bugs, so I guess we are close to a milestone, as soon as thise bug are fixed. Now, a lot of improvements are expected to be made, but we don't know which version they are targeting. Generally speaking, it might be a good thing to use JIRA roadmap management a bit more. Hope it helps. -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6 -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
Re: [MINA] 2.0 Milestone 1 ?
Emmanuel, you said There are no roadmap atm. Two versions are expected (2.0.0-M1 and 2.0.0-M2), but they barely contains any issue. I don't understand ? According to JIRA 99 of 102 issues have been resolved for 2.0.0-M1 You don't understand, because I was misrepresenting the reality, due to a lack of coffee... You have to realize that I sent this mail at 8h14 am, a very strange and unusual hour for me Ok, let me rephrase this : The 2.0.0-M1 roadmap is almost completely achieved, we just have 44 issues which need to be scheduled, most of which are improvement. Thanks to the MINA team hardwork, 99 issues has been fixed ! It think it better represents the project state than the misleading mail I sent this morning ! Sorry for that, and thanks for having corrected me, Maarten ! -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
Re: [MINA] 2.0 Milestone 1 ?
Trustin Lee wrote: Other unscheduled issues are mostly feature addition, unreproduceable bugs or bug reports for the trunk, so we will have to schedule it as soon as 2.0.0-M1 is released. Trustin Hi, Trustin Err... so, bug reports for the trunk won't be fixed? And I think there IS a serious bug, https://issues.apache.org/jira/browse/DIRMINA-515 DIRMINA-515 , which prevents XP SP2 users connects to an NioDatagramAcceptor with an NioDatagramConnector. I reported it a few days ago. If 2.0.0-M1 release is coming soon, I definitely whish that this bug can be fixed! Cheers Cheng -- View this message in context: http://www.nabble.com/-MINA--2.0-Milestone-1---tp15081795s16868p15093314.html Sent from the Apache MINA Support Forum mailing list archive at Nabble.com.
Re: [MINA] 2.0 Milestone 1 ?
I started looking at this problem. Admittedly, I am not a windows expert so I may not be the best person to look at this problem. I will continue to look at the problem and try to determine what is going on... On Jan 25, 2008 1:06 PM, Emmanuel Lecharny [EMAIL PROTECTED] wrote: Lian Cheng wrote: Err... so, bug reports for the trunk won't be fixed? 2.0.0-M1 is a milestone, not a release. We can wait forever until the last bug has been fixed, but this does not help a lot projects using MINA ! You have to understand that 2.0.0-M1 will be shortly followed by a 2.0.0-M2. And I think there IS a serious bug, https://issues.apache.org/jira/browse/DIRMINA-515DIRMINA-515 , which prevents XP SP2 users connects to an NioDatagramAcceptor with an NioDatagramConnector. I reported it a few days ago. Actually, last monday. People are quite busy, so it can take time before a bug is fixed. Or if you have a patch, it will be warmly welcomed ! If 2.0.0-M1 release is coming soon, I definitely whish that this bug can be fixed! Otherwise, you can build MINA directly from trunk as soon as your bug has been fixed, and produce your own package. -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org -- Talent hits a target no one else can hit; Genius hits a target no one else can see.
Re: [MINA] 2.0 Milestone 1 ?
I forgot to mention that we need to move transport-serial to sandbox temporarilly due to the LGPL issue. I guess we need to wait for the result of the board meeting which is going to be held on Feb 20. Trustin On Jan 25, 2008 5:56 PM, Trustin Lee [EMAIL PROTECTED] wrote: I'd wait for a new SLF4J release that enables MDC for java.util.logging and consequently simplifies MINA Logging dramatically. That is the only issue to be resolved before we release 2.0.0-M1. Maarten and Ceki is working on it, so let's wait a little bit more for him and Ceki. If the new release of SLF4J is getting late, we can just do what we planned to do; just drop IoSessionLogger and support MDC for JDK later when the new SLF4J is released. Other unscheduled issues are mostly feature addition, unreproduceable bugs or bug reports for the trunk, so we will have to schedule it as soon as 2.0.0-M1 is released. Trustin On Jan 25, 2008 4:13 PM, Emmanuel Lecharny [EMAIL PROTECTED] wrote: Alex Karasulu wrote: Hi all, What does everyone think about a 2.0 milestone release in the near future? After a convo on IRC many feel that milestone releases do not guarantee API stability. If this is the case we could get a milestone out so users can kick the tires on the API changes and give feedback so we can adjust. I would like to see some 2.0 milestones soon There are a few things to work out though : - There are no roadmap atm. Two versions are expected (2.0.0-M1 and 2.0.0-M2), but they barely contains any issue. - There are 44 unscheduled issues. It would be good to schedule those issues into the created milestones - There are only 6 open bugs, so I guess we are close to a milestone, as soon as thise bug are fixed. Now, a lot of improvements are expected to be made, but we don't know which version they are targeting. Generally speaking, it might be a good thing to use JIRA roadmap management a bit more. Hope it helps. -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6 -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
Re: [MINA] 2.0 Milestone 1 ?
On Jan 25, 2008 11:32 AM, Emmanuel Lecharny [EMAIL PROTECTED] wrote: Trustin Lee wrote: He will not mind (TM) :D So... now we can start to drop IoSessionLogger and you could add JUL MDC formatter into org.apache.mina.util, right? Wrong, unless I misunterpreted the meaning of JUL MDC. What are we exactly talking about ? We are not supposed to use JUL, are we ? Yeah I must admit I don't know what's cooking here as well. Can we get an update on what these changes will involve and the impact this will have? Thanks, Alex P.S. I can't believe logging has gotten this damn complicated where I can understand rocket science but not freaking logging speak.
Re: [MINA] 2.0 Milestone 1 ?
On Jan 25, 2008 3:56 AM, Trustin Lee [EMAIL PROTECTED] wrote: I'd wait for a new SLF4J release that enables MDC for java.util.logging and consequently simplifies MINA Logging dramatically. That is the only issue to be resolved before we release 2.0.0-M1. Maarten and Ceki is working on it, so let's wait a little bit more for him and Ceki. What's the ETA on that? Just keep in mind we can release as many times as we want. Nothing holds us back from doing as many milestones as frequently as we like. If the new release of SLF4J is getting late, we can just do what we planned to do; just drop IoSessionLogger and support MDC for JDK later when the new SLF4J is released. Yeah let's get feedback and figure out what to do. Alex
Re: [MINA] 2.0 Milestone 1 ?
Trustin Lee wrote: He will not mind (TM) :D So... now we can start to drop IoSessionLogger and you could add JUL MDC formatter into org.apache.mina.util, right? Wrong, unless I misunterpreted the meaning of JUL MDC. What are we exactly talking about ? We are not supposed to use JUL, are we ? -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org
Re: [MINA] 2.0 Milestone 1 ?
On Jan 25, 2008 5:32 PM, Emmanuel Lecharny [EMAIL PROTECTED] wrote: Trustin Lee wrote: He will not mind (TM) :D So... now we can start to drop IoSessionLogger and you could add JUL MDC formatter into org.apache.mina.util, right? Wrong, unless I misunterpreted the meaning of JUL MDC. What are we exactly talking about ? We are not supposed to use JUL, are we ? Emmanuel, let me recap what has been discussed before. 1) First we had the IoSessionLogger: it can prepend a session-identifier (eg remote addr) to the log-message 2) Then the MdcInjectionFilter was added (it has a very similar goal but uses the MDC mechanism) 3) I proposed to remove IoSessionLogger since we now have the more powerful MdcInjectionFilter but one problem is that java.util.logging is lacking the MDC feature 4) then Ceki has added MDC support for jul to SLF4J but now problem remains that there are now jul formatters that are MDC aware (except the one that I attached to the SLF4J bugzilla ticket, but that one won't be released by SLF4J) 5) Trustin suggested that we add some MDC-aware formatters for JUL to org.apache.mina.util before we remove IoSessionLogger for good. The MDC-aware formatters are 100% optional, it's just to provide jul users a means to use the MdcInjectionFilter. And users of log4j or logback can already use MdcInjectionFilter and that won't change at all. I hope that clears things up ? Maarten
Re: [MINA] 2.0 Milestone 1 ?
On Jan 25, 2008 5:55 PM, Maarten Bosteels [EMAIL PROTECTED] wrote: On Jan 25, 2008 5:32 PM, Emmanuel Lecharny [EMAIL PROTECTED] wrote: Trustin Lee wrote: He will not mind (TM) :D So... now we can start to drop IoSessionLogger and you could add JUL MDC formatter into org.apache.mina.util, right? Wrong, unless I misunterpreted the meaning of JUL MDC. What are we exactly talking about ? We are not supposed to use JUL, are we ? Emmanuel, let me recap what has been discussed before. 1) First we had the IoSessionLogger: it can prepend a session-identifier (eg remote addr) to the log-message 2) Then the MdcInjectionFilter was added (it has a very similar goal but uses the MDC mechanism) 3) I proposed to remove IoSessionLogger since we now have the more powerful MdcInjectionFilter but one problem is that java.util.logging is lacking the MDC feature 4) then Ceki has added MDC support for jul to SLF4J but now problem remains that there are now jul formatters correction: there are now jul formatters should have been there ar NO jul formatters that are MDC aware (except the one that I attached to the SLF4J bugzilla ticket, but that one won't be released by SLF4J) 5) Trustin suggested that we add some MDC-aware formatters for JUL to org.apache.mina.util before we remove IoSessionLogger for good. The MDC-aware formatters are 100% optional, it's just to provide jul users a means to use the MdcInjectionFilter. And users of log4j or logback can already use MdcInjectionFilter and that won't change at all. I hope that clears things up ? Maarten
Re: [MINA] 2.0 Milestone 1 ?
4) then Ceki has added MDC support for jul to SLF4J but now problem remains that there are now jul formatters that are MDC aware (except the one that I attached to the SLF4J bugzilla ticket, but that one won't be released by SLF4J) 5) Trustin suggested that we add some MDC-aware formatters for JUL to org.apache.mina.util before we remove IoSessionLogger for good. Sounds good, so far, unless I miss something :) Thanks for the clarification Maarten ! -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org
