<modules>
    <module>plexus-action</module>
    <module>plexus-archiver</module>
    <module>plexus-bayesian</module>
    <module>plexus-command</module>
    <module>plexus-compiler</module>
    <module>plexus-drools</module>
    <module>plexus-formica</module>
    <module>plexus-formica-web</module>
    <module>plexus-hibernate</module>
    <module>plexus-i18n</module>
    <module>plexus-interactivity</module>

  <modules>
    <module>plexus-action</module>
    <module>plexus-archiver</module>
    <module>plexus-bayesian</module>
    <module>plexus-command</module>
    <module>plexus-compiler</module>
    <module>plexus-drools</module>
    <module>plexus-formica</module>
    <module>plexus-formica-web</module>
    <module>plexus-hibernate</module>
    <module>plexus-i18n</module>
    <module>plexus-interactivity</module>

<plugins>
  <plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-resources-plugin</artifactId>
    <version>1.0</version</version>
    <executions>
      <execution>

- how to incorporate the metadata processor to start with
- create a hook to programmatically configure the test
- create a plugin processor
- directory
- jar
- hooks for loading

- I could make an annotation that marked another class as its plugin discoverer, I could just add it to
  the component descriptor and when it's loaded we can add the discoverer, that would be simpler. I could