[
https://issues.apache.org/jira/browse/LUCENE-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501326
]
Sami Siren commented on LUCENE-622:
-----------------------------------
thanks Hoss for the feedback in general. I am now a bit confused - is there a
consensus how to proceed with this (in other words should I change things as
suggested or are we going to take the maven approach to this?)
> some other questions:
> a) it doesn't seem like all contribs are accounted for ... were some
> excluded intentionally?
Some were excluded intentionally as their dependencies are not available in
public repos (gdata, db), some were just excluded(javascript, lucli, ant)
> (my worry is that overtime a contrib
> changes, it's POM doesn't get updated, and we have a "release" in which the
> maven artifacts are incorrect (which
> in my opinion is worse then not having any maven artifacts at all)
for 1.9.1 the jar itself was faulty http://jira.codehaus.org/browse/MEV-449
> Provide More of Lucene For Maven
> --------------------------------
>
> Key: LUCENE-622
> URL: https://issues.apache.org/jira/browse/LUCENE-622
> Project: Lucene - Java
> Issue Type: Task
> Affects Versions: 2.0.0
> Reporter: Stephen Duncan Jr
> Assignee: Michael Busch
> Fix For: 2.2
>
> Attachments: lucene-622.txt, lucene-core.pom,
> lucene-highlighter-2.0.0.pom, lucene-maven.patch, lucene-maven.tar.bz2
>
>
> Please provide javadoc & source jars for lucene-core. Also, please provide
> the rest of lucene (the jars inside of "contrib" in the download bundle) if
> possible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
