[news.eclipse.platform.rcp] Re: Why must a plug-in manifest contain at l

[Mike Higginbotham <higginmi@xxxxxxxx>]

Chris,

Thanks for the rapid response. I removed them with no apparent ill 
affects. Do you know why this became a warning when it was not a warning 
in Eclipse 3.2? I'm still curious as to why this would be a warning. 
What problems could it cause.

Thanks,
Mike

Chris Aniszczyk wrote:
> Mike Higginbotham wrote:
> > Greetings!
> >
> > We are moving from Eclipse 3.2 to Eclipse 3.4. We have several 
> > plugin.xml files that cause "A plug-in manifest must contain at least 
> > one extension or extension point" warnings. As the subject says, "Why 
> > must it?" What is the reasoning behind this message?
> >
> > Our plug-ins have worked fine without extensions or extension points 
> > in the past. They appear to work OK in 3.4. Is there a preference we 
> > can set to keep from getting this warning? Or, is there a simple 
> > extension we can add that shuts this up?
>
> It's as simple as deleting the plugin.xml... if the file is empty than 
> it's not needed. There should be a quickfix to add an extension or 
> extension point... or remove the file.
>
> Cheers,
>
> ~ Chris