Return-Path: X-Original-To: apmail-lucene-dev-archive@www.apache.org Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 11B409C2E for ; Mon, 23 Apr 2012 18:12:00 +0000 (UTC) Received: (qmail 52714 invoked by uid 500); 23 Apr 2012 18:11:58 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 52653 invoked by uid 500); 23 Apr 2012 18:11:58 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 52616 invoked by uid 99); 23 Apr 2012 18:11:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Apr 2012 18:11:58 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rcmuir@gmail.com designates 209.85.220.176 as permitted sender) Received: from [209.85.220.176] (HELO mail-vx0-f176.google.com) (209.85.220.176) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Apr 2012 18:11:37 +0000 Received: by vcbfl17 with SMTP id fl17so12771538vcb.35 for ; Mon, 23 Apr 2012 11:10:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=uPnt3xrAAzPtn8+JlXpUJGCIARVbvB3Ia8JwP28Hfgc=; b=cJmjrA+Ov4NvMA270uve3JQZkx/NlfehrKIJaCjjoa03JpNt4P1DJytgt4068HkDJz NaPNNchKBaOUBkW0Qgkh6ynMAMWz7nah7UAPWjZHCnynhjof6lQn1aNxNCDzH/MclhnH m129ntNw9Iop6KfgF8FMMDHIv9d0CZnnwqit+AAuw4K0p4Tbu7qA1GUdRuwpAry86IoD ks5myyiVu/ljYKmPyMd9fZ8hETNJP63zsRLIIlp4T0at9k5xgX/iFyHP1FGT9DakbGWQ w33Ultc15CFWvr7mP2HjAWM4/nB+r3fGwhsIKkRN8vxooVPzr9rezeTSLzDEwXqoS92k E4kQ== Received: by 10.220.240.20 with SMTP id ky20mr4526317vcb.27.1335204659507; Mon, 23 Apr 2012 11:10:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.220.48.72 with HTTP; Mon, 23 Apr 2012 11:10:39 -0700 (PDT) In-Reply-To: References: <6C78E97C707B5B4C8CC61D44F87545861DC832@SUEX10-mbx-03.ad.syr.edu> <-4512779896607688392@unknownmsgid> <9890C7A2-7C3C-4919-9D71-441AB7327500@gmail.com> From: Robert Muir Date: Mon, 23 Apr 2012 14:10:39 -0400 Message-ID: Subject: Re: [DISCUSS] Build/deploy Maven artifacts outside of Lucene/Solr To: dev@lucene.apache.org Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On Mon, Apr 23, 2012 at 2:07 PM, Benson Margulies wrote: >> >> How do we handle situations like >> https://issues.apache.org/jira/browse/XERCESJ-1257 (open for 5 years, >> still not incorporated in a release), without doing hackish things >> (releasing someone elses code, sucking their entire codebase into >> ours), or relying upon Uwe Schindler to come up with some clever >> workaround? > > As far as I can tell, you have exactly the same issues solving this > issue with and without Maven. > I don't think thats really the case at all. If i want to release a patched jar with ivy its pretty trivial. I simply make a project in github or google code with a build.xml that downloads their code, patches it, and produces the patched result. its still an open source project: its basically a fork. I put the binaries i generate under Downloads and point ivy directly at that jar. Done. How to do this with maven? -- lucidimagination.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org