lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4432) Make top-level default ant task print -projecthelp
Date Wed, 26 Sep 2012 01:50:07 GMT


Robert Muir commented on LUCENE-4432:

I agree: I think the ideal situation is the list of targets printed is the ones we test in
jenkins and know work (LUCENE-4416).
This way users are not confused. 

Then there is really no maintenance effort: in fact we could even imagine a future "test"
of some sort in jenkins that ensures they work (maybe AntUnit).
I especially don't want manual lists that might contain targets that no longer even exist.

Other targets like jenkins targets are really only of interest to committers: we can either
remove their description or filter on some key like "internal" or whatever.

Targets that don't ever work by themselves and are only intended to be called by other targets
should be hidden in all cases (and prefixed with a hyphen).

> Make top-level default ant task print -projecthelp
> --------------------------------------------------
>                 Key: LUCENE-4432
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: general/build
>            Reporter: Uwe Schindler
>            Assignee: Uwe Schindler
>            Priority: Trivial
>             Fix For: 4.1, 5.0
>         Attachments: LUCENE-4432.patch, LUCENE-4432.patch, LUCENE-4432.patch
> The top-level ant default task runs test, which is confusing. Instead it should alias
"-projecthelp". This is easily possible with a trick: invoke ant's main class with <java
> Solr has a good default task, it may also use the same trick, but I don't care here.
> Lucene's default task is jar-core... Maybe move the above task to common-build.xml and
let all default targets depend on "-projecthelp" task from common-build.xml?

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