You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Hildeberto Mendonça <hi...@yougi.org> on 2013/11/24 10:26:04 UTC
openjpa-2.3.0-nonfinal-1540826.jar in TomEE 1.6.0
Hello,
Just wondering why TomEE 1.6.0 distribution includes a non final library such as openjpa-2.3.0-nonfinal-1540826.jar ? I’m having persistence problems now that were not happening in 1.5.2. I will develop those problems in another thread, but I would like to know whether there are some versioning rules. Por example, “don’t use versions that finishes with ‘0’ in production” or something like that.
Regards,
Hildeberto
Re: openjpa-2.3.0-nonfinal-1540826.jar in TomEE 1.6.0
Posted by Hildeberto Mendonça <hi...@yougi.org>.
I understand you guys are running fast to make TomEE the best Java EE server. But, maybe some time in the future, all JavaEE implementations could be coordinated and released simultaneously in order to make TomEE rock solid.
Thanks for the explanation!
On 24 Nov 2013, at 17:58, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Hi
>
> no, in openjpa.
>
> basically if we wait all dependencies it can delay our release from
> 1month (in the best case) so sometimes we have to do that but we take
> the exact openjpa code (typically in this case 2.3.0 which should pass
> in few days).
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
>
> 2013/11/24 Hildeberto Mendonça <hi...@yougi.org>:
>> Is it really necessary to fork it for tomee? Does it mean that if I find a bug in OpenJPA while using TomEE I have to report the bug in TomEE’s Jira instead of OpenJPA’s Jira?
>>
>> On 24 Nov 2013, at 11:06, Romain Manni-Bucau <rm...@gmail.com> wrote:
>>
>>> You are certified is you pass the certification test. These binaries did.
>>> Consider nonfinal as a fork for tomee. We could have named it 2.3.0-tomee.
>>> Le 24 nov. 2013 11:01, "Hildeberto Mendonça" <hi...@yougi.org> a
>>> écrit :
>>>
>>>> Hi Romain,
>>>>
>>>> It is TomEE+ (
>>>> http://www.apache.org/dyn/closer.cgi/tomee/tomee-1.6.0/apache-tomee-1.6.0-plus.zip).
>>>> Sorry for not being specific. What makes a tck certified library be
>>>> released as nonfinal ?
>>>>
>>>> On 24 Nov 2013, at 10:49, Romain Manni-Bucau <rm...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> Was it or no tomee release. Btw this passes tcks.
>>>>> Le 24 nov. 2013 10:26, "Hildeberto Mendonça" <hi...@yougi.org> a
>>>>> écrit :
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Just wondering why TomEE 1.6.0 distribution includes a non final library
>>>>>> such as openjpa-2.3.0-nonfinal-1540826.jar ? I’m having persistence
>>>>>> problems now that were not happening in 1.5.2. I will develop those
>>>>>> problems in another thread, but I would like to know whether there are
>>>> some
>>>>>> versioning rules. Por example, “don’t use versions that finishes with
>>>> ‘0’
>>>>>> in production” or something like that.
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Hildeberto
>>>>
>>>>
>>
Re: openjpa-2.3.0-nonfinal-1540826.jar in TomEE 1.6.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
no, in openjpa.
basically if we wait all dependencies it can delay our release from
1month (in the best case) so sometimes we have to do that but we take
the exact openjpa code (typically in this case 2.3.0 which should pass
in few days).
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau
2013/11/24 Hildeberto Mendonça <hi...@yougi.org>:
> Is it really necessary to fork it for tomee? Does it mean that if I find a bug in OpenJPA while using TomEE I have to report the bug in TomEE’s Jira instead of OpenJPA’s Jira?
>
> On 24 Nov 2013, at 11:06, Romain Manni-Bucau <rm...@gmail.com> wrote:
>
>> You are certified is you pass the certification test. These binaries did.
>> Consider nonfinal as a fork for tomee. We could have named it 2.3.0-tomee.
>> Le 24 nov. 2013 11:01, "Hildeberto Mendonça" <hi...@yougi.org> a
>> écrit :
>>
>>> Hi Romain,
>>>
>>> It is TomEE+ (
>>> http://www.apache.org/dyn/closer.cgi/tomee/tomee-1.6.0/apache-tomee-1.6.0-plus.zip).
>>> Sorry for not being specific. What makes a tck certified library be
>>> released as nonfinal ?
>>>
>>> On 24 Nov 2013, at 10:49, Romain Manni-Bucau <rm...@gmail.com>
>>> wrote:
>>>
>>>> Hi
>>>>
>>>> Was it or no tomee release. Btw this passes tcks.
>>>> Le 24 nov. 2013 10:26, "Hildeberto Mendonça" <hi...@yougi.org> a
>>>> écrit :
>>>>
>>>>> Hello,
>>>>>
>>>>> Just wondering why TomEE 1.6.0 distribution includes a non final library
>>>>> such as openjpa-2.3.0-nonfinal-1540826.jar ? I’m having persistence
>>>>> problems now that were not happening in 1.5.2. I will develop those
>>>>> problems in another thread, but I would like to know whether there are
>>> some
>>>>> versioning rules. Por example, “don’t use versions that finishes with
>>> ‘0’
>>>>> in production” or something like that.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Hildeberto
>>>
>>>
>
Re: openjpa-2.3.0-nonfinal-1540826.jar in TomEE 1.6.0
Posted by Hildeberto Mendonça <hi...@yougi.org>.
Is it really necessary to fork it for tomee? Does it mean that if I find a bug in OpenJPA while using TomEE I have to report the bug in TomEE’s Jira instead of OpenJPA’s Jira?
On 24 Nov 2013, at 11:06, Romain Manni-Bucau <rm...@gmail.com> wrote:
> You are certified is you pass the certification test. These binaries did.
> Consider nonfinal as a fork for tomee. We could have named it 2.3.0-tomee.
> Le 24 nov. 2013 11:01, "Hildeberto Mendonça" <hi...@yougi.org> a
> écrit :
>
>> Hi Romain,
>>
>> It is TomEE+ (
>> http://www.apache.org/dyn/closer.cgi/tomee/tomee-1.6.0/apache-tomee-1.6.0-plus.zip).
>> Sorry for not being specific. What makes a tck certified library be
>> released as nonfinal ?
>>
>> On 24 Nov 2013, at 10:49, Romain Manni-Bucau <rm...@gmail.com>
>> wrote:
>>
>>> Hi
>>>
>>> Was it or no tomee release. Btw this passes tcks.
>>> Le 24 nov. 2013 10:26, "Hildeberto Mendonça" <hi...@yougi.org> a
>>> écrit :
>>>
>>>> Hello,
>>>>
>>>> Just wondering why TomEE 1.6.0 distribution includes a non final library
>>>> such as openjpa-2.3.0-nonfinal-1540826.jar ? I’m having persistence
>>>> problems now that were not happening in 1.5.2. I will develop those
>>>> problems in another thread, but I would like to know whether there are
>> some
>>>> versioning rules. Por example, “don’t use versions that finishes with
>> ‘0’
>>>> in production” or something like that.
>>>>
>>>> Regards,
>>>>
>>>> Hildeberto
>>
>>
Re: openjpa-2.3.0-nonfinal-1540826.jar in TomEE 1.6.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
You are certified is you pass the certification test. These binaries did.
Consider nonfinal as a fork for tomee. We could have named it 2.3.0-tomee.
Le 24 nov. 2013 11:01, "Hildeberto Mendonça" <hi...@yougi.org> a
écrit :
> Hi Romain,
>
> It is TomEE+ (
> http://www.apache.org/dyn/closer.cgi/tomee/tomee-1.6.0/apache-tomee-1.6.0-plus.zip).
> Sorry for not being specific. What makes a tck certified library be
> released as nonfinal ?
>
> On 24 Nov 2013, at 10:49, Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
> > Hi
> >
> > Was it or no tomee release. Btw this passes tcks.
> > Le 24 nov. 2013 10:26, "Hildeberto Mendonça" <hi...@yougi.org> a
> > écrit :
> >
> >> Hello,
> >>
> >> Just wondering why TomEE 1.6.0 distribution includes a non final library
> >> such as openjpa-2.3.0-nonfinal-1540826.jar ? I’m having persistence
> >> problems now that were not happening in 1.5.2. I will develop those
> >> problems in another thread, but I would like to know whether there are
> some
> >> versioning rules. Por example, “don’t use versions that finishes with
> ‘0’
> >> in production” or something like that.
> >>
> >> Regards,
> >>
> >> Hildeberto
>
>
Re: openjpa-2.3.0-nonfinal-1540826.jar in TomEE 1.6.0
Posted by Hildeberto Mendonça <hi...@yougi.org>.
Hi Romain,
It is TomEE+ (http://www.apache.org/dyn/closer.cgi/tomee/tomee-1.6.0/apache-tomee-1.6.0-plus.zip). Sorry for not being specific. What makes a tck certified library be released as nonfinal ?
On 24 Nov 2013, at 10:49, Romain Manni-Bucau <rm...@gmail.com> wrote:
> Hi
>
> Was it or no tomee release. Btw this passes tcks.
> Le 24 nov. 2013 10:26, "Hildeberto Mendonça" <hi...@yougi.org> a
> écrit :
>
>> Hello,
>>
>> Just wondering why TomEE 1.6.0 distribution includes a non final library
>> such as openjpa-2.3.0-nonfinal-1540826.jar ? I’m having persistence
>> problems now that were not happening in 1.5.2. I will develop those
>> problems in another thread, but I would like to know whether there are some
>> versioning rules. Por example, “don’t use versions that finishes with ‘0’
>> in production” or something like that.
>>
>> Regards,
>>
>> Hildeberto
Re: openjpa-2.3.0-nonfinal-1540826.jar in TomEE 1.6.0
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi
Was it or no tomee release. Btw this passes tcks.
Le 24 nov. 2013 10:26, "Hildeberto Mendonça" <hi...@yougi.org> a
écrit :
> Hello,
>
> Just wondering why TomEE 1.6.0 distribution includes a non final library
> such as openjpa-2.3.0-nonfinal-1540826.jar ? I’m having persistence
> problems now that were not happening in 1.5.2. I will develop those
> problems in another thread, but I would like to know whether there are some
> versioning rules. Por example, “don’t use versions that finishes with ‘0’
> in production” or something like that.
>
> Regards,
>
> Hildeberto