[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-update-dev] Automatic Product Extension Install
|
Links were not designed to be used that way. They were designed to be laid
down by the native installed, and not frequently changed. Changes in the
link file prompt reconciliation and should not be taken lightly.
Your install handler does not run because it is called when an operation is
performed on the feature (install, update, enabling, disabling etc.). No
operation is performed on features already present in the application (at
least not during the reconciliation).
Having said that, your link file should still be found on restart, so you
may have something trivial like a typo or similar. Link files are just that
- files, and we don't care who wrote them (manually using Notepad,
programmatically, using native installer etc.).
Regards,
Dejan Glozic, Ph.D.
Manager, Eclipse Platform Components
D2/MY7/8200/MKM
IBM Canada Ltd.
Tel. 905 413-2745 T/L 969-2745
Fax. 905 413-4854
Mary Kroening
<mary@xxxxxxxx> To: platform-update-dev@xxxxxxxxxxx
Sent by: cc:
platform-update-dev-admin@ Subject: [platform-update-dev] Automatic Product Extension Install
eclipse.org
03/25/2003 12:30 PM
Please respond to
platform-update-dev
We would like to install a product documentation extension on-the-fly when
Eclipse starts up, or when one of my plug-ins starts up. I did this by
adding some code to my UI plugin to create the links subdirectory (if it
does not exist), then create and write the file containing the pathname of
the plugin. However, this does not work. Eclipse does not even recognize
the linked plugin next time it restarts.
I understand the recommended procedure is a separate install program, but
that creates quite a few difficulties for us as the documentation can move.
Is there a way to dynamically install a link? Ideally I would like to check
for our product extension (the documentation) on every invocation of
Eclipse, and if its not there, recreate the link (as the documentation may
have moved).
However, it may be enough to be able to run some code when "Please
wait...completing the install" appears the first time Eclipse is run with
our plug-ins installed.
I tried writing an install handler extending BaseInstallHandler, but it is
never called. I presume this is because it is only called when the Update
Manager is working.
Any thoughts?
Thanks,
Mary Kroening
Amzi! inc.
_______________________________________________
platform-update-dev mailing list
platform-update-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-update-dev
