Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B57EE18785 for ; Tue, 26 May 2015 12:00:47 +0000 (UTC) Received: (qmail 51911 invoked by uid 500); 26 May 2015 12:00:42 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 51836 invoked by uid 500); 26 May 2015 12:00:42 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 51823 invoked by uid 99); 26 May 2015 12:00:42 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 May 2015 12:00:42 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 2D7CF182757 for ; Tue, 26 May 2015 12:00:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.899 X-Spam-Level: ** X-Spam-Status: No, score=2.899 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id FdBlifc76zH7 for ; Tue, 26 May 2015 12:00:34 +0000 (UTC) Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 5713220DC7 for ; Tue, 26 May 2015 12:00:33 +0000 (UTC) Received: by iepj10 with SMTP id j10so89811190iep.3 for ; Tue, 26 May 2015 05:00:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=TsBPGEWC/LYwqlnPwopK9nZhInuUTM22cyZrMP3Oztg=; b=clt9l7triuLa7H1Cd6JNVYq54593bdexKktUIMY28g8KqnDeNF9K40QimqIDs7tyyW oTOSoYNgBoXWfcG5Q2TtarfuqwpJQHOhZGCqeiSHxVhUKrsel1u3oDYfVYI+B6NOPbIe MOT1CxammxV6138DTnSeRDF6GBrNCGtmBdqQlF/py/c9UeT2SiOOpuvwdSlxAqHSNa5q 7EmC0tsIudnhLzJ8DPsgj7Wkk4cpBcTzjoDQmIZBdDWqFMg7N++Kpuqf7woOBQm1vIUx gaYnEcozhFBofrehqFnPJy76P/flzv6ptF/o++m3HDRvZr5CQtJsdlIN0lrSOmS+J41h RExg== MIME-Version: 1.0 X-Received: by 10.50.61.229 with SMTP id t5mr29227138igr.34.1432641632244; Tue, 26 May 2015 05:00:32 -0700 (PDT) Received: by 10.50.202.35 with HTTP; Tue, 26 May 2015 05:00:32 -0700 (PDT) In-Reply-To: References: <1432629280.2511963.278059337.5F1BE6A9@webmail.messagingengine.com> Date: Tue, 26 May 2015 13:00:32 +0100 Message-ID: Subject: Re: YAJar From: Daniel Collins To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=047d7bdca676949c5f0516fadfdc --047d7bdca676949c5f0516fadfdc Content-Type: text/plain; charset=UTF-8 I guess this is one reason why the whole WAR approach is being removed! Solr should be a black-box that you talk to, and get responses from. What it depends on and how it is deployed, should be irrelevant to you. If you are wanting to override the version of guava that Solr uses, then you'd have to rebuild Solr (can be done with maven) and manually update the pom.xml to use guava 18.0, but why would you? You need to test Solr completely (in case any guava bugs affect Solr), deal with any build issues that arise (if guava changes any APIs), and cause yourself a world of pain, for what gain? On 26 May 2015 at 11:29, Robust Links wrote: > i have custom search components. > > On Tue, May 26, 2015 at 4:34 AM, Upayavira wrote: > > > Why is your app tied that closely to Solr? I can understand if you are > > talking about SolrJ, but normal usage you use a different application in > > a different JVM from Solr. > > > > Upayavira > > > > On Tue, May 26, 2015, at 05:14 AM, Robust Links wrote: > > > I am stuck in Yet Another Jarmagedon of SOLR. this is a basic > question. i > > > noticed solr 5.0 is using guava 14.0.1. My app needs guava 18.0. What > is > > > the pattern to override a jar version uploaded into jetty? > > > > > > I am using maven, and solr is being started the old way > > > > > > java -jar start.jar > > > -Dsolr.solr.home=... > > > -Djetty.home=... > > > > > > I tried to edit jetty's start.config (then run java > > > -DSTART=/my/dir/start.config > > > -jar start.jar) but got no where... > > > > > > any help would be much appreciated > > > > > > Peyman > > > --047d7bdca676949c5f0516fadfdc--