lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-4493) Improve setup of Jenkins regarding javadocs-lint
Date Fri, 19 Oct 2012 11:42:11 GMT

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

Uwe Schindler commented on LUCENE-4493:
---------------------------------------

The current patch only works from top-level (where jenkins calls it). Inside lucene or solr,
you can still enforce execution of the linter on unsupported versions (which will break).
                
> Improve setup of Jenkins regarding javadocs-lint
> ------------------------------------------------
>
>                 Key: LUCENE-4493
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4493
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: general/build
>            Reporter: Uwe Schindler
>            Assignee: Uwe Schindler
>             Fix For: 4.1, 5.0
>
>         Attachments: LUCENE-4493.patch
>
>
> On Jenkins I have currently a complicated setup to enable Javadocs-linting depending
on the JVM. Similar to LUCENE-4488, I will move the JVM version detection to the ANT build.xml
and remove the extra config and parameter passing from Jenkins.

--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message