lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-2974) the hudson nightly for lucene should check out lucene by itself
Date Fri, 14 Sep 2012 16:42:07 GMT

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

Steven Rowe commented on LUCENE-2974:
-------------------------------------

http://builds.flonkings.com/ currently runs Lucene-only builds, but it checks out the top-level.
 Maybe it could simply be switched to checking out {{lucene/}} only?

bq. But I think we should try to test what we actually release. Maybe the nightly build should
even build release artifacts, untar them, and run javadocs/tests this way?

This is already happening, right?
                
> the hudson nightly for lucene should check out lucene by itself
> ---------------------------------------------------------------
>
>                 Key: LUCENE-2974
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2974
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: general/build
>            Reporter: Robert Muir
>             Fix For: 4.1
>
>
> Currently its too easy to break the lucene-only packaging and build.
> the hudson job for lucene should check out lucene by itself, this will
> prevent it from being broken.

--
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