| Re: [platform-update-dev] non-plugin data - what happens to it after an install |
Actually as I was looking at this there is already an API method
org.eclipse.update.core.Utilities.newCoreException(String, Throwable). This
should do the trick for you.
Vlad
Klicnik/Toronto/IBM@IBMCA To: platform-update-dev@xxxxxxxxxxx
Sent by: cc:
platform-update-dev-admin@e Subject: Re: [platform-update-dev] non-plugin data - what happens to
clipse.org it after an install
05/14/2002 01:09 PM
Please respond to
platform-update-dev
This is a good suggestion ... will do. For now just use the workaround.
Patrick_Mueller@xxxxxxx
Sent by: To:
platform-update-dev@xxxxxxxxxxx
platform-update-dev-admin@e cc:
clipse.org Subject: Re:
[platform-update-dev] non-plugin data - what happens to
it after an install
05/14/2002 10:56 AM
Please respond to
platform-update-dev
Yikes! OK ... getting there ... :-)
The CoreException bit, to leave early upon error, is a bit problematic for
me. How do I figure out which plugin to use? Status doesn't appear to eat
null or "" for the plugin id, and I don't have a plugin here, really. I'll
give it "update" for now to see how far it goes, but I think you need to
help me build a CoreException, or perhaps you should define your own
exception that lets me fill in the serverity/message fields.
Patrick Mueller
patrick_mueller@xxxxxxx
_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev