lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LUCENE-2950) Modules under top-level modules/ directory should be included in lucene's build targets, e.g. 'package-tgz', 'package-tgz-src', and 'javadocs'
Date Mon, 13 Feb 2012 14:36:59 GMT

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

Robert Muir commented on LUCENE-2950:
-------------------------------------

{quote}
Maybe lucene/contrib/demo/ should be moved to modules/demo/?
{quote}

I don't remember which issue the discussions were on, but somewhere we discussed improving
the way we do this,
such that we have something like an 'examples' module, which could have various examples showing
how to use lucene/solr,
including modules (e.g. faceting). 

I think its nice to have little examples in javadocs, but at the same time it would be really
nice to have
more fleshed-out examples which can span across different use-cases, for example faceting
and grouping combined or whatever.

As a real module of course we enforce we don't break these (unlike javadocs examples: which
really i think should not
grow too large but just be easy demonstrations of the basics), and we can even have tests
that they are also
example-ing correctly (the demo stuff does have some tests).

So my first idea would be a top-level examples/... in fact I don't even think it should be
rooted underneath modules/.
Examples are for new users and they shouldn't have to dig around to find them.

                
> Modules under top-level modules/ directory should be included in lucene's build targets,
e.g. 'package-tgz', 'package-tgz-src', and 'javadocs'
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-2950
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2950
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: general/build
>    Affects Versions: 4.0
>            Reporter: Steven Rowe
>            Priority: Blocker
>             Fix For: 4.0
>
>
> Lucene's top level {{modules/}} directory is not included in the binary or source release
distribution Ant targets {{package-tgz}} and {{package-tgz-src}}, or in {{javadocs}}, in {{lucene/build.xml}}.
 (However, these targets do include Lucene contribs.)
> This issue is visible via the nightly Jenkins (formerly Hudson) job named "Lucene-trunk",
which publishes binary and source artifacts, using {{package-tgz}} and {{package-tgz-src}},
as well as javadocs using the {{javadocs}} target, all run from the top-level {{lucene/}}
directory.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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