From dev-return-103160-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org Thu Dec 8 20:39:44 2011 Return-Path: X-Original-To: apmail-cocoon-dev-archive@www.apache.org Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4E40E9D05 for ; Thu, 8 Dec 2011 20:39:44 +0000 (UTC) Received: (qmail 15435 invoked by uid 500); 8 Dec 2011 20:39:44 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 15350 invoked by uid 500); 8 Dec 2011 20:39:44 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 15343 invoked by uid 99); 8 Dec 2011 20:39:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Dec 2011 20:39:44 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [57.67.164.69] (HELO be1ssnxpe1.nxp.com) (57.67.164.69) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Dec 2011 20:39:36 +0000 Received: from EU1RDCRDC1VW024.exi.nxp.com ([134.27.176.169]) by be1ssnxpe1.nxp.com (8.14.4/8.14.4) with ESMTP id pB8KdAiK031601 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 8 Dec 2011 21:39:10 +0100 Received: from eu1rdcrdc1wx032.exi.nxp.com ([134.27.179.186]) by EU1RDCRDC1VW024.exi.nxp.com ([134.27.176.169]) with mapi; Thu, 8 Dec 2011 21:39:10 +0100 From: Robby Pelssers To: "dev@cocoon.apache.org" CC: "Sands Alden Fish (sands@mit.edu)" Date: Thu, 8 Dec 2011 21:39:08 +0100 Subject: RE: Determining blocks specified for building an existing cocoon 2.1.9 jar Thread-Topic: Determining blocks specified for building an existing cocoon 2.1.9 jar Thread-Index: Acy150H6ByAWEy6+SJ6jb2DNhX5FMwAAeFdQ Message-ID: <78B923726E7D59429936580CF127E943A1EE4D18B6@eu1rdcrdc1wx032.exi.nxp.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_78B923726E7D59429936580CF127E943A1EE4D18B6eu1rdcrdc1wx0_" MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.5.7110,1.0.211,0.0.0000 definitions=2011-12-08_08:2011-12-08,2011-12-08,1970-01-01 signatures=0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_78B923726E7D59429936580CF127E943A1EE4D18B6eu1rdcrdc1wx0_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 too= l to find the exact differences. Kind regards. Robby Pelssers From: DeVries, Joe [mailto:joe.devries@austin.utexas.edu] Sent: Thursday, December 08, 2011 9:25 PM To: dev@cocoon.apache.org Cc: Sands Alden Fish (sands@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. Th= e 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 cod= e. 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 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 --_000_78B923726E7D59429936580CF127E943A1EE4D18B6eu1rdcrdc1wx0_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I unpacked both jar files with winrar and noticed some differ= ences 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.devries@austin.utexas.edu]
Sent: Thursday, December = 08, 2011 9:25 PM
To: dev@cocoon.apache.org
Cc: Sands Al= den Fish (sands@mit.edu)
Subject: Determining blocks specified fo= r building an existing cocoon 2.1.9 jar

 

Hello,

I am trying to recreate a custom built Cocoo= n 2.1.9 jar used by DSpace.  The custom jar has a different size and c= hecksum from the ‘official’ cocoon-2.0.9.jar, and I don't belie= ve that there were and changes to the source code.  It was likely buil= t with certain blocks included/excluded. 

Is it possible to somehow determine w= hich blocks were included/excluded at build time by looking at an existing = jar file?

http://repo1.maven.org/maven2/org/ds= pace/xmlui/cocoon/cocoon/2.1.9/cocoon-2.1.9.jar
md5: 8f4d38294286cb5= 50a2262720833fb55

http://mirrors.ibiblio.org/pub/mirrors/maven2/= cocoon/cocoon/2.1.9/cocoon-2.1.9.jar
md5: 1d80a0a9ed50764c06b664427a= 2d5098


Thanks,
Joe DeVries

 

 

--

Joe DeVries

Sr Software Developer/Analyst

Digit= al Library Services, TDL

University of Tex= as at Austin

512-495-4639

PCL 1.335 / S5477

 

= --_000_78B923726E7D59429936580CF127E943A1EE4D18B6eu1rdcrdc1wx0_--