[
https://issues.apache.org/jira/browse/LUCENE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008405#comment-13008405
]
Robert Muir commented on LUCENE-2952:
-------------------------------------
the current situation (with the macros in the root in a common-build.xml, and
the code in dev-tools breaks the lucene build when lucene is by itself:
lucene-only releases for example, or someone just svn checking out lucene)
I don't think we should be using dev-tools for anything thats integral to the
build: the whole point of dev-tools is to be optional, maintained on as-is
basis type stuff for developers only.
So i think the code should go in test-framework or something like that instead?
and the ant logic should go in lucene's common-build, which anything can use.
> 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
> Priority: Minor
> 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: [email protected]
For additional commands, e-mail: [email protected]
