better fix for issue 166575
Not sure what the problem was. Tests pass AFAIK but perhaps only affects a bigger system?
my suspicion is that it could be related to the order of items being looked up from the project.
i'm still inclined to just delete the annotation and related code rather than attempt to fix code I don't understand..
It's a public API, it cannot simply be deleted. If you don't want to fix it, reassign it.
Seems to be reproducible:
1. hg up 71c179e30950
2. ant rebuild-cluster -Drebuild.cluster.name=nb.cluster.groovy
The issue arises when there is more than one project using the same kind of lookup merger, and all have their lookups
initialized before the mergeable class is first queried: for example, when two j2seproject's are opened and then you
right-click each in turn. The mergeable class was being injected into the lookup of the first project to be queried only.
core-main #383e75d2b624 and this is pullable directly into release67 if desired (parented to changeset of #150194 impl).
Since others might wish to use @LM.R in 6.7 I recommend this be merged either into an RC or into a patch update.
Integrated into 'main-golden', will be available in build *200906130201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Jesse Glick <email@example.com>
Log: #166910: @LookupMerger.Registration does not work on >1 project.
The fix has been ported into the release67_fixes repository.