lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-3006) Javadocs warnings should fail the build
Date Wed, 30 Mar 2011 17:12:05 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013548#comment-13013548
] 

Yonik Seeley commented on LUCENE-3006:
--------------------------------------

bq. We should fail the build when there are javadocs warnings

Hopefully you mean the build of javadoc should fail?  It seems like one should be able to
do a quick change of a method to try something out and still be able to do "ant test" to see
if it works w/o having to go fix all javadoc references to it first?

> Javadocs warnings should fail the build
> ---------------------------------------
>
>                 Key: LUCENE-3006
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3006
>             Project: Lucene - Java
>          Issue Type: Improvement
>    Affects Versions: 3.2, 4.0
>            Reporter: Grant Ingersoll
>
> We should fail the build when there are javadocs warnings, as this should not be the
Release Manager's job to fix all at once right before the release.
> See http://www.lucidimagination.com/search/document/14bd01e519f39aff/brainstorming_on_improving_the_release_process

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message