A openjpa/openjpa-persistence/src/main/resources/org/apache/openjpa/persistence/validation
A openjpa/openjpa-persistence/src/main/resources/org/apache/openjpa/persistence/validation/localizer.properties
A openjpa/openjpa-persistence/pom.xml
U openjpa

#ulimit -n 10000
#nohup mvn test -Dtest=TestPersistence -Dopenjpa.loglevel=TRACE -DfailIfNoTests=false > /tmp/openjpa-test.log

Attaching the log file. Previously mentioned bug hasdiapered. John

2010/5/17 Rick Curtis <curtisr7@gmail.com>

com.sun.corba.se.spi.legacy.connection.GetEndPointInfoAgainException was in
extra import which I just removed. If you checked out via svn, running svn
update should get the change.


On Mon, May 17, 2010 at 11:36 AM, Web developer <webautomator2@gmail.com>wrote:

> I checked out the latest build from general svn trunk. Here what I got:
> /root/openjpa/openjpa-persistence-jdbc/src/test/java/org/apache/openjpa/persistence/nullity/TestBasicFieldNullity.java:[29,45]
> com.sun.corba.se.spi.legacy.connection.GetEndPointInfoAgainException is Sun
> proprietary API and may be removed in a future release
> I am curious about the
> com.sun.corba.se.spi.legacy.connection.GetEndPointInfoAgainException class
> related warning. And tests seam to lack necessary configuration details due
> to so much warnings. And the logging problem still exist. Now I will check
> a
> concrete revision that I was said to try. John