I see jdk1.3.1 jar has an i option but jdk1.2.2 does not. I've never tried it with 1.3.1; only 1.4.2. If I'm reading the docs correctly only the primary jars need indexed. Haven't tried it with Cocoon jars yet. I did find on my own code that the manifest Class-path when defined but the jar not indexed it would not find the dependent jars according to the commandline classpath; it needed the indexing. Also found I could put a patch jar in front of the indexed jar and see it use the patch.
Maintainance of the manifest Class-path could be difficult... ----- Original Message ----- From: "Geoff Howard" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, August 26, 2003 10:16 AM Subject: Re: cvs commit: cocoon-2.1/src/blocks/html/lib .cvsignore jtidy-04aug2000r7-dev.jar > Roger I Martin PhD wrote: > > Hi Carsten, > > > > Just a thought about something I've run into. When a third party makes a > > block or webapp that depends on the same lib but a different version, can > > the jar indexing capability of jdk1.4 jar utility be employed to resolve the > > issues? It involves placing and maintaining a correct Class-Path: ... in > > the jar's manifest and then running jar -i *.jar. > > http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/jar.html#i > > > > Also does anyone know if the indexing really does or would affect the speed > > of bringing up a wepapp and say Tomcat? > > > > Roger > > I have no experience with this but have been interested in it. Would > this necessarily introduce a dependency on 1.4? (in which case I doubt > we'd decide to go that way?) Or would it only require jar-ing with 1.4 > and writing backwards compatible classloaders which respect the indexing? > > Geoff (reading the link now) > >
