From kato-dev-return-182-apmail-incubator-kato-dev-archive=incubator.apache.org@incubator.apache.org Sat Jun 27 20:58:52 2009 Return-Path: Delivered-To: apmail-incubator-kato-dev-archive@minotaur.apache.org Received: (qmail 9466 invoked from network); 27 Jun 2009 20:58:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Jun 2009 20:58:51 -0000 Received: (qmail 85672 invoked by uid 500); 27 Jun 2009 20:59:02 -0000 Delivered-To: apmail-incubator-kato-dev-archive@incubator.apache.org Received: (qmail 85642 invoked by uid 500); 27 Jun 2009 20:59:02 -0000 Mailing-List: contact kato-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: kato-dev@incubator.apache.org Delivered-To: mailing list kato-dev@incubator.apache.org Received: (qmail 85632 invoked by uid 99); 27 Jun 2009 20:59:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jun 2009 20:59:02 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of spoole167@googlemail.com designates 209.85.219.221 as permitted sender) Received: from [209.85.219.221] (HELO mail-ew0-f221.google.com) (209.85.219.221) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jun 2009 20:58:50 +0000 Received: by ewy21 with SMTP id 21so2191833ewy.12 for ; Sat, 27 Jun 2009 13:58:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=/9ouewbBUOUosSTMuKNaZtw6PMErON0yojW9X8F6TOY=; b=WqYFv0NEvgk2PqFP/YKibzJ9g7LEsIQFrQqEyUakha1HAQ9CPfo4YpLkFPQCMX+x3t u7JwfhA+Yi8WqmrLxdvQrqdC1M52LRh6oowPxV8zQZnho4AYHQDsO2SJlc7jY3w+OtnA UAYhku2ghptL4blvSLhXrpudZKChpi+RBUH0Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ET2z5MqLPeuPykNGooj6ZPL63EgOjSRTJvqzfUdTiHaYnHZTkwt99yKJ3P80LWvz1E jYeNAYi6bHA6S6rqu/QLORES7N8T0WmX6Y8cgk5b5b2v7Kf8UJb7XGjGJgvuGSKe+okh MHksM80W+3Rvdel9yyeOgsc+hpHsHYBfvPVm0= MIME-Version: 1.0 Received: by 10.210.51.10 with SMTP id y10mr1938795eby.76.1246136310304; Sat, 27 Jun 2009 13:58:30 -0700 (PDT) In-Reply-To: References: Date: Sat, 27 Jun 2009 21:58:30 +0100 Message-ID: Subject: Re: Building the eclipse projects From: Steve Poole To: kato-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=0015174bedce1e1250046d5ab82c X-Virus-Checked: Checked by ClamAV on apache.org --0015174bedce1e1250046d5ab82c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I fixed this by getting the maven build to tell me the location of the API dependency and then using an Ant script to copy the directory or unpack a jar as required. Bit of a hack simple. On Thu, Jun 25, 2009 at 5:03 PM, Steve Poole wrote: > I'm hitting a weird problem when building the eclipse projects , If I > build outside eclipse using "mvn install" everything works fine. But if I > build by using the eclipse maven support I hit a problem with when the API > project (kato.api.eclipse.plugin) is built. > > It fails, it seems, because the copy dependencies maven plugin is > expecting to find a jar file and finds a directory instead. It looks like > this on windows. > > 25/06/09 16:20:48 BST: [INFO] Copying classes to C:\Documents and > Settings\spoole\workspace\kato.eclipse\plugins\kato.api.plugin\target\dependency\classes > 25/06/09 16:20:48 BST: Build errors for kato.api.eclipse.plugin; > org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in > the plugin manager executing goal > 'org.apache.maven.plugins:maven-dependency-plugin:2.0:copy-dependencies': > Mojo execution failed. > > In the maven project pom its configured as > > > org.apache.maven.plugins > maven-dependency-plugin > > > copy-dependencies > validate > > copy-dependencies > > > lib > false > true > true > > > > > > > I can't find any solution to this on the net - so I'm left with having to > fix this either by replacing the maven plugin with some clunky Ant stuff, > or by doing something clever. > > My latest thought is to use svn externals as a way to link the source code > of the API project into the eclipse project. Since the only reason for the > eclipse API project is to expose the Kato API to eclipse plugins it sort of > makes sense. > > Anyway - thought I'd mention it to see if anyone has fixed this or has an > opinion > > > Cheers > > Steve > > --0015174bedce1e1250046d5ab82c--