tasks.register('someTask') { ... }

instead of eagerly _creating_ the task:

    task someTask { ... }

The major difference between these two syntaxes is, that the configuration block of an registered task will only be executed when the task is actually created due to the build requires that task to run. The configuration block of an eagerly created tasks will be executed immediately.

   *
   * @return the source of this event.
   */
  public Object getSource() {
    return source;
  }

  /**
   * Returns the wrapped, 'dead' event, which the system was unable to deliver to any registered
   * subscriber.
   *
   * @return the 'dead' event that could not be delivered.
   */
  public Object getEvent() {
    return event;
  }

  @Override
  public String toString() {

     * If the value is an Entity object, it will be converted to a Map using BeanUtil.
     * If the value is a Collection containing Entity objects, each Entity will be converted to a Map.
     * For other types of values, they are registered directly.
     *
     * @param data the RenderData object to register the value in
     * @param key the key to associate with the value

 * the {@link EventBus}.
 *
 * <p>Unless also annotated with @{@link AllowConcurrentEvents}, event subscriber methods will be
 * invoked serially by each event bus that they are registered with.
 *
 * @author Cliff Biffle
 * @since 10.0
 */
@Retention(RetentionPolicy.RUNTIME)
@Target(ElementType.METHOD)
@Keep

    /**
     * Default constructor.
     */
    public WebApiManagerFactory() {
        // Default constructor
    }

    /**
     * Array of registered web API managers.
     */
    protected WebApiManager[] webApiManagers = {};

    /**
     * Adds a web API manager to the factory.
     *
     * @param webApiManager The web API manager to add
     */

    private PrefixQueryCommand queryCommand;
    private QueryFieldConfig queryFieldConfig;

    @Override
    protected void setUpChild() throws Exception {
        // Get the queryProcessor and queryFieldConfig that were registered in parent class
        queryProcessor = ComponentUtil.getComponent("queryProcessor");
        queryFieldConfig = ComponentUtil.getComponent("queryFieldConfig");

        // Initialize and register PrefixQueryCommand

To get a connection to a specific server, use `Manager.Connection(host)` to get a connection to the specified host.
From this connection individual requests can be made.

Each handler, with optional subroutes can be registered with the manager using
`Manager.RegisterXHandler(handlerID, handler, subroutes...)`.

A `Handler()` function provides an HTTP handler, which should be hooked up to the appropriate route on the server.

  // name is
  // 'main'. Work around this by creating a 'main' source set that forwards to 'jvmMain'.
  //
  // The forwarding SourceSet also needs to fake out some task names to prevent them from
  // being
  // registered twice.
  //
  // https://github.com/bndtools/bnd/issues/6590
  val mainSourceSet = BndBuildAction.installWorkaround(project)

  val osgiApi = configurations.create("osgiApi")
  dependencies { osgiApi(kotlinOsgi) }

	// The only aim is to generate an HTTP request in a way that the relevant/registered end point is evoked/called.
	nilBucket := "dummy-bucket"
	nilObject := "dummy-object"

	nilReq, err := newTestSignedRequestV4(http.MethodPut, getCopyObjectURL("", nilBucket, nilObject),
		0, nil, "", "", nil)

	// Below is how CopyObjectHandler is registered.

        filterList.add(filter);
        createFilterChain();
    }

    /**
     * Creates the filter chain by combining all registered filters.
     * The chain starts with the default filter chain and appends each registered filter.
     */
    protected void createFilterChain() {
        FilterChain chain = createDefaultFilterChain();
        for (final Filter element : filterList) {