[
https://issues.apache.org/jira/browse/LUCENE-4570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated LUCENE-4570:
-------------------------------
Attachment: LUCENE-4570-maven.patch
Patch adding forbidden-api calls to the Maven build.
Currently fails when running against test classes because the MavenMojo
hard-codes using the compile-scope classpath:
[https://code.google.com/p/forbidden-apis/source/browse/trunk/src/main/java/de/thetaphi/forbiddenapis/MavenMojo.java#139]
- here's the error I get:
{noformat}
[ERROR] Failed to execute goal de.thetaphi:forbiddenapis:1.1:forbiddenapis
(check-forbidden-jdk-apis) on project lucene-core-tests: Check for forbidden
API calls failed: java.lang.ClassNotFoundException: Loading of class
org.apache.lucene.util.LuceneTestCase failed: Not found -> [Help 1]
{noformat}
Uwe, can you look into adding a way for MavenMojo to change which classpath to
use? Maybe look at the name of the phase to which an execution is bound, and
if it contains the word "test" (e.g. "process-test-classes", use the test-scope
classpath instead of the compile-scope classpath?
> Release ForbiddenAPI checker on Google Code
> -------------------------------------------
>
> Key: LUCENE-4570
> URL: https://issues.apache.org/jira/browse/LUCENE-4570
> Project: Lucene - Core
> Issue Type: New Feature
> Components: general/build
> Reporter: Robert Muir
> Assignee: Uwe Schindler
> Fix For: 4.2, 5.0
>
> Attachments: LUCENE-4570-maven.patch, LUCENE-4570.patch,
> LUCENE-4570.patch, LUCENE-4570.patch, LUCENE-4570.patch, LUCENE-4570.patch
>
>
> Currently there is source code in lucene/tools/src (e.g. Forbidden APIs
> checker ant task).
> It would be convenient if you could download this thing in your ant build
> from ivy (especially if maybe it included our definitions .txt files as
> resources).
> In general checking for locale/charset violations in this way is a pretty
> general useful thing for a server-side app.
> Can we either release lucene-tools.jar as an artifact, or maybe alternatively
> move this somewhere else as a standalone project and suck it in ourselves?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
