[
https://issues.apache.org/jira/browse/LUCENE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reopened LUCENE-2952:
-----------------------------------
The nightly builds now fail because clover breaks because the checker classes
are in test-framework, and clover is not available there. The checker classes
should be build through compile-tools task (without clover) and then used.
In my opinion, this license-checker main() should be in /lucene/dev/src/tools
not /lucene/dev/src/test-framework. We already have this folder to e.g. rebuild
the files of StandardTokenizer and so on.
Also executing this in clover would create code coverage which is not really
runtime-created.
A quick fix would be to disable the license checker if run.clover=1, but I
don't like it how it is now.
> Make license checking/maintenance easier/automated
> --------------------------------------------------
>
> Key: LUCENE-2952
> URL: https://issues.apache.org/jira/browse/LUCENE-2952
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Grant Ingersoll
> Assignee: Grant Ingersoll
> Priority: Minor
> Fix For: 3.2, 4.0
>
> Attachments: LUCENE-2952.patch, LUCENE-2952.patch, LUCENE-2952.patch,
> LUCENE-2952.patch, LUCENE-2952.patch, LUCENE-2952.patch, LUCENE-2952.patch
>
>
> Instead of waiting until release to check licenses are valid, we should make
> it a part of our build process to ensure that all dependencies have proper
> licenses, etc.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
