Re: Time to release TomEE 1.6.0
Hello: Our tests with the TomEE 1.6.0 plus preview binaries are successful, both in our manual and automated tests (we do not use any other TomEE or OpenEJB packages). Now our pressure is people asking when TomEE 1.6.0 will officially be accessible from the TomEE download page. Thanks, Alex. On Sat, Nov 9, 2013 at 11:44 AM, Alex The Rocker alex.m3...@gmail.comwrote: Jean-Louis: I noticed it and I already pushed the information in my compagny for our QA development teams to test ASAP and report any issue. I'll keep you updated Thanks, Alex On Sat, Nov 9, 2013 at 11:39 AM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: Hey guys, Preview binaries are up. Give it a try please and give feedback please, whatever it is (work or not). All information are available on the other thread. JLouis 2013/11/8 David Blevins david.blev...@gmail.com Ended up having to split the OpenJPA source out to a different build due to shade plugin limitations -- you don't get the shaded version if it's being created in your same build. Our TomEE zips and tars were 5mb bigger due to having both he shaded OpenJPA and the individual jars that make the shaded OpenJPA jar. Cleaned that up and finally got it into nexus -- deploys continue to fail, so determination is required. Going to try and get some sleep. Jean-Louis staying on to get non-bloated zips up. -David On Nov 8, 2013, at 3:15 AM, David Blevins david.blev...@gmail.com wrote: On Nov 8, 2013, at 1:38 AM, Mark Struberg strub...@yahoo.de wrote: The issue with openjpa-2.3.0 is a regression which only hits you seldom. See OPENJPA-2335 I found it when I tried to use @OrderColumn. It would be easy to fix this by rolling back Pinakis changes. But there might have been a good reason for those changes. I'm on a conf today and have to deliver 2 more talks. After that I will be able to work on that stuff again and hope I get this fixed till Sunday. I suggest Romain and I fix OpenJPA and we start a release of OWB and OpenJPA immediately after that. I just finished reverting OPENJPA-2335 in the 1.6.0 branch. Just need an OWB build than can put up a preview build of TomEE and get some sleep. Fine if it's not the final build. Need to get a jump on TCK and the rest of the TomEE process that really only starts once we have a build to try. -David -- Jean-Louis
Re: Time to release TomEE 1.6.0
FYI (unrelated but still). Currently running the 'real' openjpa-2.3.0 release tasks Wish me luck... LieGrue, strub - Original Message - From: Alex The Rocker alex.m3...@gmail.com To: dev@tomee.apache.org Cc: Sent: Monday, 11 November 2013, 20:31 Subject: Re: Time to release TomEE 1.6.0 Hello: Our tests with the TomEE 1.6.0 plus preview binaries are successful, both in our manual and automated tests (we do not use any other TomEE or OpenEJB packages). Now our pressure is people asking when TomEE 1.6.0 will officially be accessible from the TomEE download page. Thanks, Alex. On Sat, Nov 9, 2013 at 11:44 AM, Alex The Rocker alex.m3...@gmail.comwrote: Jean-Louis: I noticed it and I already pushed the information in my compagny for our QA development teams to test ASAP and report any issue. I'll keep you updated Thanks, Alex On Sat, Nov 9, 2013 at 11:39 AM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: Hey guys, Preview binaries are up. Give it a try please and give feedback please, whatever it is (work or not). All information are available on the other thread. JLouis 2013/11/8 David Blevins david.blev...@gmail.com Ended up having to split the OpenJPA source out to a different build due to shade plugin limitations -- you don't get the shaded version if it's being created in your same build. Our TomEE zips and tars were 5mb bigger due to having both he shaded OpenJPA and the individual jars that make the shaded OpenJPA jar. Cleaned that up and finally got it into nexus -- deploys continue to fail, so determination is required. Going to try and get some sleep. Jean-Louis staying on to get non-bloated zips up. -David On Nov 8, 2013, at 3:15 AM, David Blevins david.blev...@gmail.com wrote: On Nov 8, 2013, at 1:38 AM, Mark Struberg strub...@yahoo.de wrote: The issue with openjpa-2.3.0 is a regression which only hits you seldom. See OPENJPA-2335 I found it when I tried to use @OrderColumn. It would be easy to fix this by rolling back Pinakis changes. But there might have been a good reason for those changes. I'm on a conf today and have to deliver 2 more talks. After that I will be able to work on that stuff again and hope I get this fixed till Sunday. I suggest Romain and I fix OpenJPA and we start a release of OWB and OpenJPA immediately after that. I just finished reverting OPENJPA-2335 in the 1.6.0 branch. Just need an OWB build than can put up a preview build of TomEE and get some sleep. Fine if it's not the final build. Need to get a jump on TCK and the rest of the TomEE process that really only starts once we have a build to try. -David -- Jean-Louis
Re: Time to release TomEE 1.6.0
Good luck Mark! Thks if not obvious! Le 11 nov. 2013 20:50, Mark Struberg strub...@yahoo.de a écrit : FYI (unrelated but still). Currently running the 'real' openjpa-2.3.0 release tasks Wish me luck... LieGrue, strub - Original Message - From: Alex The Rocker alex.m3...@gmail.com To: dev@tomee.apache.org Cc: Sent: Monday, 11 November 2013, 20:31 Subject: Re: Time to release TomEE 1.6.0 Hello: Our tests with the TomEE 1.6.0 plus preview binaries are successful, both in our manual and automated tests (we do not use any other TomEE or OpenEJB packages). Now our pressure is people asking when TomEE 1.6.0 will officially be accessible from the TomEE download page. Thanks, Alex. On Sat, Nov 9, 2013 at 11:44 AM, Alex The Rocker alex.m3...@gmail.comwrote: Jean-Louis: I noticed it and I already pushed the information in my compagny for our QA development teams to test ASAP and report any issue. I'll keep you updated Thanks, Alex On Sat, Nov 9, 2013 at 11:39 AM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: Hey guys, Preview binaries are up. Give it a try please and give feedback please, whatever it is (work or not). All information are available on the other thread. JLouis 2013/11/8 David Blevins david.blev...@gmail.com Ended up having to split the OpenJPA source out to a different build due to shade plugin limitations -- you don't get the shaded version if it's being created in your same build. Our TomEE zips and tars were 5mb bigger due to having both he shaded OpenJPA and the individual jars that make the shaded OpenJPA jar. Cleaned that up and finally got it into nexus -- deploys continue to fail, so determination is required. Going to try and get some sleep. Jean-Louis staying on to get non-bloated zips up. -David On Nov 8, 2013, at 3:15 AM, David Blevins david.blev...@gmail.com wrote: On Nov 8, 2013, at 1:38 AM, Mark Struberg strub...@yahoo.de wrote: The issue with openjpa-2.3.0 is a regression which only hits you seldom. See OPENJPA-2335 I found it when I tried to use @OrderColumn. It would be easy to fix this by rolling back Pinakis changes. But there might have been a good reason for those changes. I'm on a conf today and have to deliver 2 more talks. After that I will be able to work on that stuff again and hope I get this fixed till Sunday. I suggest Romain and I fix OpenJPA and we start a release of OWB and OpenJPA immediately after that. I just finished reverting OPENJPA-2335 in the 1.6.0 branch. Just need an OWB build than can put up a preview build of TomEE and get some sleep. Fine if it's not the final build. Need to get a jump on TCK and the rest of the TomEE process that really only starts once we have a build to try. -David -- Jean-Louis
Re: Time to release TomEE 1.6.0
Hey guys, Preview binaries are up. Give it a try please and give feedback please, whatever it is (work or not). All information are available on the other thread. JLouis 2013/11/8 David Blevins david.blev...@gmail.com Ended up having to split the OpenJPA source out to a different build due to shade plugin limitations -- you don't get the shaded version if it's being created in your same build. Our TomEE zips and tars were 5mb bigger due to having both he shaded OpenJPA and the individual jars that make the shaded OpenJPA jar. Cleaned that up and finally got it into nexus -- deploys continue to fail, so determination is required. Going to try and get some sleep. Jean-Louis staying on to get non-bloated zips up. -David On Nov 8, 2013, at 3:15 AM, David Blevins david.blev...@gmail.com wrote: On Nov 8, 2013, at 1:38 AM, Mark Struberg strub...@yahoo.de wrote: The issue with openjpa-2.3.0 is a regression which only hits you seldom. See OPENJPA-2335 I found it when I tried to use @OrderColumn. It would be easy to fix this by rolling back Pinakis changes. But there might have been a good reason for those changes. I'm on a conf today and have to deliver 2 more talks. After that I will be able to work on that stuff again and hope I get this fixed till Sunday. I suggest Romain and I fix OpenJPA and we start a release of OWB and OpenJPA immediately after that. I just finished reverting OPENJPA-2335 in the 1.6.0 branch. Just need an OWB build than can put up a preview build of TomEE and get some sleep. Fine if it's not the final build. Need to get a jump on TCK and the rest of the TomEE process that really only starts once we have a build to try. -David -- Jean-Louis
Re: Time to release TomEE 1.6.0
Jean-Louis: I noticed it and I already pushed the information in my compagny for our QA development teams to test ASAP and report any issue. I'll keep you updated Thanks, Alex On Sat, Nov 9, 2013 at 11:39 AM, Jean-Louis MONTEIRO jeano...@gmail.comwrote: Hey guys, Preview binaries are up. Give it a try please and give feedback please, whatever it is (work or not). All information are available on the other thread. JLouis 2013/11/8 David Blevins david.blev...@gmail.com Ended up having to split the OpenJPA source out to a different build due to shade plugin limitations -- you don't get the shaded version if it's being created in your same build. Our TomEE zips and tars were 5mb bigger due to having both he shaded OpenJPA and the individual jars that make the shaded OpenJPA jar. Cleaned that up and finally got it into nexus -- deploys continue to fail, so determination is required. Going to try and get some sleep. Jean-Louis staying on to get non-bloated zips up. -David On Nov 8, 2013, at 3:15 AM, David Blevins david.blev...@gmail.com wrote: On Nov 8, 2013, at 1:38 AM, Mark Struberg strub...@yahoo.de wrote: The issue with openjpa-2.3.0 is a regression which only hits you seldom. See OPENJPA-2335 I found it when I tried to use @OrderColumn. It would be easy to fix this by rolling back Pinakis changes. But there might have been a good reason for those changes. I'm on a conf today and have to deliver 2 more talks. After that I will be able to work on that stuff again and hope I get this fixed till Sunday. I suggest Romain and I fix OpenJPA and we start a release of OWB and OpenJPA immediately after that. I just finished reverting OPENJPA-2335 in the 1.6.0 branch. Just need an OWB build than can put up a preview build of TomEE and get some sleep. Fine if it's not the final build. Need to get a jump on TCK and the rest of the TomEE process that really only starts once we have a build to try. -David -- Jean-Louis
Re: Time to release TomEE 1.6.0
The issue with openjpa-2.3.0 is a regression which only hits you seldom. See OPENJPA-2335 I found it when I tried to use @OrderColumn. It would be easy to fix this by rolling back Pinakis changes. But there might have been a good reason for those changes. I'm on a conf today and have to deliver 2 more talks. After that I will be able to work on that stuff again and hope I get this fixed till Sunday. I suggest Romain and I fix OpenJPA and we start a release of OWB and OpenJPA immediately after that. So Alex, if you need a TomEE release, why don't you just set the version to some internal number and rolle your private intermediate release yourself? This is really not more than mvn clean source:jar deploy -DskipTests=true We should have the TomEE release final somewhen this week. David now runs a company with commercial support even, so if you need help with an internal release then I bet he can help you. This is OpenSource, but we are no free candy gift shop. We all take a lot of heart but also time and money into TomEE and other ASF projects. But not because we are bored! We really use that stuff in our own projects. We are very happy to get feedback. We are also very happy if tomee users are happy. We also understand that some users have time constraints. But we would be even happier if people don't see all the work we do as granted for free. don't take it personal, just needed to be said ;) LieGrue, strub From: Romain Manni-Bucau rmannibu...@gmail.com To: dev@tomee.apache.org Sent: Friday, 8 November 2013, 6:58 Subject: Re: Time to release TomEE 1.6.0 Ping Mark to know what is the openjpa regression. If blocking wait openjpa (or do the fix), if not B (or with the fix in our fork)... I just dont want a blind release Le 7 nov. 2013 22:38, Alex The Rocker alex.m3...@gmail.com a écrit : +1 for option B, and I like the idea of a 1.6.1 maintenance release with OpenJPA final in it, that's a perfect one if option B can be provided super fast (this week at least as a release candidate) Otherwise it'll amount to option C for us :( Thanks Alex On Thu, Nov 7, 2013 at 10:32 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Need to check whereas the option A is possible. I'm for B, but I would add the following: release 1.6.1 release maintenance as soon as OpenJPA gets released. Release maintenance only, no new features. Only big bugfixes and dep updates. Latest option is not acceptable for me To summarize: A = 0 B = +1 C = -1 JLouis 2013/11/7 David Blevins david.blev...@gmail.com So we need to start getting builds for Alex, Tim, Judah and crew or they won't be able to move forward with TomEE. We just have the OpenJPA issue to deal with. We have two options: A. Release with OpenJPA 2.2.2 B. Release with OpenJPA 2.3.0 pre build of our creation -- we've done this with other things before on rare occasion Of course there is a 3rd option: C. Forget those guys, they should give us more than 4 months lead time that they'll need a release. I personally don't feel good about option #3. Would hang those guys out to dry and send a very bad message to other users. We need to get that frequent release thing down. So which option would have your vote? -David On Nov 3, 2013, at 10:22 PM, Mark Struberg strub...@yahoo.de wrote: openjpa-2.2.2 uses a hardcoded asm-3.2 dependency. That pretty much sucks. From: David Blevins david.blev...@gmail.com To: dev@tomee.apache.org Sent: Monday, 4 November 2013, 3:25 Subject: Re: Time to release TomEE 1.6.0 Branched in hopes we can kick out some of the snapshot dependencies we have and get a release candidate up mid week -- or at least something people can beat on. In terms of OpenJPA specifically, what is the exact issue with using 2.2.2? -David On Oct 8, 2013, at 5:00 PM, David Blevins david.blev...@gmail.com wrote: I pinged a few people on the OpenJPA release prior to JavaOne. Mark had volunteered some personal time for doing the OpenJPA release we need. Mark, that still something you're up for doing? -David On Sep 5, 2013, at 3:52 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Cool, thanks! Will send a mail to dev@openwebbeans. JLouis 2013/9/5 Romain Manni-Bucau rmannibu...@gmail.com FYI: TCK and build are back to green so only the dep issue now (thanks David for TCK report) *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau
Re: Time to release TomEE 1.6.0
Mark: Thanks, we'll consider that. Alex On Fri, Nov 8, 2013 at 10:38 AM, Mark Struberg strub...@yahoo.de wrote: The issue with openjpa-2.3.0 is a regression which only hits you seldom. See OPENJPA-2335 I found it when I tried to use @OrderColumn. It would be easy to fix this by rolling back Pinakis changes. But there might have been a good reason for those changes. I'm on a conf today and have to deliver 2 more talks. After that I will be able to work on that stuff again and hope I get this fixed till Sunday. I suggest Romain and I fix OpenJPA and we start a release of OWB and OpenJPA immediately after that. So Alex, if you need a TomEE release, why don't you just set the version to some internal number and rolle your private intermediate release yourself? This is really not more than mvn clean source:jar deploy -DskipTests=true We should have the TomEE release final somewhen this week. David now runs a company with commercial support even, so if you need help with an internal release then I bet he can help you. This is OpenSource, but we are no free candy gift shop. We all take a lot of heart but also time and money into TomEE and other ASF projects. But not because we are bored! We really use that stuff in our own projects. We are very happy to get feedback. We are also very happy if tomee users are happy. We also understand that some users have time constraints. But we would be even happier if people don't see all the work we do as granted for free. don't take it personal, just needed to be said ;) LieGrue, strub From: Romain Manni-Bucau rmannibu...@gmail.com To: dev@tomee.apache.org Sent: Friday, 8 November 2013, 6:58 Subject: Re: Time to release TomEE 1.6.0 Ping Mark to know what is the openjpa regression. If blocking wait openjpa (or do the fix), if not B (or with the fix in our fork)... I just dont want a blind release Le 7 nov. 2013 22:38, Alex The Rocker alex.m3...@gmail.com a écrit : +1 for option B, and I like the idea of a 1.6.1 maintenance release with OpenJPA final in it, that's a perfect one if option B can be provided super fast (this week at least as a release candidate) Otherwise it'll amount to option C for us :( Thanks Alex On Thu, Nov 7, 2013 at 10:32 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Need to check whereas the option A is possible. I'm for B, but I would add the following: release 1.6.1 release maintenance as soon as OpenJPA gets released. Release maintenance only, no new features. Only big bugfixes and dep updates. Latest option is not acceptable for me To summarize: A = 0 B = +1 C = -1 JLouis 2013/11/7 David Blevins david.blev...@gmail.com So we need to start getting builds for Alex, Tim, Judah and crew or they won't be able to move forward with TomEE. We just have the OpenJPA issue to deal with. We have two options: A. Release with OpenJPA 2.2.2 B. Release with OpenJPA 2.3.0 pre build of our creation -- we've done this with other things before on rare occasion Of course there is a 3rd option: C. Forget those guys, they should give us more than 4 months lead time that they'll need a release. I personally don't feel good about option #3. Would hang those guys out to dry and send a very bad message to other users. We need to get that frequent release thing down. So which option would have your vote? -David On Nov 3, 2013, at 10:22 PM, Mark Struberg strub...@yahoo.de wrote: openjpa-2.2.2 uses a hardcoded asm-3.2 dependency. That pretty much sucks. From: David Blevins david.blev...@gmail.com To: dev@tomee.apache.org Sent: Monday, 4 November 2013, 3:25 Subject: Re: Time to release TomEE 1.6.0 Branched in hopes we can kick out some of the snapshot dependencies we have and get a release candidate up mid week -- or at least something people can beat on. In terms of OpenJPA specifically, what is the exact issue with using 2.2.2? -David On Oct 8, 2013, at 5:00 PM, David Blevins david.blev...@gmail.com wrote: I pinged a few people on the OpenJPA release prior to JavaOne. Mark had volunteered some personal time for doing the OpenJPA release we need. Mark, that still something you're up for doing? -David On Sep 5, 2013, at 3:52 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Cool, thanks! Will send a mail to dev@openwebbeans. JLouis 2013/9/5 Romain Manni-Bucau rmannibu...@gmail.com FYI: TCK and build are back to green so only the dep issue now (thanks David for TCK report
Re: Time to release TomEE 1.6.0
On Nov 8, 2013, at 1:38 AM, Mark Struberg strub...@yahoo.de wrote: The issue with openjpa-2.3.0 is a regression which only hits you seldom. See OPENJPA-2335 I found it when I tried to use @OrderColumn. It would be easy to fix this by rolling back Pinakis changes. But there might have been a good reason for those changes. I'm on a conf today and have to deliver 2 more talks. After that I will be able to work on that stuff again and hope I get this fixed till Sunday. I suggest Romain and I fix OpenJPA and we start a release of OWB and OpenJPA immediately after that. I just finished reverting OPENJPA-2335 in the 1.6.0 branch. Just need an OWB build than can put up a preview build of TomEE and get some sleep. Fine if it's not the final build. Need to get a jump on TCK and the rest of the TomEE process that really only starts once we have a build to try. -David
Re: Time to release TomEE 1.6.0
Txs Ales. Again, this was not intended as personally addressed to you. I've seen you asked great questions and give feedback and we really appreciate that! So you already started contributing in some form - and maybe it might become more in the futhre by helping us with docs, etc. txs for your understanding, LieGrue, strub From: Alex The Rocker alex.m3...@gmail.com To: dev@tomee.apache.org; Mark Struberg strub...@yahoo.de Sent: Friday, 8 November 2013, 12:12 Subject: Re: Time to release TomEE 1.6.0 Mark: Thanks, we'll consider that. Alex On Fri, Nov 8, 2013 at 10:38 AM, Mark Struberg strub...@yahoo.de wrote: The issue with openjpa-2.3.0 is a regression which only hits you seldom. See OPENJPA-2335 I found it when I tried to use @OrderColumn. It would be easy to fix this by rolling back Pinakis changes. But there might have been a good reason for those changes. I'm on a conf today and have to deliver 2 more talks. After that I will be able to work on that stuff again and hope I get this fixed till Sunday. I suggest Romain and I fix OpenJPA and we start a release of OWB and OpenJPA immediately after that. So Alex, if you need a TomEE release, why don't you just set the version to some internal number and rolle your private intermediate release yourself? This is really not more than mvn clean source:jar deploy -DskipTests=true We should have the TomEE release final somewhen this week. David now runs a company with commercial support even, so if you need help with an internal release then I bet he can help you. This is OpenSource, but we are no free candy gift shop. We all take a lot of heart but also time and money into TomEE and other ASF projects. But not because we are bored! We really use that stuff in our own projects. We are very happy to get feedback. We are also very happy if tomee users are happy. We also understand that some users have time constraints. But we would be even happier if people don't see all the work we do as granted for free. don't take it personal, just needed to be said ;) LieGrue, strub From: Romain Manni-Bucau rmannibu...@gmail.com To: dev@tomee.apache.org Sent: Friday, 8 November 2013, 6:58 Subject: Re: Time to release TomEE 1.6.0 Ping Mark to know what is the openjpa regression. If blocking wait openjpa (or do the fix), if not B (or with the fix in our fork)... I just dont want a blind release Le 7 nov. 2013 22:38, Alex The Rocker alex.m3...@gmail.com a écrit : +1 for option B, and I like the idea of a 1.6.1 maintenance release with OpenJPA final in it, that's a perfect one if option B can be provided super fast (this week at least as a release candidate) Otherwise it'll amount to option C for us :( Thanks Alex On Thu, Nov 7, 2013 at 10:32 PM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Need to check whereas the option A is possible. I'm for B, but I would add the following: release 1.6.1 release maintenance as soon as OpenJPA gets released. Release maintenance only, no new features. Only big bugfixes and dep updates. Latest option is not acceptable for me To summarize: A = 0 B = +1 C = -1 JLouis 2013/11/7 David Blevins david.blev...@gmail.com So we need to start getting builds for Alex, Tim, Judah and crew or they won't be able to move forward with TomEE. We just have the OpenJPA issue to deal with. We have two options: A. Release with OpenJPA 2.2.2 B. Release with OpenJPA 2.3.0 pre build of our creation -- we've done this with other things before on rare occasion Of course there is a 3rd option: C. Forget those guys, they should give us more than 4 months lead time that they'll need a release. I personally don't feel good about option #3. Would hang those guys out to dry and send a very bad message to other users. We need to get that frequent release thing down. So which option would have your vote? -David On Nov 3, 2013, at 10:22 PM, Mark Struberg strub...@yahoo.de wrote: openjpa-2.2.2 uses a hardcoded asm-3.2 dependency. That pretty much sucks. From: David Blevins david.blev...@gmail.com To: dev@tomee.apache.org Sent: Monday, 4 November 2013, 3:25 Subject: Re: Time to release TomEE 1.6.0 Branched in hopes we can kick out some of the snapshot dependencies we have and get a release candidate up mid week -- or at least something people can beat on. In terms of OpenJPA specifically, what is the exact issue with using 2.2.2? -David On Oct 8, 2013, at 5:00 PM, David Blevins david.blev...@gmail.com wrote: I pinged a few people on the OpenJPA release
Re: Time to release TomEE 1.6.0
Ended up having to split the OpenJPA source out to a different build due to shade plugin limitations -- you don't get the shaded version if it's being created in your same build. Our TomEE zips and tars were 5mb bigger due to having both he shaded OpenJPA and the individual jars that make the shaded OpenJPA jar. Cleaned that up and finally got it into nexus -- deploys continue to fail, so determination is required. Going to try and get some sleep. Jean-Louis staying on to get non-bloated zips up. -David On Nov 8, 2013, at 3:15 AM, David Blevins david.blev...@gmail.com wrote: On Nov 8, 2013, at 1:38 AM, Mark Struberg strub...@yahoo.de wrote: The issue with openjpa-2.3.0 is a regression which only hits you seldom. See OPENJPA-2335 I found it when I tried to use @OrderColumn. It would be easy to fix this by rolling back Pinakis changes. But there might have been a good reason for those changes. I'm on a conf today and have to deliver 2 more talks. After that I will be able to work on that stuff again and hope I get this fixed till Sunday. I suggest Romain and I fix OpenJPA and we start a release of OWB and OpenJPA immediately after that. I just finished reverting OPENJPA-2335 in the 1.6.0 branch. Just need an OWB build than can put up a preview build of TomEE and get some sleep. Fine if it's not the final build. Need to get a jump on TCK and the rest of the TomEE process that really only starts once we have a build to try. -David
Re: Time to release TomEE 1.6.0
So we need to start getting builds for Alex, Tim, Judah and crew or they won't be able to move forward with TomEE. We just have the OpenJPA issue to deal with. We have two options: A. Release with OpenJPA 2.2.2 B. Release with OpenJPA 2.3.0 pre build of our creation -- we've done this with other things before on rare occasion Of course there is a 3rd option: C. Forget those guys, they should give us more than 4 months lead time that they'll need a release. I personally don't feel good about option #3. Would hang those guys out to dry and send a very bad message to other users. We need to get that frequent release thing down. So which option would have your vote? -David On Nov 3, 2013, at 10:22 PM, Mark Struberg strub...@yahoo.de wrote: openjpa-2.2.2 uses a hardcoded asm-3.2 dependency. That pretty much sucks. From: David Blevins david.blev...@gmail.com To: dev@tomee.apache.org Sent: Monday, 4 November 2013, 3:25 Subject: Re: Time to release TomEE 1.6.0 Branched in hopes we can kick out some of the snapshot dependencies we have and get a release candidate up mid week -- or at least something people can beat on. In terms of OpenJPA specifically, what is the exact issue with using 2.2.2? -David On Oct 8, 2013, at 5:00 PM, David Blevins david.blev...@gmail.com wrote: I pinged a few people on the OpenJPA release prior to JavaOne. Mark had volunteered some personal time for doing the OpenJPA release we need. Mark, that still something you're up for doing? -David On Sep 5, 2013, at 3:52 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Cool, thanks! Will send a mail to dev@openwebbeans. JLouis 2013/9/5 Romain Manni-Bucau rmannibu...@gmail.com FYI: TCK and build are back to green so only the dep issue now (thanks David for TCK report) *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/4 Jean-Louis MONTEIRO jeano...@gmail.com I know that almost everybody is currently working in production with SNAPSHOTS (kinda releases for OpenEJB). But sometimes, it's also good to take time to product real releases. But, fully agree with you. Right now it a bit complicated regarding the community. Hopefully, that should be better in coming weeks, months cause we are seeing more and more contributors on the mailing lists. So they should join the committers' list of the project. JLouis 2013/9/4 Romain Manni-Bucau rmannibu...@gmail.com Hehe, I hope so too but *today* it seems too complicated so i prefer to be realistic. Le 4 sept. 2013 15:48, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Without moving from one side to the opposite, we can IMO do better and more frequent releases, at least with bugfixes. JLouis 2013/9/4 Romain Manni-Bucau rmannibu...@gmail.com arquillian update/fix is done for weeks, OpenJPA guys doesn't move but we can fork even if that's a bit sad, OWB is not an issue IMO (we just need to ask). However our TCKs report is broken (report, not TCKs themself ;) so we need it to be fixed before any release. About maintenance releases: I think it is clear we are not able to do so. So when somebody able to release is ready to do it, let's just release IMO. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/4 Jean-Louis MONTEIRO jeano...@gmail.com @tiklu TomEE depends on other implementations to implement Java EE 7. The work has already started with openwebbeans and bean validation. Well regarding our 1.6.0 release, I would like to have it by the end of September. Any updates on Arquillian, OpenWebBeans and OpenJPA? Are they absolutely necessary? If API changes, ok if just a bugfix, mais be we can release another maintenance release next month with new dependency updates. any comment? JLouis 2013/7/18 tiklu ganguly tiklugang...@gmail.com and when are you guys planning support for JavaEE 7? On Thu, Jul 18, 2013 at 9:25 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: PS we need arquillian 1.1.1.Final too to remove an ugly hack we have ATM, normally should be here at the end of the week *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/7/16 Romain Manni-Bucau rmannibu...@gmail.com We are still waiting for owb 1.2.1
Re: Time to release TomEE 1.6.0
Branched in hopes we can kick out some of the snapshot dependencies we have and get a release candidate up mid week -- or at least something people can beat on. In terms of OpenJPA specifically, what is the exact issue with using 2.2.2? -David On Oct 8, 2013, at 5:00 PM, David Blevins david.blev...@gmail.com wrote: I pinged a few people on the OpenJPA release prior to JavaOne. Mark had volunteered some personal time for doing the OpenJPA release we need. Mark, that still something you're up for doing? -David On Sep 5, 2013, at 3:52 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Cool, thanks! Will send a mail to dev@openwebbeans. JLouis 2013/9/5 Romain Manni-Bucau rmannibu...@gmail.com FYI: TCK and build are back to green so only the dep issue now (thanks David for TCK report) *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/4 Jean-Louis MONTEIRO jeano...@gmail.com I know that almost everybody is currently working in production with SNAPSHOTS (kinda releases for OpenEJB). But sometimes, it's also good to take time to product real releases. But, fully agree with you. Right now it a bit complicated regarding the community. Hopefully, that should be better in coming weeks, months cause we are seeing more and more contributors on the mailing lists. So they should join the committers' list of the project. JLouis 2013/9/4 Romain Manni-Bucau rmannibu...@gmail.com Hehe, I hope so too but *today* it seems too complicated so i prefer to be realistic. Le 4 sept. 2013 15:48, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Without moving from one side to the opposite, we can IMO do better and more frequent releases, at least with bugfixes. JLouis 2013/9/4 Romain Manni-Bucau rmannibu...@gmail.com arquillian update/fix is done for weeks, OpenJPA guys doesn't move but we can fork even if that's a bit sad, OWB is not an issue IMO (we just need to ask). However our TCKs report is broken (report, not TCKs themself ;) so we need it to be fixed before any release. About maintenance releases: I think it is clear we are not able to do so. So when somebody able to release is ready to do it, let's just release IMO. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/4 Jean-Louis MONTEIRO jeano...@gmail.com @tiklu TomEE depends on other implementations to implement Java EE 7. The work has already started with openwebbeans and bean validation. Well regarding our 1.6.0 release, I would like to have it by the end of September. Any updates on Arquillian, OpenWebBeans and OpenJPA? Are they absolutely necessary? If API changes, ok if just a bugfix, mais be we can release another maintenance release next month with new dependency updates. any comment? JLouis 2013/7/18 tiklu ganguly tiklugang...@gmail.com and when are you guys planning support for JavaEE 7? On Thu, Jul 18, 2013 at 9:25 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: PS we need arquillian 1.1.1.Final too to remove an ugly hack we have ATM, normally should be here at the end of the week *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/7/16 Romain Manni-Bucau rmannibu...@gmail.com We are still waiting for owb 1.2.1 and openjpa 2.3 :( Le 16 juil. 2013 15:26, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Hey guys, was wondering if we could release TomEE 1.6.0. Is there any other releases we have to wait for? Does anybody has important things in progress? It's been a very long time since latest release and it's necessary in my opinion to get it out soon now. Any thoughts? -- Jean-Louis -- Jean-Louis -- Jean-Louis -- Jean-Louis -- Jean-Louis
Re: Time to release TomEE 1.6.0
Hi David, It doesnt support asm4 + several bugfixes (on auditor, criteria api, dictionnary...) needed by several people. Le 4 nov. 2013 03:25, David Blevins david.blev...@gmail.com a écrit : Branched in hopes we can kick out some of the snapshot dependencies we have and get a release candidate up mid week -- or at least something people can beat on. In terms of OpenJPA specifically, what is the exact issue with using 2.2.2? -David On Oct 8, 2013, at 5:00 PM, David Blevins david.blev...@gmail.com wrote: I pinged a few people on the OpenJPA release prior to JavaOne. Mark had volunteered some personal time for doing the OpenJPA release we need. Mark, that still something you're up for doing? -David On Sep 5, 2013, at 3:52 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Cool, thanks! Will send a mail to dev@openwebbeans. JLouis 2013/9/5 Romain Manni-Bucau rmannibu...@gmail.com FYI: TCK and build are back to green so only the dep issue now (thanks David for TCK report) *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/4 Jean-Louis MONTEIRO jeano...@gmail.com I know that almost everybody is currently working in production with SNAPSHOTS (kinda releases for OpenEJB). But sometimes, it's also good to take time to product real releases. But, fully agree with you. Right now it a bit complicated regarding the community. Hopefully, that should be better in coming weeks, months cause we are seeing more and more contributors on the mailing lists. So they should join the committers' list of the project. JLouis 2013/9/4 Romain Manni-Bucau rmannibu...@gmail.com Hehe, I hope so too but *today* it seems too complicated so i prefer to be realistic. Le 4 sept. 2013 15:48, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Without moving from one side to the opposite, we can IMO do better and more frequent releases, at least with bugfixes. JLouis 2013/9/4 Romain Manni-Bucau rmannibu...@gmail.com arquillian update/fix is done for weeks, OpenJPA guys doesn't move but we can fork even if that's a bit sad, OWB is not an issue IMO (we just need to ask). However our TCKs report is broken (report, not TCKs themself ;) so we need it to be fixed before any release. About maintenance releases: I think it is clear we are not able to do so. So when somebody able to release is ready to do it, let's just release IMO. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/4 Jean-Louis MONTEIRO jeano...@gmail.com @tiklu TomEE depends on other implementations to implement Java EE 7. The work has already started with openwebbeans and bean validation. Well regarding our 1.6.0 release, I would like to have it by the end of September. Any updates on Arquillian, OpenWebBeans and OpenJPA? Are they absolutely necessary? If API changes, ok if just a bugfix, mais be we can release another maintenance release next month with new dependency updates. any comment? JLouis 2013/7/18 tiklu ganguly tiklugang...@gmail.com and when are you guys planning support for JavaEE 7? On Thu, Jul 18, 2013 at 9:25 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: PS we need arquillian 1.1.1.Final too to remove an ugly hack we have ATM, normally should be here at the end of the week *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/7/16 Romain Manni-Bucau rmannibu...@gmail.com We are still waiting for owb 1.2.1 and openjpa 2.3 :( Le 16 juil. 2013 15:26, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Hey guys, was wondering if we could release TomEE 1.6.0. Is there any other releases we have to wait for? Does anybody has important things in progress? It's been a very long time since latest release and it's necessary in my opinion to get it out soon now. Any thoughts? -- Jean-Louis -- Jean-Louis -- Jean-Louis -- Jean-Louis -- Jean-Louis
Re: Time to release TomEE 1.6.0
openjpa-2.2.2 uses a hardcoded asm-3.2 dependency. That pretty much sucks. From: David Blevins david.blev...@gmail.com To: dev@tomee.apache.org Sent: Monday, 4 November 2013, 3:25 Subject: Re: Time to release TomEE 1.6.0 Branched in hopes we can kick out some of the snapshot dependencies we have and get a release candidate up mid week -- or at least something people can beat on. In terms of OpenJPA specifically, what is the exact issue with using 2.2.2? -David On Oct 8, 2013, at 5:00 PM, David Blevins david.blev...@gmail.com wrote: I pinged a few people on the OpenJPA release prior to JavaOne. Mark had volunteered some personal time for doing the OpenJPA release we need. Mark, that still something you're up for doing? -David On Sep 5, 2013, at 3:52 AM, Jean-Louis MONTEIRO jeano...@gmail.com wrote: Cool, thanks! Will send a mail to dev@openwebbeans. JLouis 2013/9/5 Romain Manni-Bucau rmannibu...@gmail.com FYI: TCK and build are back to green so only the dep issue now (thanks David for TCK report) *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/4 Jean-Louis MONTEIRO jeano...@gmail.com I know that almost everybody is currently working in production with SNAPSHOTS (kinda releases for OpenEJB). But sometimes, it's also good to take time to product real releases. But, fully agree with you. Right now it a bit complicated regarding the community. Hopefully, that should be better in coming weeks, months cause we are seeing more and more contributors on the mailing lists. So they should join the committers' list of the project. JLouis 2013/9/4 Romain Manni-Bucau rmannibu...@gmail.com Hehe, I hope so too but *today* it seems too complicated so i prefer to be realistic. Le 4 sept. 2013 15:48, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Without moving from one side to the opposite, we can IMO do better and more frequent releases, at least with bugfixes. JLouis 2013/9/4 Romain Manni-Bucau rmannibu...@gmail.com arquillian update/fix is done for weeks, OpenJPA guys doesn't move but we can fork even if that's a bit sad, OWB is not an issue IMO (we just need to ask). However our TCKs report is broken (report, not TCKs themself ;) so we need it to be fixed before any release. About maintenance releases: I think it is clear we are not able to do so. So when somebody able to release is ready to do it, let's just release IMO. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/4 Jean-Louis MONTEIRO jeano...@gmail.com @tiklu TomEE depends on other implementations to implement Java EE 7. The work has already started with openwebbeans and bean validation. Well regarding our 1.6.0 release, I would like to have it by the end of September. Any updates on Arquillian, OpenWebBeans and OpenJPA? Are they absolutely necessary? If API changes, ok if just a bugfix, mais be we can release another maintenance release next month with new dependency updates. any comment? JLouis 2013/7/18 tiklu ganguly tiklugang...@gmail.com and when are you guys planning support for JavaEE 7? On Thu, Jul 18, 2013 at 9:25 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: PS we need arquillian 1.1.1.Final too to remove an ugly hack we have ATM, normally should be here at the end of the week *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/7/16 Romain Manni-Bucau rmannibu...@gmail.com We are still waiting for owb 1.2.1 and openjpa 2.3 :( Le 16 juil. 2013 15:26, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Hey guys, was wondering if we could release TomEE 1.6.0. Is there any other releases we have to wait for? Does anybody has important things in progress? It's been a very long time since latest release and it's necessary in my opinion to get it out soon now. Any thoughts? -- Jean-Louis -- Jean-Louis -- Jean-Louis -- Jean-Louis -- Jean-Louis
Re: Time to release TomEE 1.6.0
FYI: TCK and build are back to green so only the dep issue now (thanks David for TCK report) *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/4 Jean-Louis MONTEIRO jeano...@gmail.com I know that almost everybody is currently working in production with SNAPSHOTS (kinda releases for OpenEJB). But sometimes, it's also good to take time to product real releases. But, fully agree with you. Right now it a bit complicated regarding the community. Hopefully, that should be better in coming weeks, months cause we are seeing more and more contributors on the mailing lists. So they should join the committers' list of the project. JLouis 2013/9/4 Romain Manni-Bucau rmannibu...@gmail.com Hehe, I hope so too but *today* it seems too complicated so i prefer to be realistic. Le 4 sept. 2013 15:48, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Without moving from one side to the opposite, we can IMO do better and more frequent releases, at least with bugfixes. JLouis 2013/9/4 Romain Manni-Bucau rmannibu...@gmail.com arquillian update/fix is done for weeks, OpenJPA guys doesn't move but we can fork even if that's a bit sad, OWB is not an issue IMO (we just need to ask). However our TCKs report is broken (report, not TCKs themself ;) so we need it to be fixed before any release. About maintenance releases: I think it is clear we are not able to do so. So when somebody able to release is ready to do it, let's just release IMO. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/4 Jean-Louis MONTEIRO jeano...@gmail.com @tiklu TomEE depends on other implementations to implement Java EE 7. The work has already started with openwebbeans and bean validation. Well regarding our 1.6.0 release, I would like to have it by the end of September. Any updates on Arquillian, OpenWebBeans and OpenJPA? Are they absolutely necessary? If API changes, ok if just a bugfix, mais be we can release another maintenance release next month with new dependency updates. any comment? JLouis 2013/7/18 tiklu ganguly tiklugang...@gmail.com and when are you guys planning support for JavaEE 7? On Thu, Jul 18, 2013 at 9:25 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: PS we need arquillian 1.1.1.Final too to remove an ugly hack we have ATM, normally should be here at the end of the week *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/7/16 Romain Manni-Bucau rmannibu...@gmail.com We are still waiting for owb 1.2.1 and openjpa 2.3 :( Le 16 juil. 2013 15:26, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Hey guys, was wondering if we could release TomEE 1.6.0. Is there any other releases we have to wait for? Does anybody has important things in progress? It's been a very long time since latest release and it's necessary in my opinion to get it out soon now. Any thoughts? -- Jean-Louis -- Jean-Louis -- Jean-Louis -- Jean-Louis
Re: Time to release TomEE 1.6.0
arquillian update/fix is done for weeks, OpenJPA guys doesn't move but we can fork even if that's a bit sad, OWB is not an issue IMO (we just need to ask). However our TCKs report is broken (report, not TCKs themself ;) so we need it to be fixed before any release. About maintenance releases: I think it is clear we are not able to do so. So when somebody able to release is ready to do it, let's just release IMO. *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/4 Jean-Louis MONTEIRO jeano...@gmail.com @tiklu TomEE depends on other implementations to implement Java EE 7. The work has already started with openwebbeans and bean validation. Well regarding our 1.6.0 release, I would like to have it by the end of September. Any updates on Arquillian, OpenWebBeans and OpenJPA? Are they absolutely necessary? If API changes, ok if just a bugfix, mais be we can release another maintenance release next month with new dependency updates. any comment? JLouis 2013/7/18 tiklu ganguly tiklugang...@gmail.com and when are you guys planning support for JavaEE 7? On Thu, Jul 18, 2013 at 9:25 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: PS we need arquillian 1.1.1.Final too to remove an ugly hack we have ATM, normally should be here at the end of the week *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/7/16 Romain Manni-Bucau rmannibu...@gmail.com We are still waiting for owb 1.2.1 and openjpa 2.3 :( Le 16 juil. 2013 15:26, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Hey guys, was wondering if we could release TomEE 1.6.0. Is there any other releases we have to wait for? Does anybody has important things in progress? It's been a very long time since latest release and it's necessary in my opinion to get it out soon now. Any thoughts? -- Jean-Louis -- Jean-Louis
Re: Time to release TomEE 1.6.0
and when are you guys planning support for JavaEE 7? On Thu, Jul 18, 2013 at 9:25 AM, Romain Manni-Bucau rmannibu...@gmail.comwrote: PS we need arquillian 1.1.1.Final too to remove an ugly hack we have ATM, normally should be here at the end of the week *Romain Manni-Bucau* *Twitter: @rmannibucau https://twitter.com/rmannibucau* *Blog: **http://rmannibucau.wordpress.com/* http://rmannibucau.wordpress.com/ *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/7/16 Romain Manni-Bucau rmannibu...@gmail.com We are still waiting for owb 1.2.1 and openjpa 2.3 :( Le 16 juil. 2013 15:26, Jean-Louis MONTEIRO jeano...@gmail.com a écrit : Hey guys, was wondering if we could release TomEE 1.6.0. Is there any other releases we have to wait for? Does anybody has important things in progress? It's been a very long time since latest release and it's necessary in my opinion to get it out soon now. Any thoughts? -- Jean-Louis
