Community
Participate
Working Groups
As investigating another bugzilla, https://bugs.eclipse.org/bugs/show_bug.cgi?id=346349, I found out that the remote indexer has been treat header files as source files to parse. This is because the variable of fValidSourceUnitNames(a list of source files extensions) in the standaloneIndexer class never gets populated, so when StandaloneIndexerInputAdapter ask if a file is a source unit, it always return true, then it will be parsed as a source unit. This may not have a big impact in the parse result, but after we fix this bug, we have to run a thorough indexer test to make sure everything still works OK.
Created attachment 197736 [details] api update patch Add the api changes of the fix first, hoping I can include the api update into Indigo. This fix doesn't interact with any existing functions, so it has no impact to anything.
RC4a was the final build. No further builds are planned at this stage.
Created attachment 197738 [details] A bit updated patch
(In reply to comment #2) > RC4a was the final build. No further builds are planned at this stage. Hi, Greg: We understand it is impossible to add the entire fix into Indigo at this late, but we are hoping we can update the api first in Indigo, then later on when we add a real fix, we won't break the api changing rule. This fix is juts like a place holder and doesn't interact with any existing functions, so it has no impact to any of current functions. Is it possible to have another build to include this patch in?
Do you have API tooling enabled? I don't see any version number changes in the patch. Unfortunately it is not possible to update the PTP build as this late stage as the Indigo builds have been disabled pending release of the RC4 milestone tomorrow. Even if I do another PTP build, and a rebuild of Indigo is requested before GA, they will still probably reject the update if any version numbers have changed.
(In reply to comment #5) > Do you have API tooling enabled? I don't see any version number changes in the > patch. > Unfortunately it is not possible to update the PTP build as this late stage as > the Indigo builds have been disabled pending release of the RC4 milestone > tomorrow. > Even if I do another PTP build, and a rebuild of Indigo is requested before GA, > they will still probably reject the update if any version numbers have changed. Ah I see, then I guess we will have to wait for a fix pack to add it. I have API tooling enabled and added a since tag to the new api function, getFValidSourceUnitNames, as the plugin version was already updated, so I didn't change it. Should I update something else?
The package is internal, so this is not an API change. I've committed this patch, so if there's a rebuild of Indigo it may get in.
John is a committer... shouldn't this be iplog- ?
I don't think it needs any iplog in that case.
Created attachment 197970 [details] a fix patch add a fix patch on top of the previous api update patch, will wait until Indigo is completed and then commit it into a fix pack.
Created attachment 197972 [details] Updated fix patch
It doesn't look like this was ever applied.
