Geek Answers Handbook

Apply fix to fix error in Eclipse?

I have a bug in Eclipse. When you go through the code, when it goes to another class, the editor loses focus, and I need to click on it again to continue debugging using keyboard shortcuts.

I found this thread describing the error and the patch to fix it. Is there a way to apply the patch? I assume that it includes the source code.

+7
source share
1 answer

Yes, you will need to recompile the module and install it. Nowadays, using git SCM and using the layouts of the Maven project and the tycho plugin, you can easily rebuild the module (compared to what it was just a few years ago).

Let's see now:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=372941

Patches:

bundles / org.eclipse.e4.ui.workbench.renderers.swt / SRC / org / eclipse / e4 / w / workbench / renderers / S.T. / StackRenderer.java

We search on google "git org.eclipse.e4.ui.workbench.renderers.swt", as a result we get the URL:

https://git.eclipse.org/c/platform/eclipse.platform.ui.git/

This can be used to test module 1 for assembly.

Git is available for many Linux distributions by default, google you ditro name and "install git" for better reference. Windows has https://code.google.com/p/msysgit/ , and on MacOSX there is https://code.google.com/p/git-osx-installer/ all of this provides a command line environment for using git. You can see the EGit / JGit plugins for Eclipse itself to do the job. But the instruction below is for the command line method.

git clone https://git.eclipse.org/c/platform/eclipse.platform.ui.git

Now you will want to find the tagged version of the version you are using. Therefore, you need to find it in your eclipse / plugins / ** folder of the Eclipse installation. The version number can be in the file name or in the MANIFEST.MF file or other * .xml, the version number usually indicates the source date and / or builds the number.

This can help find the link to the eclipse.org website above for the git tree to find the version. This is necessary to get the tag or version name / commit -id (for example, "abc1234":

 # List tags (might see it in the list) git tag -l # Look through history, maybe you can work on the date git log # Finally once you know the version you want # checkout the exact version that goes with your eclipse install git checkout -b mylocalbranch <tag_or_version>

Now you can use Maven to create it.

 cd eclipse.platform.ui.git mvn package # The full-monty would be: mvn deploy (or 'mvn install') # But I am not sure if unit and integration tests will work this easily, using # the 'mvn package' it enough to get you the JAR you need to install in Eclipse.

Now you can search for .jar in subdir build / *, you can turn off the eclipse and put this JAR in the plugins folder so that the version number is newer.

If it works, update the error report. Say it worked for you.

Also think of trying to push it through github accounts as a new change, enlisting the original author.

..

DISCLAIMER: The foregoing is basic on how you can achieve what you want. This may take less than 5 minutes. But there may be complications, and you will need to research them (if you get them) yourself.

You can also do most of the work with Eclipse itself, 'git checkout' and 'build Eclispe plugin module', although for me it can take more than 15 minutes (if there is no complication).

+7
source

More articles:


All Articles