Jiri Rechtacek wrote:
> Please, check it again. I think there are no problematic issues now.

1. What about provide-require/need/recommend dependencies? They are not
mentioned. Are they interpreted by AU?

2. Example B4.1 has "AU1" in diagram yet descr mentions "A1".

3. I don't like using the "OpenIDE-Module-" prefix for manifest
attributes which are not in fact interpreted by the module system.
(-S-I-AU-C, proposed -Essential) Also, since I don't agree with the
direction of the entire proposal as a whole (i.e. its partial
duplication of the functions of the module system, but am OK with it for
6.0 given that we are past feature freeze), I would not recommend using
attribute names which imply permanent status in the official Modules
API. Perhaps "AutoUpdate-" prefixed attributes would make it clearer
that these exist solely for the benefit of the current Plugin Manager UI
and behavior?

4. Regarding *-Essential attribute: maybe. Seems preferable to
special-casing modules in the platform cluster, which would not work for
some modules we would probably consider "essential", e.g. projectui.
(Although projectuiapi, which a lot of things have a dep on, -Needs
projectui, so this particular case would probably not pose a problem.)
Could alternately combine both attributes into one AutoUpdate-Visibility
attribute, with possible values "visible", "hidden", "essential"?

-J.

-- 
jesse.glick@sun.com  netbeans.org  ant.apache.org  hudson.dev.java.net
            http://google.com/search?q=e%5E%28pi*i%29%2B1