Le 15 sept. 2016 21:17, "Mark Struberg" a
écrit :
>
> I'd rather ship 3.0.x now and keep working on the ASM move in the branch.
>
> And then enable it either pluggable or move the default to ASM for 3.1.x.
> It's really much more work than you think...
>
Well it will
I'd rather ship 3.0.x now and keep working on the ASM move in the branch.
And then enable it either pluggable or move the default to ASM for 3.1.x.
It's really much more work than you think...
LieGrue,
strub
> On Thursday, 15 September 2016, 21:01, Romain Manni-Bucau
>
Being said i cant help much ATM (:'() not sure i can judge but making it
part of 3.0 would be important IMO and qane for the future. Otherwise what
about doing some 2.5 with stored proc and std ddl for instance?
Le 15 sept. 2016 20:47, "Mark Struberg" a
écrit :
> Of
Welcome Francesco. Good to have you on board.
Craig
> On Sep 15, 2016, at 5:10 AM, Mark Struberg wrote:
>
> Good evening!
>
> Please welcome Francesco Chicchiriccò as new Apache OpenJPA PMC member!
>
> Francesco, txs for helping to push OpenJPA forward!
>
> best
Of course it would be better to have the bytecode stuff pluggable and move to
ASM for default.
The problem is that there are quite a few classes which are heavily bound to
Serp by using the BCClass interface as parameter type. E.g. AuxilaryEnhancer.
The generated bytecode is also very complex
Since the jvm uses asm - shaded - i dee this convergence as only being
positive for our ecosystem if reachable.
Le 15 sept. 2016 20:34, "Mark Struberg" a
écrit :
> Yes, most likely it could be seen as regression.
>
> The problem was that it was not easy to spot as
Yes, most likely it could be seen as regression.
The problem was that it was not easy to spot as Serp was blowing up wildly.
Serp has quite a few empty catch(Exception) blocks :(
In conjunction with the heavy use of magic indices + bit flags I simply only
saw random side effects until I
This issue hits most of projects including a plain tomcat so guess j9
should avoid this regression (yes it is).
Le 15 sept. 2016 16:14, "Francesco Chicchiriccò" a
écrit :
> On 15/09/2016 15:49, Mark Struberg wrote:
>
>> Hi folks!
>>
>> I did invest some time to get OpenJPA
[
https://issues.apache.org/jira/browse/OPENJPA-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò closed OPENJPA-2628.
---
Resolution: Fixed
Trying out my fresh PMC privileges by cleaning up the
[
https://issues.apache.org/jira/browse/OPENJPA-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg updated OPENJPA-2663:
---
Fix Version/s: (was: 3)
3.0.0
> cleanup ConcreteClassGenerator and
On 15/09/2016 15:49, Mark Struberg wrote:
Hi folks!
I did invest some time to get OpenJPA running on Java9.
We did hit some issues, mainly with the stricter behaviour of getResources with
Jigsaw.
In our enhancement layer we pretty often load just the byte[] of Classes to
avoid triggering the
Hi folks!
I did invest some time to get OpenJPA running on Java9.
We did hit some issues, mainly with the stricter behaviour of getResources with
Jigsaw.
In our enhancement layer we pretty often load just the byte[] of Classes to
avoid triggering the actual Classloading. This is mostly done by
[
https://issues.apache.org/jira/browse/OPENJPA-2662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15493144#comment-15493144
]
ASF subversion and git services commented on OPENJPA-2662:
--
Commit 1760922 from
Good evening!
Please welcome Francesco Chicchiriccò as new Apache OpenJPA PMC member!
Francesco, txs for helping to push OpenJPA forward!
best regards,
the OpenJPA team
14 matches
Mail list logo