Bug 465584 - Incremental build doesn't report breakages when API field refers to internal constant
Summary: Incremental build doesn't report breakages when API field refers to internal ...
Status: NEW
Alias: None
Product: PDE
Classification: Eclipse Project
Component: API Tools (show other bugs)
Version: 4.5   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE API Tools Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2015-04-27 09:17 EDT by Markus Keller CLA
Modified: 2023-09-20 02:15 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2015-04-27 09:17:45 EDT 
Bug that caused bug 465521:

org.eclipse.jdt.ui.ISharedImages is an API interface that contains many String constants that are initialized by references to an internal class, e.g.:

public interface ISharedImages {
    /**
     * Key to access the shared image or image descriptor for a Java compilation unit.
     */
    public static final String IMG_OBJS_CUNIT= JavaPluginImages.IMG_OBJS_CUNIT;
    //...
}

When the value of the constant in the internal class JavaPluginImages is changed, the automatic incremental build does not report the API breakage. Only a full build on the project reveals the problem. The incremental API Tools builder should immediately report the problem.
Comment 1 Eclipse Genie CLA 2019-10-09 03:07:28 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2021-09-29 00:04:29 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2023-09-20 02:15:50 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.