oh, then all is well! sorry for the noise ;)
LieGrue, strub ----- Original Message ----- > From: Kevin Sutter <kwsut...@gmail.com> > To: dev@openjpa.apache.org > Cc: > Sent: Wednesday, January 4, 2012 3:13 PM > Subject: Re: [jira] [Resolved] (OPENJPA-2087) Remove or limit the use of the > ConcreteClassGenerator > > Hi guys, > I'm confused by this conversation. OpenJPA has been only supporting Java 6 > since the development of OpenJPA 2.1. The source and target levels for 1.6 > have seen set since revision 1022964 (10/15/2010). > > The changes that have recently been introduced have allowed OpenJPA to be > built by Java 7, but that is not a requirement at this point. OpenJPA can > continue to be built and execute in either a Java 6 or Java 7 environment. > The use of Java 5 has not been part of the story since OpenJPA 2.1. > > Kevin > > On Tue, Jan 3, 2012 at 3:51 PM, Craig L Russell > <craig.russ...@oracle.com>wrote: > >> 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) <j...@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<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<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<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<https://issues.apache.org/jira/secure/ContactAdministrators%21default.jspa> >>>> For more information on JIRA, see: http://www.atlassian.com/** >>>> software/jira <http://www.atlassian.com/software/jira> >>>> >>>> >> Craig L Russell >> Architect, Oracle >> http://db.apache.org/jdo >> 408 276-5638 mailto:Craig.Russell@oracle.**com > <craig.russ...@oracle.com> >> P.S. A good JDO? O, Gasp! >> >> >
