Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support validating test classes in Maven Mojo #4

Closed
GoogleCodeExporter opened this issue Mar 14, 2015 · 3 comments
Closed

Support validating test classes in Maven Mojo #4

GoogleCodeExporter opened this issue Mar 14, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

The current MavenMojo class can only validate classes from the build/classes 
dir, not the test dir. It might be possible to do this with the same Mojo, but 
the problem here is the DependencyResolutionScope, which cannot be changed at 
runtime.
I think we must add a second Mojo (ideally all Mojos using the same default 
base class, only providing access to defaults and classpath)

Original issue reported on code.google.com by uwe.h.schindler on 12 Feb 2013 at 8:25

@GoogleCodeExporter
Copy link
Author

I committed a first version to trunk. The main Mojo Goal was renamed (the old 
one is still there, but deprecated): forbiddenapis -> "check". A new one was 
added: "testCheck"

Original comment by uwe.h.schindler on 12 Feb 2013 at 10:06

  • Changed state: Committed

@GoogleCodeExporter
Copy link
Author

1.2-SNAPSHOT from oss.sonatype.org works for me with the maven build patch I 
attached to ASF JIRA LUCENE-4570.

It was triggering failures where I didn't have excludes setup properly, so it 
seems to fail when it should.

Original comment by [email protected] on 13 Feb 2013 at 1:13

@GoogleCodeExporter
Copy link
Author

Fixed in release 1.2.

Original comment by uwe.h.schindler on 16 Feb 2013 at 10:27

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant