Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates
 209.85.200.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=ZmPTh4qKsy/75nZPP5blzBCODEnEaqOgiCQv0wl4TcwTx7dKkWI9jy0rb4V06HzbAY
         Pxdi2OlzeaUjlK4mpQbve2+smM3u9+Y3hYx7yG1i7jYlVQeymbUsmwydkZwLBJS83W5J
         UHTlQowi9ss9zhh4IS4TsUmjSWqWRDUrOqk40=
MIME-Version: 1.0
In-Reply-To: <7A1B4CB6-3B35-4D48-BDE6-6DF4F3F18E5F@gmail.com>
References: <498C3EBF.4080408@apache.org>
	 <7A1B4CB6-3B35-4D48-BDE6-6DF4F3F18E5F@gmail.com>
Date: Fri, 6 Feb 2009 09:55:17 -0600
Message-ID: <89c0c52c0902060755g25c435d2p5c39011d4170484f@mail.gmail.com>
Subject: Re: Plans for a OpenJPA 1.0.4 release?
From: Kevin Sutter <kwsutter@gmail.com>
To: dev@openjpa.apache.org
Content-Type: multipart/alternative; boundary=000e0cd32af01dd8450462420c0f

--000e0cd32af01dd8450462420c0f
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

On Fri, Feb 6, 2009 at 8:32 AM, Kevan Miller <kevan.miller@gmail.com> wrote:

>
> Personally, I'd prefer to see the issue with OpenJPA 1.2.1-SNAPSHOT
> resolved. Anybody making any progress on identifying the root cause of the
> issue?


I'm not aware of any open issues related to the TCK.  The last issue that
was raised was with the EJB3 TCK with OpenJPA, which used OpenJPA, of
course.  We responded with a JIRA Issue that supposedly resolved that
problem.  I thought it was openjpa-872 (
https://issues.apache.org/jira/browse/OPENJPA-872), but I may be mistaken.

If there are any other open issues, I am not aware of them.

Thanks,
Kevin


>
> --kevan
>

--000e0cd32af01dd8450462420c0f--