Mailing-List: contact harmony-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <22854946.1161728238298.JavaMail.root@brutus>
Date: Tue, 24 Oct 2006 15:17:18 -0700 (PDT)
From: "Alex Blewitt (JIRA)" <jira@apache.org>
To: harmony-commits@incubator.apache.org
Subject: [jira] Commented: (HARMONY-1871) [classlib][pack200] Ongoing
 improvements to pack200; work-in-progress
In-Reply-To: <175236.1160901335053.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/HARMONY-1871?page=comments#action_12444537 ] 
            
Alex Blewitt commented on HARMONY-1871:
---------------------------------------

Looking good :-)

> [classlib][pack200] Ongoing improvements to pack200; work-in-progress
> ---------------------------------------------------------------------
>
>                 Key: HARMONY-1871
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1871
>             Project: Harmony
>          Issue Type: Improvement
>          Components: Classlib
>            Reporter: Alex Blewitt
>         Assigned To: Paulex Yang
>            Priority: Trivial
>         Attachments: pack200.main.patch, pack200.test.patch
>
>
> This is a work-in-progress of the pack200 implementation that allows a Jar to be written and class files generated. It's not complete (by a long shot) but it shows end-to-end ability.
> The code is pretty ugly at the moment; I expect (for example) the code to write out classes will get factored into its own package and there's a lot more tidying up on Segment to do as well. However, it's pretty volatile (in the sense that I'm still working on the internals and moving it around) so it would be easier to leave code cleanups and message extraction until it's more complete. To that end, I've rolled back the changes from HARMONY-1327.
> It would probably make my life easier if this patch was applied before the code was moved into a different module :-) I'm not sure how well an svn up will work in this instance since I don't have the entire trunk checked out.

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