Hi,
I found this definition of package sealing in the Java tutorial
(http://java.sun.com/docs/books/tutorial/deployment/jar/):
Package Sealing: Packages stored in JAR files can be optionally sealed so
that the package can enforce version consistency. Sealing a package within a
JAR file means that all classes defined in that package must be found in the
same JAR file.
So I believe what this means is one of the classes that is being loaded is
coming out of a different jar file then the one that the
org.apache.derby.iapi.services.crypto package is in.
(If someone else is more knowledgeable here, please jump in!)
Essentially, what this means is that you have two versions of at least one of
the derby jar files in your classpath. When you add the derby nature to one of
your java projects, you don't need to add it to the project's build path as
well.
If you did not do this double-check that you have not added it to the
classpath that you launched Eclipse from.
Regards,
Susan
