Mailing-List: contact commits-help@buildr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@buildr.apache.org
Message-ID: <30263098.56421283062373721.JavaMail.jira@thor>
Date: Sun, 29 Aug 2010 02:12:53 -0400 (EDT)
From: "Hudson (JIRA)" <jira@apache.org>
To: buildr-commits@incubator.apache.org
Subject: [jira] Commented: (BUILDR-483) Write specs for java commands
In-Reply-To: <29266567.465501279582371056.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/BUILDR-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903934#action_12903934 ] 

Hudson commented on BUILDR-483:
-------------------------------

Integrated in Buildr-ci-build #110 (See [https://hudson.apache.org/hudson/job/Buildr-ci-build/110/])
    partial fix for BUILDR-483, with specs for javac
BUILDR-483: Write specs for java commands (Antoine Toulme)


> Write specs for java commands
> -----------------------------
>
>                 Key: BUILDR-483
>                 URL: https://issues.apache.org/jira/browse/BUILDR-483
>             Project: Buildr
>          Issue Type: Task
>          Components: Core features
>    Affects Versions: 1.4.1
>            Reporter: Antoine Toulme
>             Fix For: 1.4.2
>
>         Attachments: patch_javac_BUILDR-483.patch
>
>
> The java commands have no coverage.
> They are front and central to Buildr. They need to start having coverage as people on Windows tend to suffer from them.
> Also, the javac command should use the code from the external.rb file to avoid long command lines. The code between those two files shoud be merged.
> Here is the current coverage:
> http://buildr.apache.org/coverage/lib-buildr-java-commands_rb.html

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.