Pull parser for jmod packages

[Rémi Forax]

On 05/25/2012 12:37 PM, Chris Hegarty wrote:
> On 25/05/2012 09:35, Paul Sandoz wrote:
>> Hi
>>
>> At the moment the reader of jmod packages, 
>> org.openjdk.jigsaw.ModuleFile.Reader, is tightly bound to reading a 
>> module file and extracting out the contents into a directory (and 
>> tightly bound to the implementation details of the library contents).
>>
>> How about we develop a module file pull parser?
>
> I really like this idea. I was always a little uncomfortable with the 
> tight relationship between the reading of the module file and the 
> writing out of its data. For example, jsign and the changes to support 
> listing the module file contents does some funnies to avoid writing 
> out the actual contents. A pull parser type API may work well here. 
> I'll take a stab at what this would look like ( unless you want to? ).
>
>> Such a parser can then be used by "jmod install/extract" [1] and by 
>> other tools, for example IDEs to more easily extract out the class 
>> file contents for analysis.
>>
>> Paul.
>>
>> [1] Arguably "jmod extract" should be "jpkg extract"
>
> Yes, I agree. If jpkg evolves into a tool for creating and inspecting 
> module files/native packages, then I think 'extract' is better suited 
> in jpkg.
>
> -Chris.

yes, great idea !

Rémi