Change Modules/*.xml - see:
<A HREF="http://openide.netbeans.org/issues/show_bug.cgi?
id=13921">feature #13921</A>

Target milestone -> 3.3.1.

Summary from mails with Jesse:

We only need to copy content of nbm into netbeans dir
(as Updater does) and then create somemodule.xml in
system/Modules dir, e.g.:

<module name="org.netbeans.modules.somemodule">
    <param name="autoload">false</param>
    <param name="enabled">true</param>
    <param name="jar">somemodule.jar</param>
    <param name="origin">installation</param>
    <param name="release">1</param>
    <param name="reloadable">false</param>
    <param name="specversion">1.1</param>
</module>

'origin':
  installation, installation/autoload
  user, user/autoload depending of module.jar location

  Soon (#17501) installation/eager and user/eager will also be legal   
  values, for modules present in modules/eager/ scan folder, in which   
  case use <param name="eager">true</param>.

'reloadable': False. This is for test modules.

All of them are optional except 'origin' and 'jar'. But better to
include them if you know about them.

'enabled' *cannot* be present (neither true nor false) if either
'autoload' or (soon) 'eager' is true.

'release' should be there only if there is a release version after a
slash, else not.

'specversion' should be there only if
OpenIDE-Module-Specification-Version was given, else not.

See also:
org.netbeans.core.modules.ModuleList.computeProperties(...)

Implemented in trunk.

Thanks.

From the point of view of #20254, it would be ideal if the updater did
not have to deal with user-dir NBMs at all, only home-dir NBMs. I.e.:
all global NBMs installed using updater.jar between restarts; all
non-global NBMs installed with IDE running.

Otherwise the core will have to leave some piece of information for
the updater, in a file somewhere I guess: "what was the last user dir
I used?" This is possible but not as nice.

Verified.

Resolved for 3.3.x or earlier, no new info since then -> closing.