$ git checkout pull_request_branch
$ git rebase -i HEAD~n //n is the number of commits you would like to see during rebase or you could specify the number of commits you have made to the pull request.
3. Replace pick with drop for commits that you want to discard from the PR
Once you are done with the rebase, push forcefully to the remote branch
$git push origin pull_request_branch -f
You are good!
Create plugin_customization.ini in your product branding plugin with the following property
# show progress on startup
org.eclipse.ui/SHOW_PROGRESS_ON_STARTUP=true
Add plugin_customization.ini in plugin.xml property extension
<plugin>
<extension
id="myid"
name="my-IDE"
point="org.eclipse.core.runtime.products">
<product
application="org.eclipse.ui.ide.workbench"
description="About product description"
name="%product.name">
<property
name="appName"
value="my-IDE">
</property>
<property
name="preferenceCustomization"
value="plugin_customization.ini">
</property>
</product>
</extension>
</plugin>
To control the coordinates of the progress monitor and message on the splash screen add the following three properties
<property
name="startupForegroundColor"
value="000000">
</property>
<property
name="startupMessageRect"
value="7,305,285,20">
</property>
<property
name="startupProgressRect"
value="7,290,490,15">
</property>
In Eclipse 3.x RCP applications, this could be done directly from the .product splash screen page
This is a simple icon editor which I'm using these days for resizing and creating new icons for the eclipse plugin
INSTALLED - This means that OSGi knows about your bundle but there is something wrong and it couldn't resolve. Problems may include thing from missing dependencies to requiring a higher Java VM version than you are running with. To get more information on why your bundle is not resolved try running the diag <bundle id> command, where <bundle id> is your bundle id or bundle symbolic name.RESOLVED - If your bundle is resolved but you expected it to be started, then try starting your bundle from the command-line with the start 123 command. If it won't start, then you should get some feedback as to what the problem is.<<lazy>> - This means your bundle is resolved and is marked to be lazy started. Everything should be ok.ACTIVE - your bundle is resolved and has been started, everything should be working as planned.
(source: OSGi Service Platform – Core Specification)
For example: I want to check the bundle states for my company plugins so I will use the below command.
osgi> ss com.espressif
"Framework is launched."
id State Bundle
6 RESOLVED com.espressif.idf.branding_1.2.0.qualifier
7 ACTIVE com.espressif.idf.core_1.0.0.qualifier
8 STARTING com.espressif.idf.help_1.0.0.qualifier
9 ACTIVE com.espressif.idf.launch.serial.core_1.0.0.qualifier
10 ACTIVE com.espressif.idf.launch.serial.ui_1.0.0.qualifier
11 STARTING com.espressif.idf.sdk.config.core_1.0.1.qualifier
12 STARTING com.espressif.idf.sdk.config.ui_1.0.0.qualifier
13 STARTING com.espressif.idf.terminal.connector_1.0.0.qualifier
14 STARTING com.espressif.idf.terminal.connector.serial_1.0.0.qualifier
15 ACTIVE com.espressif.idf.ui_1.0.0.qualifier
721 ACTIVE com.espressif.idf.debug.gdbjtag.openocd_1.0.0.qualifier
References:
Source code: