[
https://issues.apache.org/jira/browse/LUCENE-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014355#comment-13014355
]
Hoss Man commented on LUCENE-3009:
----------------------------------
I question if we really need to bother with binary lucene / module tar/zip
artifacts -- if we only had source release packages, then the build.xml files
make it clear exactly what the dpeendencies for each piece of code are.
for Solr, a large percentage of hte user base doesn't know anything about java
-- so it definitely makes sense to have artifacts with precompiled jars; but if
you're using the java libraries directly, you're a java programer, and you
should be able to run "ant compile" on a src release (or use the maven to fetch
the published jars with poms that link to the appropriate dependencies)
> binary packaging: lucene modules/contribs that depend on jars are confusing
> ----------------------------------------------------------------------------
>
> Key: LUCENE-3009
> URL: https://issues.apache.org/jira/browse/LUCENE-3009
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Robert Muir
> Fix For: 3.2, 4.0
>
>
> In the binary release, i noticed lucene contribs (for example benchmark)
> that rely upon jar files, don't include them, nor do they have a README
> telling
> you they depend upon them, nor is there any hint they actually have any
> dependencies at all!
> we should improve this either by including the jars you need or by including
> a README.txt telling you what a particular module/contrib depends upon.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
