Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <28895338.1169053050781.JavaMail.jira@brutus>
Date: Wed, 17 Jan 2007 08:57:30 -0800 (PST)
From: "Alex Blewitt (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_12465445 ] 

Alex Blewitt commented on HARMONY-2479:
---------------------------------------

I guess this bug can be closed -- the code is in there now. I've put in a patch (HARMONY-2957) for a few other things, but there doesn't seem to be much motion on that one.

> [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