Return-Path: X-Original-To: apmail-uima-user-archive@www.apache.org Delivered-To: apmail-uima-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7302B108DD for ; Mon, 12 Aug 2013 10:03:00 +0000 (UTC) Received: (qmail 87453 invoked by uid 500); 12 Aug 2013 10:03:00 -0000 Delivered-To: apmail-uima-user-archive@uima.apache.org Received: (qmail 87421 invoked by uid 500); 12 Aug 2013 10:03:00 -0000 Mailing-List: contact user-help@uima.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@uima.apache.org Delivered-To: mailing list user@uima.apache.org Received: (qmail 87411 invoked by uid 99); 12 Aug 2013 10:02:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Aug 2013 10:02:59 +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 richard.eckart@gmail.com designates 209.85.215.182 as permitted sender) Received: from [209.85.215.182] (HELO mail-ea0-f182.google.com) (209.85.215.182) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Aug 2013 10:02:54 +0000 Received: by mail-ea0-f182.google.com with SMTP id o10so3337187eaj.27 for ; Mon, 12 Aug 2013 03:02:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=9How64YrYXPB+/DoHAQ8SMFKXHFwV6ljqMjAk6oDY9c=; b=VRpEGxmLHLTloKKU655J21cGLwNPxtBsSVlrIxwALc1+g62yJyBJvZ3uhNO9s6s9YS wbgOEvK28Xtn8LAswG2cyshz+QzR0q8WwyRLdnBK9B7g9pYeATvP2invStp4p5W046em rElr/j1Je+BKFz9wNez7elIUisNsbV3D6PoecSm8sy5j72SH5OAbP+7sIbmV7hPDjWB1 XLUt++qaC37yHAFlGOSUDP0Yb+518/O4Szj83OI0Q4bzms9y2yBc9ARlOHQnjCLzkwWb HA4gajyj9/VXmLU2UEtHRzA0mDUJTGpHpYqSpKWdjAO/jLUFU91ufZD+E91uTJkUVtyl sM/w== X-Received: by 10.14.205.200 with SMTP id j48mr12392794eeo.80.1376301753708; Mon, 12 Aug 2013 03:02:33 -0700 (PDT) Received: from highfire.ukp.informatik.tu-darmstadt.de (macbook-rec.ukp.informatik.tu-darmstadt.de. [130.83.167.192]) by mx.google.com with ESMTPSA id bn13sm55999434eeb.11.2013.08.12.03.02.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 12 Aug 2013 03:02:32 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: Where is uimafit? From: Richard Eckart de Castilho In-Reply-To: Date: Mon, 12 Aug 2013 12:02:26 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <78D3A665-71D6-4D1A-8B25-D08758875E6A@gmail.com> References: To: user@uima.apache.org X-Mailer: Apple Mail (2.1508) X-Virus-Checked: Checked by ClamAV on apache.org Hi, only the legacy module of uimaFIT 2.x should have a dependency on = uimaFIT 1.x. The artifact "uimafit-core" doesn't show uimafit 1.x in its dependency hierarchy. Can you check your dependency hierarchy to check where 1.x is drawn in? -- Richard Am 12.08.2013 um 11:48 schrieb Roberto Franchini : > On Tue, Jul 30, 2013 at 6:50 PM, Richard Eckart de Castilho > wrote: >> Am 30.07.2013 um 18:43 schrieb Roberto Franchini : >>=20 >>> On Tue, Jul 30, 2013 at 6:31 PM, Richard Eckart de Castilho >>> wrote: >>>=20 >>>> I cannot tell you a day, but it is not going to be long before the >>>> uimaFIT 2.0.0 release. >>>>=20 > [cut] >=20 > Hi, > today, after updating to uima 2.4.2, all my tests were broken. > It seems that uimafit (from apache) needs uimafit (google code = legacy). > Last Friday all was working right, so I guess that this dep wa added > after friday. > So I addded the dependency to uimafit(legacy) to my poms. > Is there a way to avoid this dependency request? > Thanks a lot, cheers, > FRANK > --=20 > Roberto Franchini > The impossible is inevitable. > http://www.celi.it http://www.blogmeter.it > http://github.com/celi-uim http://github.com/robfrank > Tel +39.011.562.71.15 > jabber:ro.franchini@gmail.com skype:ro.franchini tw:@robfrankie