From: Markus B. <Mar...@gm...> - 2005-08-25 17:00:13
|
Werner Schuster (murphee) wrote: > Markus Barchfeld wrote: > >> Thanks for your hint. Although I am not sure if the additional step >> of extracting the *.rb file to the workspace location simplifies the >> matter. And I don't think the files belong to the workspace because >> they are coupled with the plugin-version. What if somebody uses the >> same workspace with different versions of the plugin? > > > Hmm... that can be solved by simply putting the file inside a > directory that is unique to the plugin relase. So, if you use it with > Relase 0.x a directory 0_x/ is created (and the file stored in there); > If you use it with 0_y afterwards, no 0_y/ is found, and the plugin > does the same thing, just this time for 0_y,... > > I know, doesn't make the whole thing easier. But: are there any other > plugin specific filesystem locations that could be used (if .jar > Plugins are required). Fair point :-). Maybe we should keep at least one non-jar plugin (eg. rdt.core) or create a dummy plugin for the ruby files. I've just checked the Eclipse plugins itself and they also do not come exclusively as jar plug-ins. Do you understand this distinction? BTW, what are the reasons for using jar plug-ins except for "its new, I want to have it"? Thanks Markus |