| distributing non java executables along with a plugin [message #336780] |
Thu, 02 July 2009 06:04  |
Eclipse User |
|
|
|
Hello,
I created a plugin that is an IDE for working with a custom language/platform.
The language/platform is available in several versions, the IDE can adapt to the version each project is declaring to use.
Currently, the user can independently of the Eclipse plugin install several versions of the language/platform, and in Eclipse have different projects use different versions of the language/platform.
I would like to improve the user experience by allowing him to manage language/platform versions installed on his computer via Eclipse.
The user should be able to manage several versions of the language/platform installed on his computer at the same time.
Please note that this language/platform has nothing to do with java.
Before engaging to this path, I would like to know whether it's a deadlock or not.
(Additional constraints I have is that the language/platform is specialized to the host OS - but that certainly can be solved by fragments)
Do you think it is possible, and not fighting the framework too much ?
Thanks,
--
Laurent
|
|
|
| Re: distributing non java executables along with a plugin [message #336826 is a reply to message #336780] |
Mon, 06 July 2009 03:50  |
| Eclipse User |
|
|
|
Hello,
sorry, that I do not have an answer, but instead the very same question. I
also aim to provide "external, non-Eclipse related, non-Java-related"
executables for different platforms as an Eclipse plug-in, such that they
are distributable and updatable via the Eclipse update manager.
I started by creating a small test-plugin that bundels several executables
(for a start only on Mac OS X). The plug-in is contained in a feature,
which in turn is provided via an update site. All was done with the
functionalities provided by the PDE.
1) After installing the plug-in, I realized, that the file permissions of
the executables changed and they no longer were executable. My idea would
now be to omplement an Install Handler for the providing feature.
2) Another problem is that some of the provided external executables
create temporary files in the same folder they are installed, i.e. they
modify the plug-in directory. So, is there any "standard way" to copy the
plug-in into the users workspace, where the operations of the executables
can be carried out safely?
Thanks for any comment / any suggestion.
Stefan
|
|
|
|
| Re: distributing non java executables along with a plugin [message #336843 is a reply to message #336833] |
Tue, 07 July 2009 08:13 |
| Eclipse User |
|
|
|
Paul Webster wrote:
> In 3.5 this is supported by using p2 to install ... specifically
> touchpoints:
> http://wiki.eclipse.org/Equinox/p2/Engine/Touchpoint_Instruc tions
>
> It seems this supports copying out source (maybe contributed
> executables) to a separate (controlled) directory and then supports some
> native touchpoints (like chmod)
>
> PW
>
Hi Paul,
Thanks for the answer.
From it, I can guess that there is in 3.4 no supported way to do this. What I'll do is , as Stefan suggested, create a feature and different version of plugins (maybe even different plugins ids since
I want several version of the executables to be concurrently installed by the user), and maybe resort to an Installation Handler.
==> Do you know of a public documentation about the Install Handler ? I had a hard time finding tutorials or even refs material about it ?
Thanks in advance,
--
Laurent
|
|
|
Powered by
FUDForum. Page generated in 0.23235 seconds
Home