Bug 117526 [Contributions] [Commands] Javadoc warnings in N20051122-0010
/builds/N/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.core.commands/src/org/eclipse/core/commands/INamedHandleStateIds.java:30: warning - Tag @link: Class or Package not found: NamedHandleObjectWithState /builds/N/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.core.commands/src/org/eclipse/core/commands/Command.java:581: warning - @param argument "state" is not a parameter name. /builds/N/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.jface/src/org/eclipse/jface/commands/RadioState.java:46: warning - Tag @link: Class or Package not found: Boolean.TRUE /builds/N/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.jface/src/org/eclipse/jface/commands/RadioState.java:46: warning - Tag @link: Class or Package not found: Boolean.FALSE /builds/N/src/plugins/org.eclipse.platform.doc.isv/../org.eclipse.ui.workbench/Eclipse UI/org/eclipse/ui/handlers/RegistryRadioState.java:51: warning - Tag @link: Class or Package not found: Boolean.FALSE
bundles/org.eclipse.core.commands/src/org/eclipse/core/commands/Command.java
/*******************************************************************************
 * Copyright (c) 2004, 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.ArrayList;
import java.util.Collection;
import org.eclipse.core.commands.common.NotDefinedException;
import org.eclipse.core.internal.commands.util.Util;
/**
 * <p>
 * A command is an abstract representation for some semantic behaviour. It is
 * not the actual implementation of this behaviour, nor is it the visual
 * appearance of this behaviour in the user interface. Instead, it is a bridge
 * between the two.
 * </p>
 * <p>
 * The concept of a command is based on the command design pattern. The notable
 * difference is how the command delegates responsibility for execution. Rather
 * than allowing concrete subclasses, it uses a handler mechanism (see the
 * <code>handlers</code> extension point). This provides another level of