Skip to main content
diff options
Diffstat (limited to 'examples/org.eclipse.emf.teneo.eclipselink.examples.derby/ReadMe.txt')
1 files changed, 0 insertions, 28 deletions
diff --git a/examples/org.eclipse.emf.teneo.eclipselink.examples.derby/ReadMe.txt b/examples/org.eclipse.emf.teneo.eclipselink.examples.derby/ReadMe.txt
deleted file mode 100644
index f9ab4f711..000000000
--- a/examples/org.eclipse.emf.teneo.eclipselink.examples.derby/ReadMe.txt
+++ /dev/null
@@ -1,28 +0,0 @@
-This bundle uses an Equinox extension to the Manifest file to
-make a jar available as a bundle by reference, rather than by
-wrapping it inside a bundle. This provides a way to build EclipseLink
-examples that rely on third party (possibly commercial) JDBC drivers
-without having to ship those drivers with EclipseLink.
-This bundle contains *NO* classes. For it to function you must define the
-environment variable DERBY_HOME, (e.g., DERBY_HOME=C:\bin\db-derby-
-In the bundle Manifest DERBY_HOME is used to reference the derbyclient.jar
-to make its classes available as if they resided inside the bundle. The
-jar is referenced as "DERBY_HOME\lib\derbyclient.jar".
-DERBY_HOME must be defined either in your environment or in the Eclipse
-Application launch configuration on the "Environment" tab.
-In Eclipse, PDE will give the error:
- "Package 'org.apache.derby.jdbc' does not exist in this plug-in"
-This is expected--don't panic. At runtime, Equinox will resolve the
-jar using the environment variable.

Back to the top