Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <3243942.1168032507570.JavaMail.jira@brutus>
Date: Fri, 5 Jan 2007 13:28:27 -0800 (PST)
From: "Alexei Zakharov (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Commented: (HARMONY-2479) [classlib][pack200] Move pack200
 code to its own module
In-Reply-To: <1819481.1165361361079.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HARMONY-2479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462612 ] 

Alexei Zakharov commented on HARMONY-2479:
------------------------------------------

Alex, sorry for the delay. We have quite a long New Year holidays here in Russia. I've almost finished the transfer and suppose we will have the new module in a couple of days.

> [classlib][pack200] Move pack200 code to its own module
> -------------------------------------------------------
>
>                 Key: HARMONY-2479
>                 URL: https://issues.apache.org/jira/browse/HARMONY-2479
>             Project: Harmony
>          Issue Type: Improvement
>          Components: Classlib
>            Reporter: Alex Blewitt
>         Assigned To: Alexei Zakharov
>            Priority: Minor
>
> The pack200 code currently lives in the archive module, which will ultimately result in a tighter coupling of the internal pack200 code and the external java.util.jar code. Furthermore, whilst the java.util.jar is using generics internally, the pack200 stuff needs to avoid the use of generics and putting it into a different module will allow the compiler and project settings to be appropriately amended.
> We should create another module (e.g. archive-pack200) and then move the o.a.h.a.internal.pack200 and test code into that new module instead, perhaps with a package name change, and then set up a template build.xml and Manifest.MF. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira