I'm not really that familiar with the building of Cocoon2.1.x apps but shouldn't there be some blocks.properties (not 100% sure about the name) file used by ant where you can determine which blocks you want to include? That would be a good starting point to compare with the default one.
By the way, I noticed that the last modified timestamps were very similar, as if the Dspace jar was from a scheduled build from another day. Regular cocoon jar : 4/12/2006 12:56 PM DSpace jar: 4/11/2006 12:56 PM Can you also explain what the point is of this exercise? You don't have the sources used to build the DSpace.jar in some source repository? Kind regards, Robby From: DeVries, Joe [mailto:joe.devr...@austin.utexas.edu] Sent: Thursday, December 08, 2011 10:43 PM To: dev@cocoon.apache.org Cc: Sands Alden Fish (sa...@mit.edu); Scott Phillips (scott.a.phill...@gmail.com) Subject: RE: Determining blocks specified for building an existing cocoon 2.1.9 jar Hi Robby, I ran Java Decompiler on both jars and compared the resulting files. Unfortunately there are over 600 differences (see attached list), with oddities such as: cocoon-2.1.9.src\org\apache\cocoon\Cocoon.java cocoon: boolean result = this.threadSafeProcessor.process(environment); dspace -2.1.9.src\org\apache\cocoon\Cocoon.java: result = this.threadSafeProcessor.process(environment); However, I don't know very much about decompiling, so maybe these are misleading results. There are also 6 new classes in the DSpace version: org\apache\cocoon\components\flow\javascript\fom \CompilingClassLoader$1.java org\apache\cocoon\components\flow\javascript\fom\ CompilingClassLoader$2.java org\apache\cocoon\components\flow\javascript\fom\ CompilingClassLoader$3.java org\apache\cocoon\components\flow\javascript\fom\ CompilingClassLoader$4.java org\apache\cocoon\generation\ JXTemplateGenerator$3.java org\apache\cocoon\transformation\IncludeTransformer$1.java I was going to look into a tool like clirr to check for binary compatibility and see if that can narrow down any differences. Joe -- Joe DeVries Sr Software Developer/Analyst Digital Library Services, TDL University of Texas at Austin 512-495-4639 PCL 1.335 / S5477 From: Robby Pelssers [mailto:robby.pelss...@nxp.com] Sent: Thursday, December 08, 2011 2:39 PM To: dev@cocoon.apache.org Cc: Sands Alden Fish (sa...@mit.edu) Subject: RE: Determining blocks specified for building an existing cocoon 2.1.9 jar I unpacked both jar files with winrar and noticed some differences in size for a few files. One of those files is cocoon.roles for example. I suggest you take the same approach and find out by using some compare tool to find the exact differences. Kind regards. Robby Pelssers From: DeVries, Joe [mailto:joe.devr...@austin.utexas.edu]<mailto:[mailto:joe.devr...@austin.utexas.edu]> Sent: Thursday, December 08, 2011 9:25 PM To: dev@cocoon.apache.org<mailto:dev@cocoon.apache.org> Cc: Sands Alden Fish (sa...@mit.edu<mailto:sa...@mit.edu>) Subject: Determining blocks specified for building an existing cocoon 2.1.9 jar Hello, I am trying to recreate a custom built Cocoon 2.1.9 jar used by DSpace. The custom jar has a different size and checksum from the 'official' cocoon-2.0.9.jar, and I don't believe that there were and changes to the source code. It was likely built with certain blocks included/excluded. Is it possible to somehow determine which blocks were included/excluded at build time by looking at an existing jar file? http://repo1.maven.org/maven2/org/dspace/xmlui/cocoon/cocoon/2.1.9/cocoon-2.1.9.jar md5: 8f4d38294286cb550a2262720833fb55 http://mirrors.ibiblio.org/pub/mirrors/maven2/cocoon/cocoon/2.1.9/cocoon-2.1.9.jar<http://mirrors.ibiblio.org/pub/mirrors/maven2/cocoon/cocoon/2.1.9/> md5: 1d80a0a9ed50764c06b664427a2d5098 Thanks, Joe DeVries -- Joe DeVries Sr Software Developer/Analyst Digital Library Services, TDL University of Texas at Austin 512-495-4639 PCL 1.335 / S5477
