On 8/28/06, Kristian Waagan <[EMAIL PROTECTED]> wrote:
Myrna van Lunteren (JIRA) wrote:
> [
http://issues.apache.org/jira/browse/DERBY-1746?page=comments#action_12431034 ]
>
> Myrna van Lunteren commented on DERBY-1746:
> -------------------------------------------
>
> I experimented and found the following:
> - the problem appears to be with 10.1.3.1 derby.jar. Using the other 10.1.3.1
jars don't cause the same trouble.
> - comparing the 10.1.1.0 derby.jar and 10.1.3.1 derby.jar it seemed the main
difference was that the 10.1.3.1. does not have the directories in the jar.
> - When I unjarred 10.1.3.1 derby.jar with jar -tvf, and then jar-ed back up using
jar -xvf *, the resulting derby.jar could be used & the test did not give the
sealing error.
Hi Myrna,
This is just a shot in the dark, I have not investigated on my own.
You say that you unjarred 10.1.3.1, then jar-ed the files back up. By
looking at the jar command used, a manifest does not seem to be specified.
Could the reason why the re-packaged jar is working be because it simply
isn't sealed, as I suppose the official 10.1.3.1 jars are?
--
Kristian
I thought about that, but I assumed that if I unjarred a jar file that
has a manifest (as the original 10.1.3.1 derby.jar has) this manifest
also got unjarred, and thus, when jarring it back up, the manifest
would get jarred back up also...
Naive, probably...But the jar does contain the a manifest again.
I'll see if poking at that gives me some clues.
Myrna
