Alexander Kitaev wrote:
> I tried that once, but as far as I understand patch should replace the
> whole set of plugin libraries, may be I'm wrong, so I will check those
> links, thanks!
Patch actually will create copy of the plugin with a new version and
you can patch individual plugins from any given feature (e.g. my
splitter patch is replacing only jdt.ui plugin from jdt feature).
How Actually it depends from the install handler. In splitter patch
I'm using DelataInstallHandler, which will create copy of the existing
plugin and put resources from the patch on top of it.
> Good news is that from Subclipse 0.9.33 there will be no need to
> install "Subclipse Extension" - JavaSVN will be part of Subclipse. And
> what is not so good is that JavaSVN will be bundled into "core" plugin
> - so there will be no way to update JavaSVN automcatically and
> independenlty on the Subclipse (manual update is still possible of
> course).
I know that, and by the way, in my opinion it would be better to
bundle JavaSVN as a separate plugin within Subclipse feature (look at
junit plugin in Eclipse). Or even better as a dependent feature
(possible optional). See how Eclipse Bytecode Outline plugin is packaged
with ASM plugin, update site is at
http://download.forge.objectweb.org/eclipse-update/ You only need to
choose BCO plugin and ASM plugin will be installed automatically. This
way you can share library between plugins and also update their versions
independently...
regards,
Eugene
> ------------------------------------------------------------------------
> *From:* Eugene Kuleshov [mailto:eu@md.pp.ru]
> *Sent:* Thursday, August 25, 2005 10:17 PM
> *To:* users@subclipse.tigris.org
> *Subject:* Re: Stable SubClipse 0.9.33 + SVN 1.2.3 to use with
> Eclipse 3.1
>
> Alexander Kitaev wrote:
>
>> Even when Subclipse 0.9.33 is not yet released, you still may use
>> JavaSVN 0.9.2 with Subclipse 0.9.32 - exactly the same version
>> that will be included into Subclipse 0.9.33
>> Comparing to version 0.9.1, version 0.9.2 fixes number of svn+ssh
>> issues. It should work well both with 1.1.* and 1.2.* Subversion
>> servers.
>
> By the way, Alexander, you don't really have to package entire
> 500k subclipse.core plugin in order to patch plugin.xml or few
> classes. There is a "patch" feature that you can use for this,
> which should save you quite a lot of the download traffic.
>
> See some examples how patches can be packaged at my Eclipse
> update site at http://www.md.pp.ru/~eu/eclipse/
> There is a splitter patch and memory monitor patch deployed
> there. Some description is at
> http://jroller.com/page/eu?entry=eclipse_patches
>
> regards,
> Eugene
>
>
Received on Fri Aug 26 06:55:31 2005