openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Struberg <strub...@yahoo.de>
Subject Re: [jira] [Resolved] (OPENJPA-2087) Remove or limit the use of the ConcreteClassGenerator
Date Wed, 04 Jan 2012 09:47:32 GMT
nope, at least not on my mac.
And I think it was the same on linux.


But this will not be our last problem with compiling on differnt jdks.

Another issue is the damn getParentLogger() some dumbasses added to the jdbc Driver and DataSource
in java7 [1]. 
I really don't know who did this *piep*, but the result is that you cannot compile a Driver
or DataSource impl in java7, because it forces you to implement getParentLogger().
Just go on just add this method, you will say. But snack, that will break compiling in java5
and 6 because those morons added an Exception to this new method which doesn't exist in java5.
God, please let it rain brain for them ^^

Conclusion: sooner or later we need to drop java5 support at all :/

LieGrue,
strub


[1] http://docs.oracle.com/javase/7/docs/api/java/sql/Driver.html#getParentLogger%28%29


----- Original Message -----
> From: Craig L Russell <craig.russell@oracle.com>
> To: dev@openjpa.apache.org
> Cc: 
> Sent: Tuesday, January 3, 2012 10:51 PM
> Subject: Re: [jira] [Resolved] (OPENJPA-2087) Remove or limit the use of the ConcreteClassGenerator
> 
> Just a thought: does this get caught when compiling with source=1.5?
> 
> Craig
> 
> On Jan 3, 2012, at 1:28 PM, Mark Struberg wrote:
> 
>>  We really need to take care that we don't pickup some java6 only stuff 
> like String.isEmpty() in our code. Sadly this doesn't get detected when 
> compiling with target=1.5 :(
>> 
>> 
>>  Thus we need run the TCK with java5 runtime to verify that all things work.
>> 
>>  LieGrue,
>>  strub
>> 
>> 
>> 
>>  ----- Original Message -----
>>>  From: Kevin Sutter (Resolved) (JIRA) <jira@apache.org>
>>>  To: dev@openjpa.apache.org
>>>  Cc:
>>>  Sent: Tuesday, January 3, 2012 9:14 PM
>>>  Subject: [jira] [Resolved] (OPENJPA-2087) Remove or limit the use of 
> the ConcreteClassGenerator
>>> 
>>> 
>>>       [
>>> 
> https://issues.apache.org/jira/browse/OPENJPA-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>>>  ]
>>> 
>>>  Kevin Sutter resolved OPENJPA-2087.
>>>  -----------------------------------
>>> 
>>>         Resolution: Fixed
>>>      Fix Version/s: 2.2.0
>>> 
>>>>  Remove or limit the use of the ConcreteClassGenerator
>>>>  -----------------------------------------------------
>>>> 
>>>>                   Key: OPENJPA-2087
>>>>                   URL: 
> https://issues.apache.org/jira/browse/OPENJPA-2087
>>>>               Project: OpenJPA
>>>>            Issue Type: Improvement
>>>>            Components: build / infrastructure
>>>>              Reporter: Jacob Nowosatka
>>>>              Assignee: Kevin Sutter
>>>>              Priority: Minor
>>>>               Fix For: 2.2.0
>>>> 
>>>>           Attachments: OPENJPA-2087-1.patch, OPENJPA-2087-2.patch
>>>> 
>>>> 
>>>>  Now that we have to only support Java 6 in OpenJPA 2.x, there is 
> discussion
>>>  about revisiting the issue of removing or limiting the use of the
>>>  ConcreteClassGenerator. This was originally discussed in OpenJPA-1520 
> [1].  This
>>>  would help cleanup some of the code and would hopefully result in some
>>>  performance gains, despite that it didn't seem to help with earlier
>>>  primitive tests.
>>>>  [1] https://issues.apache.org/jira/browse/OPENJPA-1520
>>> 
>>>  --
>>>  This message is automatically generated by JIRA.
>>>  If you think it was sent incorrectly, please contact your JIRA 
> administrators:
>>> 
> https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
>>>  For more information on JIRA, see: 
> http://www.atlassian.com/software/jira
>>> 
> 
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
> 

Mime
View raw message