RFR: jmod remove

[Chris Hegarty]

On 19/04/12 09:59, David Holmes wrote:
> Hi Chris,
>
> Does this remove native libs and native commands along with any other
> installed "resource" files?

Yeap, sure does.

When installing (from a jmod file), a module keeps a list of it's out of 
module content. Currently we fail if there is a conflict on any of these 
files at install time. So, each of these external files can only belong 
to it's one owner module. When removing we simply delete all the files 
in the modules external files list.

-Chris.

>
> Thanks,
> David
>
> On 19/04/2012 6:47 PM, Chris Hegarty wrote:
>> I heard the following expression a few times, 'rm -rf has reached the
>> limit of its usefulness'! So it's about time we had a 'jmod remove'.
>>
>> The webrev is based upon Mandy's alias support patch [1]. I figured it
>> would most likely be going in after the alias support.
>>
>> http://cr.openjdk.java.net/~chegar/jigsaw/jmodrm.02/webrev/
>>
>> Essentially, you can remove any module not required by a configuration.
>> Fails if you try to remove a module which will break a configuration,
>> unless you specify --force, or remove both the root module along with
>> the dependent module.
>>
>> I added a comment about the parent/child relationship. That is, a module
>> library has no notion of its children so we could remove a module in a
>> parent library that is not part of any configuration in that library,
>> but may be part of a configuration in a child library. I think this is
>> fine for now, but we may have to revisit the parent/child relationship
>> in the future ( beyond the scope of jmod remove ).
>>
>> -Chris.
>>
>> [1]
>> http://mail.openjdk.java.net/pipermail/jigsaw-dev/2012-April/002351.html