No, I didn't. Must have been a glitch in how JIRA Client merged the changes to the issue made while I was offline.
-Patrick -- Patrick Linskey BEA Systems, Inc. _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 08, 2007 6:27 PM > To: open-jpa-dev@incubator.apache.org > Subject: Re: [jira] Resolved: (OPENJPA-71) Caching primitive > array types consumes excessive memory > > Hi Patrick, > > The message below says that when you resolved OPENJPA-71, you > changed > the fix version from 0.9.7 to none. Now there is no fix version. > > Was that your intent? > > Craig > > On Mar 8, 2007, at 1:35 AM, Patrick Linskey (JIRA) wrote: > > > > > [ https://issues.apache.org/jira/browse/OPENJPA-71? > > page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > > > > Patrick Linskey resolved OPENJPA-71. > > ------------------------------------ > > > > Resolution: Fixed > > Fix Version/s: (was: 0.9.7) > > Craig Russell > Architect, Sun Java Enterprise System http://java.sun.com/products/jdo > 408 276-5638 mailto:[EMAIL PROTECTED] > P.S. A good JDO? O, Gasp! > >
