Re: [JBoss-dev] JBossAS-4.0.5.CR1
JBossCache 1.4.0.GA in this release? Brian, any comments, since the main use case for JBoss Cache in AS is clustering? -- Manik Surtani Lead, JBoss Cache JBoss, a division of Red Hat Email: [EMAIL PROTECTED] Telephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo/AIM/Skype: maniksurtani On 6 Jul 2006, at 20:02, Dimitris Andreadis wrote: > Hello, > > JBossAS-4.0.5.CR1 is scheduled for release on the 21st of August. We > really want to keep this release minimal, driven by the most important > user/customer needs, since we have higher priorities (i.e. JB5). > > The list of pending JIRA issues is quite long at this point (138, > due to > overflow from the previous 4.0.4 release) but we'll shamelessly reduce > it by deferring stuff until we get to a manageable set that can be > implemented within the next 4 weeks, in parallel to whatever else you > do. > > August 4th will be the *LAST* day for any new feature/bug fix, after > that it's integration/test tasks only. Please, try to make it for the > target date, we simply can't afford the cost of introducing last > minutes > changes (and it has happened quite a few times before). > > If there are dependencies we should be aware of (your project A, > depends > on project B, that needs unfinished project X), make it clear in JIRA. > If there are other issues (technical or otherwise) make them known > early. > > So the action points: > > 1) Developers/Leads - Browse the JBossAS-4.0.5.CR1 tasks, decide what > can be solved by Aug/4th, reject or defer everything else to > 4.0.6.CR1: > http://jira.jboss.com/jira/browse/JBAS > > 2) Support - Help us define priorities. Raise priorities (Critical) to > the issues that *MUST* make it for the release. Create issues, if > there > is something missing. > > Cheers > /Dimitris > > > -- > > Dimitris Andreadis > AS Development Manager > JBoss, a Division of Red Hat > Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] Re: FW: jboss-4.0.4 portal-2.2 issue
Good point - why doesn't Portal ship with Hibernate configured with JBoss Cache? On 12 May 2006, at 19:34, Adrian Brock wrote: The solutions are: 1) JBoss Portal's session factory is configured to use JBoss Cache not EhCache --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBossCache 1.3.0.SP1 (WAS: JBossCache 1.3.0.GA released)
I have created a new release in JIRA - 1.3.0.SP1Could you pls mark these JIRA tasks as targets for fixing in both 1.4.0 and 1.3.0.SP1 - makes it easy for me to create release notes for 1.3.0.SP1. Please do so even if you've already fixed and closed the JIRA tasks.Thanks!--Manik Surtani[EMAIL PROTECTED]Lead, JBoss CacheTelephone: +44 7786 702 706MSN: [EMAIL PROTECTED]Yahoo: maniksurtaniAIM: maniksurtaniSkype: maniksurtani On 6 Apr 2006, at 19:02, Manik Surtani wrote:Ok, so I have created a branch - Branch_JBossCache_1_3_0Could we make sure any potential fixes for an SP release go here as well as in HEAD.From what I can tell, we have:* Ben's SFSB fixes* The fix to the examples build script* Potential problem with the TreeCache GUI* JBCACHE-531 (Forcing file encodings when reading properties)* JBCACHE-548 (to do with TxManagers in WebLogic and WebSphere)* JBCACHE-534 (documentation typo)What else is critical for this SP? Do we have JIRA tasks for the first 3?Cheers, --Manik Surtani[EMAIL PROTECTED]Lead, JBoss CacheTelephone: +44 7786 702 706MSN: [EMAIL PROTECTED]Yahoo: maniksurtaniAIM: maniksurtaniSkype: maniksurtani On 6 Apr 2006, at 15:55, Ben Wang wrote: What tutorial? It is not broken, AFAIK. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Manik SurtaniSent: Thursday, April 06, 2006 8:16 PMTo: jboss-development@lists.sourceforge.netSubject: Re: [JBoss-dev] JBossCache 1.3.0.GA released Ok. Has the tutorial been fixed as well? -- Manik Surtani [EMAIL PROTECTED] Lead, JBoss Cache Telephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtani On 6 Apr 2006, at 12:36, Ben Wang wrote: Yes, it has. The other two are almost done. Scott Marlow and I need to verify JBCACHE-531 fix. I'd say let's go for QA next Monday then? -Ben From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Manik SurtaniSent: Thursday, April 06, 2006 5:51 PMTo: jboss-development@lists.sourceforge.netSubject: Re: [JBoss-dev] JBossCache 1.3.0.GA released This is a better case. The tutorial issue on its own was not strong enough, IMO. :) Ben, is this fixed in HEAD at the moment?Cheers, -- Manik Surtani [EMAIL PROTECTED]Lead, JBoss CacheTelephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtaniOn 5 Apr 2006, at 21:55, Ryan Campbell wrote: Is this (and the tutorial issue) not a good reason for 1.3.1.CR1? And then 1 week later, once we have a bug free release, we just rename (and retag it) as 1.3.1.GA.From: Ben Wang Sent: Tuesday, April 04, 2006 8:42 PMTo: jboss-development@lists.sourceforge.netCc: QASubject: RE: [JBoss-dev] JBossCache 1.3.0.GA releasedI know this not good timing. :-) But during my work on migrating ejb3 sfsb passivation using JBossCache (http://jira.jboss.com/jira/browse/EJBTHREE-500), I have discovered two bugs. And I will need these two fixed so I can check in my code in head. So first option is to create a patch and use that. Second option is use the snapshot in JBossCache and couting on that 1.4 release will be out soon.I am leaning towards the second option such that if there is any future bug fixes or enahncement then I can create another shapshot right away. What do people think? And how do I do that properly?Thanks,-Ben From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Rajesh RajasekaranSent: Tuesday, April 04, 2006 6:04 AMTo: jboss-development@lists.sourceforge.netCc: QASubject: [JBoss-dev] JBossCache 1.3.0.GA releasedJBossCache 1.3.0.GA “Wasabi” has been released and is available for download athttp://sourceforge.net/project/showfiles.php?group_id=22866&package_id=102339&release_id=406920JBossCache 1.3.0.GA has also been updated in the repository.ThanksRajeshJBoss QA
Re: [JBoss-dev] JBossCache 1.3.0.SP1 (WAS: JBossCache 1.3.0.GA released)
Yup -- Manik Surtani [EMAIL PROTECTED] Lead, JBoss Cache Telephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtani On 6 Apr 2006, at 19:30, Scott Marlow wrote: Sure, is the following command correct for accessing it: cvs co -r Branch_JBossCache_1_3_0 JBossCache Thanks, Scott On Thu, 2006-04-06 at 19:02 +0100, Manik Surtani wrote: Ok, so I have created a branch - Branch_JBossCache_1_3_0 Could we make sure any potential fixes for an SP release go here as well as in HEAD. From what I can tell, we have: * Ben's SFSB fixes * The fix to the examples build script * Potential problem with the TreeCache GUI * JBCACHE-531 (Forcing file encodings when reading properties) * JBCACHE-548 (to do with TxManagers in WebLogic and WebSphere) * JBCACHE-534 (documentation typo) What else is critical for this SP? Do we have JIRA tasks for the first 3? Cheers, -- Manik Surtani [EMAIL PROTECTED] Lead, JBoss Cache Telephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtani On 6 Apr 2006, at 15:55, Ben Wang wrote: What tutorial? It is not broken, AFAIK. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manik Surtani Sent: Thursday, April 06, 2006 8:16 PM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] JBossCache 1.3.0.GA released Ok. Has the tutorial been fixed as well? -- Manik Surtani [EMAIL PROTECTED] Lead, JBoss Cache Telephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtani On 6 Apr 2006, at 12:36, Ben Wang wrote: Yes, it has. The other two are almost done. Scott Marlow and I need to verify JBCACHE-531 fix. I'd say let's go for QA next Monday then? -Ben __ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Manik Surtani Sent: Thursday, April 06, 2006 5:51 PM To: jboss-development@lists.sourceforge.net Subject: Re: [JBoss-dev] JBossCache 1.3.0.GA released This is a better case. The tutorial issue on its own was not strong enough, IMO. :) Ben, is this fixed in HEAD at the moment? Cheers, -- Manik Surtani [EMAIL PROTECTED] Lead, JBoss Cache Telephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtani On 5 Apr 2006, at 21:55, Ryan Campbell wrote: Is this (and the tutorial issue) not a good reason for 1.3.1.CR1? And then 1 week later, once we have a bug free release, we just rename (and retag it) as 1.3.1.GA. From: Ben Wang Sent: Tuesday, April 04, 2006 8:42 PM To: jboss-development@lists.sourceforge.net Cc: QA Subject: RE: [JBoss-dev] JBossCache 1.3.0.GA released I know this not good timing. :-) But during my work on migrating ejb3 sfsb passivation using JBossCache (http://jira.jboss.com/jira/browse/EJBTHREE-500), I have discovered two bugs. And I will need these two fixed so I can check in my code in head. So first option is to create a patch and use that. Second option is use the snapshot in JBossCache and couting on that 1.4 release will be out soon. I am leaning towards the second option such that if there is any future bug fixes or enahncement then I can create another shapshot right away. What do people think? And how do I do that properly? Thanks, -Ben From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rajesh Rajasekaran Sent: Tuesday, April 04, 2006 6:04 AM To: jboss-development@lists.sourceforge.net Cc: QA Subject: [JBoss-dev] JBossCache 1.3.0.GA released JBossCache 1.3.0.GA “Wasabi” has been released and is available for download at http://sourceforge.net/project/showfiles.php? group_id=22866&package_id=102339&release_id=406920 JBossCache 1.3.0.GA has also been updated in the repository. Thanks Rajesh JBoss QA --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel? cmd=lnk&kid=110944&bid=241720&dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel
[JBoss-dev] JBossCache 1.3.0.SP1 (WAS: JBossCache 1.3.0.GA released)
Ok, so I have created a branch - Branch_JBossCache_1_3_0Could we make sure any potential fixes for an SP release go here as well as in HEAD.From what I can tell, we have:* Ben's SFSB fixes* The fix to the examples build script* Potential problem with the TreeCache GUI* JBCACHE-531 (Forcing file encodings when reading properties)* JBCACHE-548 (to do with TxManagers in WebLogic and WebSphere)* JBCACHE-534 (documentation typo)What else is critical for this SP? Do we have JIRA tasks for the first 3?Cheers, --Manik Surtani[EMAIL PROTECTED]Lead, JBoss CacheTelephone: +44 7786 702 706MSN: [EMAIL PROTECTED]Yahoo: maniksurtaniAIM: maniksurtaniSkype: maniksurtani On 6 Apr 2006, at 15:55, Ben Wang wrote: What tutorial? It is not broken, AFAIK. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Manik SurtaniSent: Thursday, April 06, 2006 8:16 PMTo: jboss-development@lists.sourceforge.netSubject: Re: [JBoss-dev] JBossCache 1.3.0.GA released Ok. Has the tutorial been fixed as well? -- Manik Surtani [EMAIL PROTECTED] Lead, JBoss Cache Telephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtani On 6 Apr 2006, at 12:36, Ben Wang wrote: Yes, it has. The other two are almost done. Scott Marlow and I need to verify JBCACHE-531 fix. I'd say let's go for QA next Monday then? -Ben From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Manik SurtaniSent: Thursday, April 06, 2006 5:51 PMTo: jboss-development@lists.sourceforge.netSubject: Re: [JBoss-dev] JBossCache 1.3.0.GA released This is a better case. The tutorial issue on its own was not strong enough, IMO. :) Ben, is this fixed in HEAD at the moment?Cheers,-- Manik Surtani [EMAIL PROTECTED]Lead, JBoss CacheTelephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtaniOn 5 Apr 2006, at 21:55, Ryan Campbell wrote: Is this (and the tutorial issue) not a good reason for 1.3.1.CR1? And then 1 week later, once we have a bug free release, we just rename (and retag it) as 1.3.1.GA.From: Ben Wang Sent: Tuesday, April 04, 2006 8:42 PMTo: jboss-development@lists.sourceforge.netCc: QASubject: RE: [JBoss-dev] JBossCache 1.3.0.GA releasedI know this not good timing. :-) But during my work on migrating ejb3 sfsb passivation using JBossCache (http://jira.jboss.com/jira/browse/EJBTHREE-500), I have discovered two bugs. And I will need these two fixed so I can check in my code in head. So first option is to create a patch and use that. Second option is use the snapshot in JBossCache and couting on that 1.4 release will be out soon.I am leaning towards the second option such that if there is any future bug fixes or enahncement then I can create another shapshot right away. What do people think? And how do I do that properly?Thanks,-Ben From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Rajesh RajasekaranSent: Tuesday, April 04, 2006 6:04 AMTo: jboss-development@lists.sourceforge.netCc: QASubject: [JBoss-dev] JBossCache 1.3.0.GA releasedJBossCache 1.3.0.GA “Wasabi” has been released and is available for download athttp://sourceforge.net/project/showfiles.php?group_id=22866&package_id=102339&release_id=406920JBossCache 1.3.0.GA has also been updated in the repository.ThanksRajeshJBoss QA
Re: [JBoss-dev] JBossCache 1.3.0.GA released + a change to how we deal with java.util.properties
Escaping single backslashes is probably not a good idea. What if I
want to pass in (for some obscure reason) a \n ? I'd expect this to
be translated to a new line, not the string "\\n".
I think we just mandate that users passing in backslashes as a part
of a path construct use double-backslashes. Fair assumption I'd
assume (it's what I'd do anyway if specifying Windows paths in a Java
propfile.)
--
Manik Surtani
[EMAIL PROTECTED]
Lead, JBoss Cache
Telephone: +44 7786 702 706
MSN: [EMAIL PROTECTED]
Yahoo: maniksurtani
AIM: maniksurtani
Skype: maniksurtani
On 6 Apr 2006, at 14:12, Scott Marlow wrote:
It turns out that the root cause behind JBCACHE-531 is deeper than I
thought.
After fixing a minor international character support issue in
org.jboss.cache.config.CacheLoaderConfig (we were calling
String.getBytes() without specifying an encoding). I then came across
the same issue in
org.jboss.util.propertyeditor.PropertiesEditor.getValue(). I fixed
the
character encoding issue locally but I'm not sure of how to fix the
deeper issue.
Before I move into the deeper issue, let me explain the problem with
calling String.getBytes() without specifying an encoding (before
someone
flames me :). String.getBytes() will return a byte array
containing the
character values converted into the default platform encoding (perhaps
big5 or utf8 or perhaps latin1). In the two code sites mentioned
above,
we are passing the byte array into java.util.properties which always
wants encoding "ISO8859_1".
The deeper issue:
org.jboss.util.propertyeditor.PropertiesEditor.getValue() is
expected to
take a Java String value and parse it java.util.properties style.
However, we also support expanding JBoss system expressions that
can be
invalid when passed into java.util.properties.load() as we do.
For example, if the expression "${jboss.server.data.dir}" is passed in
and you are running on Windows, the intermediate result might be path
"c:\jboss\server\all\data". The output of java.util.properties.load
will be something like: "c: boss erver ll ata".
This creates a blocking problem for our sfsb fine grained replication
project. :(
Should we try to hack the expansion of jboss system expressions to
double escape the "\" escape character?
This seems like a tricky path to follow as I'm not sure if we
should do
the same for values that are simply passed in. For instance, are
users
expected to hard code paths in configuration files like this?
mytempdir=c:\temp
or like this:
mytempdir=c:\\temp
In one case, they already hit the bug that requires "\" to be doubled.
If I add code that doubles their "\", then we might end up with
something like "mytempdir=c:temp" (assuming that they already
doubled them). I suppose we could detect if the "\" characters are
already escaped and don't escape them again if so.
This also seems like a big change to make so near the end of the 4.0.4
release. I'll create a Jira for 4.0.4 unless someone talks me out of
making this change.
What is the right thing to do here?
On Thu, 2006-04-06 at 06:36 -0500, Ben Wang wrote:
Yes, it has. The other two are almost done. Scott Marlow and I
need to
verify JBCACHE-531 fix. I'd say let's go for QA next Monday then?
-Ben
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting
language
that extends applications into web and mobile media. Attend the
live webcast
and join the prime developer group breaking into this new coding
territory!
http://sel.as-us.falkag.net/sel?
cmd=lnk&kid=110944&bid=241720&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: [JBoss-dev] JBossCache 1.3.0.GA released
Also, we need to branch 1.3.0 for this. Let me create one and I'll send you the branch tag. Too many half baked 1.4.0 features in HEAD now. --Manik Surtani[EMAIL PROTECTED]Lead, JBoss CacheTelephone: +44 7786 702 706MSN: [EMAIL PROTECTED]Yahoo: maniksurtaniAIM: maniksurtaniSkype: maniksurtani On 6 Apr 2006, at 12:36, Ben Wang wrote: Yes, it has. The other two are almost done. Scott Marlow and I need to verify JBCACHE-531 fix. I'd say let's go for QA next Monday then? -Ben From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Manik SurtaniSent: Thursday, April 06, 2006 5:51 PMTo: jboss-development@lists.sourceforge.netSubject: Re: [JBoss-dev] JBossCache 1.3.0.GA released This is a better case. The tutorial issue on its own was not strong enough, IMO. :) Ben, is this fixed in HEAD at the moment? Cheers, -- Manik Surtani [EMAIL PROTECTED] Lead, JBoss Cache Telephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtani On 5 Apr 2006, at 21:55, Ryan Campbell wrote: Is this (and the tutorial issue) not a good reason for 1.3.1.CR1? And then 1 week later, once we have a bug free release, we just rename (and retag it) as 1.3.1.GA.From: Ben Wang Sent: Tuesday, April 04, 2006 8:42 PMTo: jboss-development@lists.sourceforge.netCc: QASubject: RE: [JBoss-dev] JBossCache 1.3.0.GA releasedI know this not good timing. :-) But during my work on migrating ejb3 sfsb passivation using JBossCache (http://jira.jboss.com/jira/browse/EJBTHREE-500), I have discovered two bugs. And I will need these two fixed so I can check in my code in head. So first option is to create a patch and use that. Second option is use the snapshot in JBossCache and couting on that 1.4 release will be out soon.I am leaning towards the second option such that if there is any future bug fixes or enahncement then I can create another shapshot right away. What do people think? And how do I do that properly?Thanks,-Ben From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Rajesh RajasekaranSent: Tuesday, April 04, 2006 6:04 AMTo: jboss-development@lists.sourceforge.netCc: QASubject: [JBoss-dev] JBossCache 1.3.0.GA releasedJBossCache 1.3.0.GA “Wasabi” has been released and is available for download athttp://sourceforge.net/project/showfiles.php?group_id=22866&package_id=102339&release_id=406920JBossCache 1.3.0.GA has also been updated in the repository.ThanksRajeshJBoss QA
Re: [JBoss-dev] JBossCache 1.3.0.GA released
Ok. Has the tutorial been fixed as well? --Manik Surtani[EMAIL PROTECTED]Lead, JBoss CacheTelephone: +44 7786 702 706MSN: [EMAIL PROTECTED]Yahoo: maniksurtaniAIM: maniksurtaniSkype: maniksurtani On 6 Apr 2006, at 12:36, Ben Wang wrote: Yes, it has. The other two are almost done. Scott Marlow and I need to verify JBCACHE-531 fix. I'd say let's go for QA next Monday then? -Ben From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Manik SurtaniSent: Thursday, April 06, 2006 5:51 PMTo: jboss-development@lists.sourceforge.netSubject: Re: [JBoss-dev] JBossCache 1.3.0.GA released This is a better case. The tutorial issue on its own was not strong enough, IMO. :) Ben, is this fixed in HEAD at the moment? Cheers, -- Manik Surtani [EMAIL PROTECTED] Lead, JBoss Cache Telephone: +44 7786 702 706 MSN: [EMAIL PROTECTED] Yahoo: maniksurtani AIM: maniksurtani Skype: maniksurtani On 5 Apr 2006, at 21:55, Ryan Campbell wrote: Is this (and the tutorial issue) not a good reason for 1.3.1.CR1? And then 1 week later, once we have a bug free release, we just rename (and retag it) as 1.3.1.GA.From: Ben Wang Sent: Tuesday, April 04, 2006 8:42 PMTo: jboss-development@lists.sourceforge.netCc: QASubject: RE: [JBoss-dev] JBossCache 1.3.0.GA releasedI know this not good timing. :-) But during my work on migrating ejb3 sfsb passivation using JBossCache (http://jira.jboss.com/jira/browse/EJBTHREE-500), I have discovered two bugs. And I will need these two fixed so I can check in my code in head. So first option is to create a patch and use that. Second option is use the snapshot in JBossCache and couting on that 1.4 release will be out soon.I am leaning towards the second option such that if there is any future bug fixes or enahncement then I can create another shapshot right away. What do people think? And how do I do that properly?Thanks,-Ben From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Rajesh RajasekaranSent: Tuesday, April 04, 2006 6:04 AMTo: jboss-development@lists.sourceforge.netCc: QASubject: [JBoss-dev] JBossCache 1.3.0.GA releasedJBossCache 1.3.0.GA “Wasabi” has been released and is available for download athttp://sourceforge.net/project/showfiles.php?group_id=22866&package_id=102339&release_id=406920JBossCache 1.3.0.GA has also been updated in the repository.ThanksRajeshJBoss QA
Re: [JBoss-dev] JBossCache 1.3.0.GA released
This is a better case. The tutorial issue on its own was not strong enough, IMO. :)Ben, is this fixed in HEAD at the moment?Cheers, --Manik Surtani[EMAIL PROTECTED]Lead, JBoss CacheTelephone: +44 7786 702 706MSN: [EMAIL PROTECTED]Yahoo: maniksurtaniAIM: maniksurtaniSkype: maniksurtani On 5 Apr 2006, at 21:55, Ryan Campbell wrote:Is this (and the tutorial issue) not a good reason for 1.3.1.CR1? And then 1 week later, once we have a bug free release, we just rename (and retag it) as 1.3.1.GA. From: Ben Wang Sent: Tuesday, April 04, 2006 8:42 PMTo: jboss-development@lists.sourceforge.netCc: QASubject: RE: [JBoss-dev] JBossCache 1.3.0.GA released I know this not good timing. :-) But during my work on migrating ejb3 sfsb passivation using JBossCache (http://jira.jboss.com/jira/browse/EJBTHREE-500), I have discovered two bugs. And I will need these two fixed so I can check in my code in head. So first option is to create a patch and use that. Second option is use the snapshot in JBossCache and couting on that 1.4 release will be out soon. I am leaning towards the second option such that if there is any future bug fixes or enahncement then I can create another shapshot right away. What do people think? And how do I do that properly? Thanks, -Ben From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Rajesh RajasekaranSent: Tuesday, April 04, 2006 6:04 AMTo: jboss-development@lists.sourceforge.netCc: QASubject: [JBoss-dev] JBossCache 1.3.0.GA releasedJBossCache 1.3.0.GA “Wasabi” has been released and is available for download athttp://sourceforge.net/project/showfiles.php?group_id=22866&package_id=102339&release_id=406920 JBossCache 1.3.0.GA has also been updated in the repository. ThanksRajeshJBoss QA
