<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 148: Pack200 and signed jars</title><link href="https://sourceforge.net/p/easyeclipse/bugs/148/" rel="alternate"/><link href="https://sourceforge.net/p/easyeclipse/bugs/148/feed.atom" rel="self"/><id>https://sourceforge.net/p/easyeclipse/bugs/148/</id><updated>2009-07-15T20:44:05Z</updated><subtitle>Recent changes to 148: Pack200 and signed jars</subtitle><entry><title>Pack200 and signed jars</title><link href="https://sourceforge.net/p/easyeclipse/bugs/148/" rel="alternate"/><published>2009-07-15T20:44:05Z</published><updated>2009-07-15T20:44:05Z</updated><author><name>Philippe Ombredanne</name><uri>https://sourceforge.net/u/pombredanne/</uri></author><id>https://sourceforge.net40b179277c6eefcdaec96e00765f9c7f010defb7</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;In order to avoid adding exceptions to a build when using pack200 signed jars (that should be NOT packed if they have not been -repacked upstream prior to signature) we could do the following test:&lt;/p&gt;
&lt;p&gt;% pack200 --repack this.jar&lt;br /&gt;
% jarsigner -verify this.jar&lt;br /&gt;
If the jar is not verified at that step, then the jar SHOULD NOT be packed or its signature will no verify after pack/unpack.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>