db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren" <m.v.lunte...@gmail.com>
Subject Re: [jira] Commented: (DERBY-1746) upgrade tests should start using 10.1.3 released builds
Date Mon, 28 Aug 2006 22:17:29 GMT
On 8/28/06, Kristian Waagan <Kristian.Waagan@sun.com> 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 derby.jar. Using the other jars
don't cause the same trouble.
> > - comparing the derby.jar and derby.jar it seemed the main difference
was that the does not have the directories in the jar.
> > - When I unjarred 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
> Hi Myrna,
> This is just a shot in the dark, I have not investigated on my own.
> You say that you unjarred, 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 jars are?
> --
> Kristian

I thought about that, but I assumed that if I unjarred a jar file that
has a manifest (as the original 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.


View raw message