Re: [transaction] Release plan?
Oliver Zeigermann oliver.zeigermann at gmail.com writes: Also what is the minimum JDK version for transaction? I used ant for the previous releases (target package). Minimum jdk is 1.2 Has anybody actually been checking this? Setting those properties has probably influence on the compiler (e.g. complain about newer language constructs (asserts, etc.) and the generated bytecode), but not on the available API I think. Despite bytecode compatibility you might end with ClassNotFoundExceptions and NoSuchMethodExceptions when using JDK 1.3+ API. Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction] Release plan?
On 7/15/06, Joerg Heinicke [EMAIL PROTECTED] wrote: Oliver Zeigermann oliver.zeigermann at gmail.com writes: Also what is the minimum JDK version for transaction? I used ant for the previous releases (target package). Minimum jdk is 1.2 Has anybody actually been checking this? Setting those properties has probably influence on the compiler (e.g. complain about newer language constructs (asserts, etc.) and the generated bytecode), but not on the available API I think. Despite bytecode compatibility you might end with ClassNotFoundExceptions and NoSuchMethodExceptions when using JDK 1.3+ API. I just tried compiling using JDK 1.3 1) The maven build doesn't work because geronimo has been built using JDK 1.4(compile fails complaining class file has the wrong version 48.0, should be 47.0 for one of the javax.transaction classes) 2) I got the ant build to work by doing the following: - plug in alternative j2ee and servlet jars (rather than geronimo) - change the order of the classpath in build.xml to pick up the alternative jars before whats in the lib directory (i.e. geronimo) - add an exclude for the Jdk14Logger class - modify FileResourceManager - it uses a JDK 1.4 constructor of FileOutputStream So it seem that for JDK 1.3 the only real issue is in FileResourceManager. Another thing I noticed - the build.xml sets the compile target to 1.3 - so maybe I should switch back the equivalent maven settings (I added them as 1.3 and then switched to 1.2 yesterday, following Oliver's comment). I've changed the build.xml to resolve the JDK 1.3 issues there - but have left the FileResourceManager issue for someone else to deal with. http://svn.apache.org/viewvc?view=revrevision=422213 Niall Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction] Release plan?
Niall Pemberton niall.pemberton at gmail.com writes: Has anybody actually been checking this? I just tried compiling using JDK 1.3 Thanks. So it seem that for JDK 1.3 the only real issue is in FileResourceManager. It was me who introduced it :) Fixed it ... Another thing I noticed - the build.xml sets the compile target to 1.3 - so maybe I should switch back the equivalent maven settings (I added them as 1.3 and then switched to 1.2 yesterday, following Oliver's comment). So switching back to 1.3? Oliver? I've changed the build.xml to resolve the JDK 1.3 issues there - but have left the FileResourceManager issue for someone else to deal with. You could commit this as well as easy as it was :) Cheers, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction] Release plan?
Oliver Zeigermann oliver.zeigermann at gmail.com writes: Excatly! That's just what I was proposing in my last email! 2006/7/13, Henri Yandell flamefew at gmail.com: Is the aim to have a 1.2 release of transaction at some point? Yes, I would like to see a 1.2 release as well. There are enough fixes and enhancements that qualify for a new release. What's the actual release process (code freeze, etc.)? RELEASE-NOTES.txt talks about 1.1.1 while we now will probably name it 1.2 btw. Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction] Release plan?
2006/7/14, Joerg Heinicke [EMAIL PROTECTED]: Oliver Zeigermann oliver.zeigermann at gmail.com writes: Excatly! That's just what I was proposing in my last email! 2006/7/13, Henri Yandell flamefew at gmail.com: Is the aim to have a 1.2 release of transaction at some point? Yes, I would like to see a 1.2 release as well. There are enough fixes and enhancements that qualify for a new release. What's the actual release process (code freeze, etc.)? Feature freeze for 1.2 is exactly now ;) More info can be found here: http://jakarta.apache.org/commons/releases/release.html http://jakarta.apache.org/commons/releases/prepare.html I'd go for a release candidate right now, skipping betas. Opinions? RELEASE-NOTES.txt talks about 1.1.1 while we now will probably name it 1.2 btw. Oh, right. Will fix this. Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction] Release plan?
2006/7/14, Henri Yandell [EMAIL PROTECTED]: On 7/13/06, Oliver Zeigermann [EMAIL PROTECTED] wrote: Excatly! That's just what I was proposing in my last email! Would you want to assist? Definitely happy to assist with getting the release out there etc. No real itch on transactions themselves, but I want to do what I can to speed up our release cycles. Cool :) I'll go through jira tonight and do the same thing I'll do for Pool; add version information for all new/old issues. Great! Thanks a lot! Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction] Release plan?
2006/7/14, Niall Pemberton [EMAIL PROTECTED]: On 7/13/06, Henri Yandell [EMAIL PROTECTED] wrote: On 7/13/06, Oliver Zeigermann [EMAIL PROTECTED] wrote: Excatly! That's just what I was proposing in my last email! Would you want to assist? Definitely happy to assist with getting the release out there etc. No real itch on transactions themselves, but I want to do what I can to speed up our release cycles. I don't have an itch/need for transaction either but am also happy to help with build/site issues that normally get raised with release candidates, if you want. Nice. I will certainly came back to you with questions ;) Is maven the primary build mechanism (i.e. the one you use for release)? Also what is the minimum JDK version for transaction? I used ant for the previous releases (target package). Minimum jdk is 1.2 Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction] Release plan?
On 7/14/06, Oliver Zeigermann [EMAIL PROTECTED] wrote: 2006/7/14, Niall Pemberton [EMAIL PROTECTED]: On 7/13/06, Henri Yandell [EMAIL PROTECTED] wrote: On 7/13/06, Oliver Zeigermann [EMAIL PROTECTED] wrote: Excatly! That's just what I was proposing in my last email! Would you want to assist? Definitely happy to assist with getting the release out there etc. No real itch on transactions themselves, but I want to do what I can to speed up our release cycles. I don't have an itch/need for transaction either but am also happy to help with build/site issues that normally get raised with release candidates, if you want. Nice. I will certainly came back to you with questions ;) Is maven the primary build mechanism (i.e. the one you use for release)? Also what is the minimum JDK version for transaction? I used ant for the previous releases (target package). Minimum jdk is 1.2 OK, I updated the maven build earlier which even if you still use ant, is good to have - I set maven.compile.target and maven compile.source in project.properties to JDK 1.3, so you may want to correct those (or I can) Niall Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction] Release plan?
2006/7/14, Niall Pemberton [EMAIL PROTECTED]: On 7/14/06, Oliver Zeigermann [EMAIL PROTECTED] wrote: 2006/7/14, Niall Pemberton [EMAIL PROTECTED]: On 7/13/06, Henri Yandell [EMAIL PROTECTED] wrote: On 7/13/06, Oliver Zeigermann [EMAIL PROTECTED] wrote: Excatly! That's just what I was proposing in my last email! Would you want to assist? Definitely happy to assist with getting the release out there etc. No real itch on transactions themselves, but I want to do what I can to speed up our release cycles. I don't have an itch/need for transaction either but am also happy to help with build/site issues that normally get raised with release candidates, if you want. Nice. I will certainly came back to you with questions ;) Is maven the primary build mechanism (i.e. the one you use for release)? Also what is the minimum JDK version for transaction? I used ant for the previous releases (target package). Minimum jdk is 1.2 OK, I updated the maven build earlier which even if you still use ant, is good to have - I set maven.compile.target and maven compile.source in project.properties to JDK 1.3, so you may want to correct those (or I can) Anything you can do for maven, please do! My tool is ant and I am always lost with maven! Thanks a lot in advance Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[transaction] Release plan?
Is the aim to have a 1.2 release of transaction at some point? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction] Release plan?
Excatly! That's just what I was proposing in my last email! Would you want to assist? Hihi Oliver 2006/7/13, Henri Yandell [EMAIL PROTECTED]: Is the aim to have a 1.2 release of transaction at some point? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction] Release plan?
The current transaction site is using the old way of building sites. Do you mind if I change it to the new way? -- Dennis Lundberg Oliver Zeigermann wrote: Excatly! That's just what I was proposing in my last email! Would you want to assist? Hihi Oliver 2006/7/13, Henri Yandell [EMAIL PROTECTED]: Is the aim to have a 1.2 release of transaction at some point? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction] Release plan?
No, go ahead! Thanks Oliver 2006/7/13, Dennis Lundberg [EMAIL PROTECTED]: The current transaction site is using the old way of building sites. Do you mind if I change it to the new way? -- Dennis Lundberg Oliver Zeigermann wrote: Excatly! That's just what I was proposing in my last email! Would you want to assist? Hihi Oliver 2006/7/13, Henri Yandell [EMAIL PROTECTED]: Is the aim to have a 1.2 release of transaction at some point? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction] Release plan?
On 7/13/06, Oliver Zeigermann [EMAIL PROTECTED] wrote: Excatly! That's just what I was proposing in my last email! Would you want to assist? Definitely happy to assist with getting the release out there etc. No real itch on transactions themselves, but I want to do what I can to speed up our release cycles. I'll go through jira tonight and do the same thing I'll do for Pool; add version information for all new/old issues. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [transaction] Release plan?
On 7/13/06, Henri Yandell [EMAIL PROTECTED] wrote: On 7/13/06, Oliver Zeigermann [EMAIL PROTECTED] wrote: Excatly! That's just what I was proposing in my last email! Would you want to assist? Definitely happy to assist with getting the release out there etc. No real itch on transactions themselves, but I want to do what I can to speed up our release cycles. I don't have an itch/need for transaction either but am also happy to help with build/site issues that normally get raised with release candidates, if you want. Is maven the primary build mechanism (i.e. the one you use for release)? Also what is the minimum JDK version for transaction? Niall I'll go through jira tonight and do the same thing I'll do for Pool; add version information for all new/old issues. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
