buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert (JIRA)" <j...@apache.org>
Subject [jira] Commented: (BUILDR-483) Write specs for java commands
Date Sun, 29 Aug 2010 04:44:53 GMT

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

Alex Boisvert commented on BUILDR-483:
--------------------------------------

Yeah, it's a metaprogramming fail.  

By using Java.java.lang.String, the Java module itself gets shadowed during the execution
of the __package__ method.   This results in Java.classpath being redefined to a constant/module.

I'm going to try to clean this up.





> 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.


Mime
View raw message