[ http://issues.apache.org/jira/browse/OPENJPA-76?page=all ]
Patrick Linskey resolved OPENJPA-76.
Resolution: Fixed
I applied the patch with revision 472018. I changed it slightly to make it use
resources instead of files.
add-was-interfaces ant
any suggestions for either getting the classes into the
classpath or moving the exception to runtime, so that there aren't
build-time dependency issues resulting in different jars from the same
sources?
Thanks,
-Patrick
Partial stack trace:
[INFO] [antrun:run {execution: add-was-interfaces
getting the classes into the
classpath or moving the exception to runtime, so that there aren't
build-time dependency issues resulting in different jars from the same
sources?
Thanks,
-Patrick
Partial stack trace:
[INFO] [antrun:run {execution: add-was-interfaces}]
[INFO] Executing tasks
this
by email and then delete it.
-Original Message-
From: Michael Dick [mailto:[EMAIL PROTECTED]
Sent: Monday, November 06, 2006 7:14 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: add-was-interfaces
Hi Patrick,
I just ran svn update and mvn clean package and I didn't get
add-was-interfaces ant task throws exception on a non-clean build.
-
Key: OPENJPA-76
URL: http://issues.apache.org/jira/browse/OPENJPA-76
Project: OpenJPA
Issue Type: Bug
immediately return this
by email and then delete it.
-Original Message-
From: Michael Dick [mailto:[EMAIL PROTECTED]
Sent: Monday, November 06, 2006 7:14 PM
To: open-jpa-dev@incubator.apache.org
Subject: Re: add-was-interfaces
Hi Patrick,
I just ran svn update and mvn clean package and I
needed to
link against various Oracle-specific classes, but between judicious reflection
and Oracle's increased standards compliance over the years, we've been able to
avoid that for now. But I'm sure that similar situations will crop up in the
future.
add-was-interfaces ant task throws
