You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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 sar...@gmail.com on 13 Feb 2013 at 1:13
Original issue reported on code.google.com by
uwe.h.schindler
on 12 Feb 2013 at 8:25The text was updated successfully, but these errors were encountered: