Maven plugin should only uses classes directory and not entire runtime classpath about testability-explorer HOT 3 CLOSED

Thanks for reporting this and especially for the patch. I'm leaving the 
artifactId,
since it makes sense with the groupId and matches the ant task. See
http://build.hevery.com/job/Testability-Explorer/259/changes#detail0

I understand the point that it makes sense in terms of the groupId, but I know 
that
you can specify some plugins without groupIds.  This may be only for
org.apache.maven.plugins....I cannot recall at this time.  If you can do it for 
any
groupId mapped in your settings.xml such as

  <pluginGroups>
    <pluginGroup>com.google.testability-explorer</pluginGroup>
  </pluginGroups>

then you might have a problem with this approach because then they would only 
need to
put the following the pom:

<plugin>
  <artifactId>maven2-plugin</artifactId>
</plugin> 

and that can be really confusing.  While I think this is always a bad way to 
define
plugins without groupIds, I see it all the time.

Ah, I see, thank you for the explanation. I agree that it would suck if the 
groupId
wasn't always listed with the artifactId.

I submitted that change as
http://code.google.com/p/testability-explorer/source/detail?r=328

Thanks again for the help!!