[platform-update-dev] Are bad features supposed to configure?f

[Pat McCarthy <patmc@xxxxxxxxxx>]

I've  been playing install games
again... RC1 based this time around.

Q on what is right/wrong.

I have a bad feature (some would say
all mine are bad).
This feature has a requires block:
   <requires>
      <import plugin="org.eclipse.ui.nothere"/>
   </requires>

I can add this feature to Eclipse without
a problem. Either using a link file, or the Product Config dialog to add
an extension.  Plugins in the feature get added/work.
Only when I try to disable the feature
does the platform acknowledge that it is bad with a warning that I won't
be able to return to this config state.

No visual clues, no error messages,
no warning in status.

Is this right?  Expected?? The
design???

Pat McCarthy   --   Eclipse Platform Enablement (3ECA)
                    
        --   RTP, NC
                    
        --   (919 254-6231 / 8-444-6231 -- FAX
8-444-8169)
                    
        --   Internet: PatMc@xxxxxxxxxx  
               
                    
        --   Lotus: Pat McCarthy/Raleigh/IBM