Bug 120150 [Commands] Javadoc bugs in ParameterizedCommand and ExecutionEvent
The constructor for ParameterizedCommand refers to "an array of quadruples (<code>String[]</code>)" for the 'parameterizations' parameter, however the type of that parameter is Parameterization[]. In ExecutionEvent there are several places where it says "parameter name" but I think it should say "parameter id". In the constructor: * @param parameters * The parameters to qualify the execution; must not be * <code>null</code>. This must be a map of parameter names (<code>String</code>) * to parameter values (<code>String</code>). And the method getParameter(final String parameterName) has the same problem. This analysis is based on the code in ParameterizedCommand.getParameterMap() that builds a Map of parameter id to parameter value which is passed to the ExecutionEvent constructor.
bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/ExecutionEvent.java
/*******************************************************************************
 * Copyright (c) 2005 IBM Corporation and others.
 * All rights reserved. This program and the accompanying materials
 * are made available under the terms of the Eclipse Public License v1.0
 * which accompanies this distribution, and is available at
 * http://www.eclipse.org/legal/epl-v10.html
 *
 * Contributors:
 *     IBM Corporation - initial API and implementation
 *******************************************************************************/
package org.eclipse.core.commands;
import java.util.Collections;
import java.util.Map;
import org.eclipse.core.commands.common.NotDefinedException;
/**
 * <p>
 * The data object to pass to the command (and its handler) as it executes. This
 * carries information about the current state of the application, and the
 * application context in which the command was executed.
 * </p>
 * <p>
 * An execution event carries three blocks of data: the parameters, the trigger,
 * and the application context. How these blocks are used is application
 * dependent. In the Eclipse workbench, the trigger is an SWT event, and the
 * application context contains information about the selection and active part.
 * </p>
 * 
 * @since 3.1
 */
public final class ExecutionEvent {