Community
Participate
Working Groups
I20030813++ I have the following CU /****************************************************************************** * * Copyright (c) 2003 International Business Machines Corp. and others. * All rights reserved. This program and the accompanying materials * are made available under the terms of the Common Public License v0.5 * which accompanies this distribution, and is available at * http://www.eclipse.org/legal/cpl-v05.html * * Contributors: * IBM Corporation - initial API and implementation ******************************************************************************/ package org.eclipse.jdt.internal.corext.refactoring.participants; import org.eclipse.core.runtime.CoreException; public abstract class DeleteProcessor implements IRefactoringProcessor { private static final <cursor> public final IRefactoringParticipant[] getPrimaryParticipants() throws CoreException { return DeleteExtensionManager.getParticipants(this, getElements ()); } public final IRefactoringParticipant[] getDerivedParticipants() throws CoreException { IRefactoringParticipant[] result= DeleteExtensionManager.getParticipants(this, getDerivedElements()); IRefactoringParticipant[] additions= getMappedParticipants (result); if (additions == null || additions.length == 0) return result; IRefactoringParticipant[] temp= new IRefactoringParticipant [result.length + additions.length]; System.arraycopy(result, 0, temp, 0, result.length); System.arraycopy(additions, 0, result, result.length, additions.length); return temp; } protected IRefactoringParticipant[] getMappedParticipants (IRefactoringParticipant[] result) { return null; } } Opening code assist on <cursor> position only proposes DeleteProcessor.
Do you have the same problem if you use the latest integration build?
It is the latest integration build with the latest plug-in export.
I'd like to find out if this is a regression from the latest integration build. So if you simply use the latest integration build, do you get the same problem? or do you get it only when you use the latest jdt/core patch? It is important to know that for the tomorrow's submission.
I get the problem with the latest integration build without latest JDT/Core patch but with JDT/UI plug-in export
Ok, then this is not a regression from previous jdt/core submission. So I consider our submission ok. This problem will be addressed as soon as David is back.
When the completion token is empty only top level types, enclosing types and expected types are proposed. file X1.java public class X1 { X2 x = <cursor> class X3 {} } class X4{ } file X5.java class X5 { } In this exemple, the completion proposals must be X1, X2, X3, X4. So, the behavior in your test case seems to be correct. But the algorithm do not work correctly, because in my test case X3 and X4 are not found.
Not propose all types is the intended behavior when completion token is empty (avoid to propose all types in the classpath). Problem with field initializer is fixed. Fixed.
Verified.
