| Summary: | Enable API analysis for org.eclipse.debug.ui.launchview | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Andrey Loskutov <loskutov> |
| Component: | Debug | Assignee: | Andrey Loskutov <loskutov> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | akurtakov, sarika.sinha |
| Version: | 4.23 | ||
| Target Milestone: | 4.23 M2 | ||
| Hardware: | PC | ||
| OS: | All | ||
| See Also: |
https://bugs.eclipse.org/bugs/show_bug.cgi?id=513735 https://git.eclipse.org/r/c/platform/eclipse.platform.debug/+/189809 https://git.eclipse.org/c/platform/eclipse.platform.debug.git/commit/?id=58380fd1f9e9fa02a59a92671f6c79458b099b64 |
||
| Whiteboard: | |||
|
Description
Andrey Loskutov
New Gerrit change created: https://git.eclipse.org/r/c/platform/eclipse.platform.debug/+/189809 Gerrit change https://git.eclipse.org/r/c/platform/eclipse.platform.debug/+/189809 was merged to [master]. Commit: http://git.eclipse.org/c/platform/eclipse.platform.debug.git/commit/?id=58380fd1f9e9fa02a59a92671f6c79458b099b64 Still in the list ??? https://download.eclipse.org/eclipse/downloads/drops4/I20220120-1800/apitools/analysis/html/Skipped%20Bundles/report.html @Alex, Sarika - any idea where that list is generated? It's generated by https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse.platform.releng.tychoeclipsebuilder/eclipse/buildScripts/api-tools-builder.xml Changes in pom.xml files are ignored by compare to filter out parent pom versoin changes. As the change is in pom.xml you have to either create forceQualifierUpdate.txt file to enforce new version is published or create some trivial fix in it. I prefer the second option as if we are to publish new jar make it have at least some change. (In reply to Alexander Kurtakov from comment #4) > It's generated by > https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/ > tree/eclipse.platform.releng.tychoeclipsebuilder/eclipse/buildScripts/api- > tools-builder.xml > Changes in pom.xml files are ignored by compare to filter out parent pom > versoin changes. > As the change is in pom.xml you have to either create > forceQualifierUpdate.txt file to enforce new version is published or create > some trivial fix in it. I prefer the second option as if we are to publish > new jar make it have at least some change. OK, makes sense, so I can close this one as done. Next code change should also trigger API analysis. |