assertThat(filter.include(artifact), is(false));
    }

    @Test
    void testExcludeArtifactIdWildcardNoMatch() {
        Exclusion exclusion = new Exclusion();
        exclusion.setGroupId("org.apache.groovy");
        exclusion.setArtifactId("*");
        ExclusionArtifactFilter filter = new ExclusionArtifactFilter(Collections.singletonList(exclusion));

        assertThat(filter.include(artifact), is(true));
    }

- we also seem to have information like the plugin lifecycle model that's buried inside the maven execution model
- we also seem to have artifact information tangled inside the plugin model
- we have to deal with scripting implementations (groovy, beanshell, ruby)
- we need to deal with a shared context for plugins, like the guarded mojos
- we need to deal with plugins as core application logic which can also interact with plugins