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 16:07:01 GMT

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

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

{quote}
I think you're thinking of LUCENE-3550.
{quote}

That's the one, though it does seem to hint at examples being within each module.

I am proposing instead that we have examples that can show how the different parts and pieces
work together,
"big picture", which I think is important as 4.0 is already a more modular architecture than
3.x

{quote}
Interesting - I assume, though, that solr/example/ would stay where it is?
{quote}

I have no opinion for now. I'd say leave it for the time being, there is already lots of documentation
and stuff about how to use this in the place where it is now. I also think this is less of
an 'example'
and more of a 'defaults'... whenever I say this people argue with me, but lets face reality
:)

But from the lucene side, as mentioned on LUCENE-3550, lots of APIs have changed, things have
been modularized
and refactored and moved around, and when lucene 4.x comes out (unless people are working
really hard in secret
on this and I don't know about it), we won't have any "lucene in action" book for 4.x (to
my knowledge) to shove 
the responsibility onto... I sorta feel thats how users have dealt with this lack of documentation
in the past.

Examples are like the least-maintained part of lucene, so I dont have any solutions for 'hey
how do we get people
excited about writing some nice clean examples', but it would be good to at least set things
up so people can
do this easily without refactoring the build system.

                
> 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