lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4416) disable manual invocation of internal untested ant targets
Date Sat, 22 Sep 2012 01:29:07 GMT


Robert Muir commented on LUCENE-4416:

...and all said targets we want to support should be tested from a totally 
clean checkout (ant clean clean-jars), so we know that both their 
dependencies are correct, and they resolve anything they need.

for example, today we don't really "test" javadocs, because it runs
after 'ant test' is done. 

"ant javadocs" could be and has been in the past broken standalone, where 
it doesnt properly resolve e.g. 3rd party libraries but happens to work if
its run after other things which forced lib/ to be populated.

So today this is an example of what I mean by unsupported target.

if a user sent an email tonight to the list saying "can't build javadocs for 4.0,
the ant target fails", because it didnt resolve its dependencies correctly if
you weren't previously doing other shit, i wouldn't be surprised at all. And
then we would have blocker issues/ respins / etc etc when we can avoid this with
just some jenkins testing.

> disable manual invocation of internal untested ant targets
> ----------------------------------------------------------
>                 Key: LUCENE-4416
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Task
>          Components: general/build
>            Reporter: Robert Muir
> This typically comes up at e.g. release vote time, people try to run one of the many
targets that happens to have a "description" in build.xml, but is really internal.
> e.g. if someone runs 'dist-contrib                 Make the contribs ready for distribution'
from solr, will it work? I have no idea. probably not.
> we should change some of these to be e.g. -dist-contrib or whatever, so there are no

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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message