Skip to main content
aboutsummaryrefslogtreecommitdiffstats
path: root/codan/org.eclipse.cdt.codan.core.tests/.settings
AgeCommit message (Collapse)AuthorFilesLines
2022-04-20[releng] Make CDT Clean-up profile match Editor on save actionsJonah Graham1-0/+80
The CDT Cleanup profile had a bunch of extra cleanups applied to it, this prevents running the CDT cleanup profile manually to simulate running the save actions on all Java files Change-Id: Iad491e1258a4ba90d81d1457ea0f6779e3663e38
2020-08-31Bug 566511: [releng] Add missing UTF-8 encoding for all CDT projectsJonah Graham1-0/+2
Includes updates to code cleanliness script Change-Id: Ic495124285e3e002993f34dc12be5ad7337fe13b
2020-08-24Bug 562494: Update BREE to Java 11Jonah Graham1-8/+30
Change-Id: I0c91aafc0cb1b179936acbd4c9df2d961899e3fa
2018-11-24Bug 540373: Update the compiler warnings/ignoresJonah Graham2-14/+14
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
2018-11-22Bug 540373: Standard .settings auto appliedJonah Graham5-37/+432
The releng/scripts/apply_jdt_prefs_to_all_projects.sh was run to copy standard settings to all other projects. Change-Id: I4436c947d7f0142f56b709e661379c3eb54f666b
2017-02-14releng: Make use of Tycho POM-less functionalityMarc-Andre Laperle2-0/+424
This removes a lot of pom.xml from the source tree. This is using the "POM-less" Tycho functionality. See https://wiki.eclipse.org/Tycho/Release_Notes/0.24#POM-less_Tycho_builds One advantage of this is that you do not need to update the version in the pom.xml when you change it in the MANIFEST.MF because the pom.xml is automatically generated. This also reduces a lot of the duplicated information and pom.xml repetition. - Maven 3.3 and up is required. - Only eclipse-plugins and eclipse-features can be pom-less. Repositories, target and others still have pom.xml. - New parent poms are added because a parent is necessary directly one level above the plug-in/feature that will have its pom generated - Some test plug-ins had to be renamed .test -> .tests because it's required so that it detects that it's a test plug-in - Some suites were renamed so that they all use the same consistent name "AutomatedIntegrationSuite" - Profiles were added for the more common test configurations. They are activated by the presence of simple .properties files that only serve to activate the correct profile. The profiles: - One for UI tests (UI present and start in UI thread) - One for SWTBot tests (UI present and do not start in UI thread) Other test plug-ins that are too different are kept intact and still have a pom.xml - Fragments are kept intact since they all have different target platform configurations Change-Id: I9d73380eb766f547830c552daf08053a30b1845c Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>

    Back to the top