[
https://issues.apache.org/jira/browse/LUCENE-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242180#comment-13242180
]
Chris Male commented on LUCENE-3930:
------------------------------------
The only real remaining issue here is how to handle the langdetect jar in
Solr's langid contrib. The solution in ivy works fine (specifying the location
of the jar) except I don't think you can do the same thing in Maven, which
stumps our Maven releases a little. For some people that isn't an issue, but
I'd like to see it solved. Does anybody know of how to do something similar in
Maven?
The other alternative is to get the language-detection project to make an
actual release. It is possible to simulate a repo in a googlecode project.
But I'm unsure how to go about getting the project maintainer to do that?
> nuke jars from source tree and use ivy
> --------------------------------------
>
> Key: LUCENE-3930
> URL: https://issues.apache.org/jira/browse/LUCENE-3930
> Project: Lucene - Java
> Issue Type: Task
> Components: general/build
> Reporter: Robert Muir
> Assignee: Robert Muir
> Priority: Blocker
> Fix For: 3.6
>
> Attachments: LUCENE-3930-skip-sources-javadoc.patch,
> LUCENE-3930-solr-example.patch, LUCENE-3930-solr-example.patch,
> LUCENE-3930.patch, LUCENE-3930.patch, LUCENE-3930.patch,
> LUCENE-3930__ivy_bootstrap_target.patch, ant_-verbose_clean_test.out.txt,
> noggit-commons-csv.patch, patch-jetty-build.patch
>
>
> As mentioned on the ML thread: "switch jars to ivy mechanism?".
--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
