Forgot to address this part...
5.1 will include the ability to define lazy attribute fetch groups, the
development of which requires a lot of changes to the contracts called from
bytecode enhancement. So rather than retrofit these changes back into the
legacy enhancement code, I chose to simply
Hmm, looks like I might have been mistaken about the "external Hibernate
Maven plugin". The only one I can find (cannot remember if this is the one
I was thinking of) just does schema export.
On Fri, Nov 13, 2015 at 8:11 AM Steve Ebersole wrote:
> For runtime enhancement there is no change, we
For runtime enhancement there is no change, we manage it internally. For
build-time, legacy enhancement only offered an Ant task (there is a Maven
plugin developed by another group; I will reach out to them about this). At
the moment those folks would need to point to a new Ant task. We could
Hey,
How would migration for a user look like?
Do they need to configure a different Ant/Gradle/Maven task? Would 5.1
(assuming the old enhancer has been removed) be able to work with
entities enhanced by the old one, or would a re-build of the app be
required? Would they see a deprecation at all
+1
On 12 November 2015 at 16:39, Steve Ebersole wrote:
> https://hibernate.atlassian.net/browse/HHH-10280
> https://hibernate.atlassian.net/browse/HHH-10281
>
> On Wed, Nov 11, 2015 at 12:15 PM andrea boriero wrote:
>
>> no objections
>>
>> On 11 November 2015 at 17:55, Steve Ebersole wrote:
>>
https://hibernate.atlassian.net/browse/HHH-10280
https://hibernate.atlassian.net/browse/HHH-10281
On Wed, Nov 11, 2015 at 12:15 PM andrea boriero wrote:
> no objections
>
> On 11 November 2015 at 17:55, Steve Ebersole wrote:
>
>> I'd like to more formally deprecate the legacy bytecode enhanceme
no objections
On 11 November 2015 at 17:55, Steve Ebersole wrote:
> I'd like to more formally deprecate the legacy bytecode enhancement
> starting in 5.0.4 and remove it in 5.1.
>
> The new code is superior and already feature compatible back to 5.0 Final.
>
> Any objections?
> _
There is a time and place for decaf coffee. (Never and in the trash)
http://joel.megapr0ject.ru/daisy-amanda
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
On Wed 22 Aug 2012 03:15:14 AM CDT, Hardy Ferentschik wrote:
>
> On 22 Jan 2012, at 2:11 AM, Steve Ebersole wrote:
>
>> Also, I wonder if we ought to rename MetadataSources to remove the
>> ambiguity, maybe MetadataOrigins or MetadataSourcesOrigins?
>
> Not so fond of this. Then you would have to a
On 22 Jan 2012, at 2:11 AM, Steve Ebersole wrote:
> Also, I wonder if we ought to rename MetadataSources to remove the
> ambiguity, maybe MetadataOrigins or MetadataSourcesOrigins?
Not so fond of this. Then you would have to almost rename MetadataSource as
well.
Even though I also get sometime
Also, I think how you were expecting beforeMetadataProcessing to happen
can't really happen, but I suspect it is the more direct way to port envers.
I *think* what you were thinking is to have envers pass along its extra
EntitySource/EntityHierarchy stuff. You cannot just simply "add the
custo
Yes, thats what you said in the javadocs ;)
What I mean is that we have a use case for one of those. But not the
other. So why develop something that we do not have a use case for?
On Mon 20 Aug 2012 11:23:14 PM CDT, Strong Liu wrote:
> reuse the IntegratorService / ServiceLoader ?
>
> On Aug
reuse the IntegratorService / ServiceLoader ?
On Aug 21, 2012, at 2:14 AM, Steve Ebersole wrote:
> Also, I have been thinking that there really ought to be different types of
> "integrators". Not sure what we gain by forcing
> MetadataContributingIntegrator, ServiceContributingIntegrator,
>
Also, I have been thinking that there really ought to be different
types of "integrators". Not sure what we gain by forcing
MetadataContributingIntegrator, ServiceContributingIntegrator,
TypeContributingIntegrator, etc to extend Integrator
On Sat 18 Aug 2012 05:50:29 PM CDT, Steve Ebersole wr
how are you
http://Synergyservice.co.id/httpbestworkathome19273347.php?ahyprof=13
Mon, 16 Jan 2012 23:47:40
_
"You going to make one--you and Gus?I guess we cant afford it, Bill replied
quickly." (c) Coralee vivŠ½ficas
_
15 matches
Mail list logo
