code is a great way to give something back to the open source community. Before
you dig right into the code, there are a few guidelines that we need
contributors to follow so that we can have a chance of keeping on top of
things.

Some of the ideas are documented in the [Maven Wiki][maven-wiki]
which might be interesting to read and for further discussion.

Getting Started
---------------

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.eventspy;

/**
 * A skeleton eventspy that does nothing other than helping implementors.
 * @since 3.0.2
 */
public abstract class AbstractEventSpy implements EventSpy {

    public void init(Context context) throws Exception {}

    public void onEvent(Object event) throws Exception {}

 * </p>
 * <p>
 * Wise voices have suggested that maybe aggregators shouldn't be bound to the ordinary
 * lifecycle at all, in which case we wouldn't be needing this class at all ( and
 * ProjectBuildList.getByTaskSegments). Or maybe they should be introduced in the calculation
 * of the execution plan instead, which seems much nicer.
 * </p>
 * <p>