Return-Path: X-Original-To: apmail-incubator-jspwiki-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-jspwiki-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 72C369825 for ; Wed, 4 Jul 2012 20:25:28 +0000 (UTC) Received: (qmail 76861 invoked by uid 500); 4 Jul 2012 20:25:28 -0000 Delivered-To: apmail-incubator-jspwiki-dev-archive@incubator.apache.org Received: (qmail 76804 invoked by uid 500); 4 Jul 2012 20:25:28 -0000 Mailing-List: contact jspwiki-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jspwiki-dev@incubator.apache.org Delivered-To: mailing list jspwiki-dev@incubator.apache.org Received: (qmail 76795 invoked by uid 99); 4 Jul 2012 20:25:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jul 2012 20:25:28 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of juanpablo.santos@gmail.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-ob0-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jul 2012 20:25:24 +0000 Received: by obcva7 with SMTP id va7so11977770obc.6 for ; Wed, 04 Jul 2012 13:25:03 -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=L3VKU8X/f/wAzfUV767DNI/o7ZHxJ5P3BL8fdwz4Saw=; b=bW0nuwqrHQRKQ7/GUQnvC/yG0nuVmhyaNAWgvksV+E3GL/nvUAPGNkzCSgW5RSKh9P cNaXwWHOVJ+aDFjMm+Fv2bLYO1oWXfKBRzyA4qUSLRdX8owPt5CfPhAcYbFFFteQdehq 9w9WsIu1qRqAbqj/F4qQqxnZdw1B6pcJ38ioTLL5gf/M+i0te++MmPWnMB8gwqWYDXys wgA3QJh+zzi2lg6F88Apq6V4LOUBA5NYkS0EHIK88T8C3x6Dm4p/mYqnoqjb7lJfwmHW SUmd1nOb1eBQuxWjmkDBiVM8Cb2C0BBThll+NExlRt3lzH0Y/xyZy/jqjTzkJ/utmM90 9L+A== MIME-Version: 1.0 Received: by 10.182.174.68 with SMTP id bq4mr18653326obc.53.1341433503325; Wed, 04 Jul 2012 13:25:03 -0700 (PDT) Received: by 10.76.99.239 with HTTP; Wed, 4 Jul 2012 13:25:03 -0700 (PDT) In-Reply-To: <0233F718-7B4D-4F37-ABFB-697C2A88DE32@ecyrd.com> References: <2723836.160.1340789528121.JavaMail.florian@ultron> <0233F718-7B4D-4F37-ABFB-697C2A88DE32@ecyrd.com> Date: Wed, 4 Jul 2012 22:25:03 +0200 Message-ID: Subject: Re: code coverage and sonar integration From: =?UTF-8?Q?Juan_Pablo_Santos_Rodr=C3=ADguez?= To: jspwiki-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=e89a8f50311a749f2204c406d392 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f50311a749f2204c406d392 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, just committed it a few moments ago: ant [clean] coverage-reports generates cobertura reports in ./tests/build/cobertura ant [clean] sonar to connect to a default sonar installation (i.e., running at localhost:9000, using derby database) non AL-dependencies are downloaded via maven-ant-tasks to ./tests/build/libs-opt br, juan pablo On Thu, Jun 28, 2012 at 7:59 PM, Janne Jalkanen w= rote: > > What we're pretty successfully doing right now at my current work is that > we use Maven for dependency management (and Eclipse integration), but Ant > for scripting, building, etc. We just dumped Ivy because it's hard to > configure correctly and has inferior IDE integration. > > Check out ant-maven-tasks; it's pretty useful. > > /Janne > > On Jun 27, 2012, at 12:33 , Florian Holeczek wrote: > > > Hi Juan Pablo and Janne, > > > > improving our build management is something I've had in mind for a long > time already. Just having a look at the output of some Ant visualization > tool is demonstrating that there is much room for improvement :-) > > I remember a discussion with Janne on this. He wasn't really in favour > of Maven, and, after I've personally seen some not that huge project > suffering from Maven's complexity, I tend to share his opinion. > > IMO, JSPWiki has definitely grown too big for Ant, but it's ways too > small for Maven. I think Ivy might be a small partial improvement regardi= ng > dependency management, but the most promising candidate to me is Gradle [= 1]. > > Heard of it already? WDYT? > > > > Regards > > Florian > > > > [1] http://www.gradle.org/ > > > > > > ----- Urspr=C3=BCngliche Mail ----- > > Von: "Juan Pablo Santos Rodr=C3=ADguez" > > An: jspwiki-dev@incubator.apache.org > > Gesendet: Mittwoch, 27. Juni 2012 10:49:37 > > Betreff: Re: code coverage and sonar integration > > > > hmmm.., then I'd rather go adding Ivy support to manage all dependencie= s > > (or even to a maven-based build). Will begin on this as soon as I can. > Thx > > for the info on this :-) > > > > > > regards, > > jp > > > > On Wed, Jun 27, 2012 at 9:18 AM, Janne Jalkanen < > janne.jalkanen@ecyrd.com>wrote: > > > >> > >> Nope. > >> > >> But what you can do is to make an ant task which downloads Cobertura a= nd > >> the relevant JARs when you run "ant coverage-tests" or whatever. > >> > >> /Janne > >> > >> On 27 Jun 2012, at 01:11, Juan Pablo Santos Rodr=C3=ADguez wrote: > >> > >>> Hi again, > >>> > >>> I was curious and have added the needed jars and the related ant task > to > >>> see how JSPWiki is performing in terms of test coverage. I was about = to > >>> commit the changes, but I'm not very sure if we can commit the > Cobertura > >>> jar, as it is not clear to me if their license is AL-compatible or no= t > >> (by > >>> the way, if anybody is curious, I've uploaded the reports to [1]). > >>> > >>> Cobertura ant tasks are AL-licensed [2], but cobertura.jar contains > both > >>> ant-tasks and Cobertura itself, which is GPL. Is it OK to commit this > jar > >>> in tests/lib? Regarding asm-3.0.jar and asm-tree-3.0.jar, they seem O= K > >> [3]. > >>> > >>> Also, following up with the coverage reports, I've also made the > >> appropiate > >>> task to let Sonar gather some statistics from JSPWiki. The point is, > >> Sonar > >>> is LGPL'ed, which means we can't add the Sonar ant tasks to the > project, > >>> so, does it make sense to commit these build.xml changes? As I have > them > >>> now, they assume that the Sonar ant tasks are placed inside > $ANT_HOME/lib > >>> > >>> > >>> regards, > >>> juan pablo > >>> > >>> > >>> [1]: http://people.apache.org/~juanpablo/coverage_2.9.0-incubating-3 > >>> [2]: http://cobertura.sourceforge.net/license.html > >>> [3]: http://asm.ow2.org/license.html > >> > >> > > --e89a8f50311a749f2204c406d392--