An example of a failure that used to be buried in the log is a project
that failed to be created due to different case resource exception.
Change-Id: I89acd7474d499cfe258dfdd840983bef64d38838
Deprecated since CDT 8.0 and not used anywhere.
Change-Id: Ie0dc3e844dfc2edd9ac4e77501372fec7a36c2f2
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
The check-code-cleanliness CI jobs have not been running recently,
so this commit is to the code up to those minor changes
Change-Id: I9fb4b0213dec558f58c5ca718b3d2685564ef456
Get rid of it in user visible places for now.
Change-Id: If887dce5de1a9a23a8fa2a55445b632b31ba6401
Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
If an option page contributed by an extension throws an exception,
then none of the other pages get created. It is better to use a
SafeRunner when in such case where plugins could break other things
than its own functionality.
Change-Id: I531c966be8ef6460a838b3d10bc61dcbdbe627b0
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
Without setting dependent plug-ins to minimum version to match the
target platform we are aiming for we can imply (and therefore let install)
CDT into older versions of Eclipse where CDT does not actually work.
This can be exposed in very odd ways, such as IllegalAccessError, when
platform has allowed API changes.
However, rather than update every single bundle in CDT, only the
o.e.cdt.core/ui bundles are being updated as this should achieve the
desired result without every other bundle needing to be touched.
See Bug 536448
Change-Id: Ifad2e0eef003b037ac332301120c26fe079a2e7f
Without setting dependent plug-ins to minimum version to match the
target platform we are aiming for we can imply (and therefore let install)
CDT into older versions of Eclipse where CDT does not actually work.
This can be exposed in very odd ways, such as IllegalAccessError, when
platform has allowed API changes.
However, rather than update every single bundle in CDT, only the
o.e.cdt.core/ui bundles are being updated as this should achieve the
desired result without every other bundle needing to be touched.
See Bug 536448
Change-Id: I1c8f102a9a750e40970197da3e6cd56d139492bc
Methods weren't added if the virtual methods were in a base
template class.
Change-Id: I34b05eeb1e7dc5ce83944a642461eca521764967
Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
It's now possible to select among four options for the
implementation of single method stub: delete, default, inline
or definition.
Change-Id: I9aac9c53a5a7143235d0f2f447b8d22fa2e2c839
Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
Rules used:
1) Default is right alignment to be compliant with built-in formatter
rules;
2) Pointer with declarator without name will be always left alignment
unless there's a nested declarator;
3) Return value of methods/functions is always left alignment;
4) If left alignment is selected, if space after comma is selected too
for a declaration list, space is always forced after the comma.
Change-Id: I82d5ad130e665e5357644cc59655a558f3fb732f
Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
The option was already used but there wasn't any widget in the UI
to let user change it.
Change-Id: Ib8795468cc83b89bb3ef9676a5e0ed3f288d55da
Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
Fix keybinding so that is doesn't conflict with "Last edit location"
Change-Id: I75ab9ad4a46e64808cbe4f71dfa95f75fc20780e
Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
Init list was always on new lines regardless user input about new line
policy or wrapping policy.
Change-Id: I1ac85611129c23e89d9b299ca87ced314ad542f3
Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
Search background color will be now taken from:
Preferences > General > Appearance > Color and Fonts > Match highlight
background color
so it will look good on both default and dark theme.
Change-Id: I2800b6cd3ac651cda577cc533149f0ead0fa75f3
Signed-off-by: Tomasz Rojek <me@tomrosystems.com>
We used color keys not saved in the preferences and without any UI
widget. The user wasn't able to change them.
Change-Id: I48bc4e411d2bc016501613b7dbfb0e7f95532099
Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
Formatter has an option for it but the user can't change it
without an option in the UI.
Change-Id: Ibe3f36bd55b24ef06c13300792e425592285c8ea
Signed-off-by: Marco Stornelli <marco.stornelli@gmail.com>
Refresh the toolbar buttons after registering the command handlers, to
make sure that they are active.
Change-Id: Ibee71a54fff7be0325257d25247e4e73f8b09b2e
Task-Url: https://bugs.eclipse.org/bugs/show_bug.cgi?id=544535
Signed-off-by: Felix Morgner <fmorgner@hsr.ch>
The previous alignment of all the warnings/ignores
led to too many warnings that weren't there before. This
commit relaxes them a bit.
The core/org.eclipse.cdt.core/.settings/org.eclipse.jdt.core.prefs
is still the "master" copy, with
releng/scripts/check_code_cleanliness.sh containing the
exceptions that apply to test plug-ins.
Change-Id: Ibd4e31ade0b42b31e7cbe5a94f06c6fc15183a56
