[ 
https://issues.apache.org/jira/browse/JOSHUA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304048#comment-15304048
 ] 

ASF GitHub Bot commented on JOSHUA-252:
---------------------------------------

Github user mjpost commented on the pull request:

    https://github.com/apache/incubator-joshua/pull/12#issuecomment-222143162
  
    Okay, can't stop scratching this itch. 
    
    On even further investigation, with some System.err.println()s, I 
discovered that the properties file isn't getting loaded correctly. 
Consequently, isDebugEnabled() is always returning true, but the logging 
statements are not printed anywhere visible. So the work is getting triggered, 
and is just not seen, and that is the problem.
    
    I've pushed up the merge. Can you folks take care of making sure that the 
logger file is running correctly? You can test this by running
    
        cd $JOSHUA/src/test/resources/bn-en/hiero/
        time ./test.sh
    
    Depending on your hardware, of course, that should run in just a few 
seconds tops.
    
    Incidentally, there are at least two other problems I am hoping you can 
help address?
    
    -  I see how to build a big tarball and run Maven that way, but that's a 
pain for development, since you have to incur the time of rebuilding the 
tarball. Is there a way to just run against the files in target/classes 
directly? I've tried this, but the problem is that the jar dependencies don't 
seem to get downloaded anywhere. 
    
    -  Your response might be, "actually, you just have to regenerated the 
tarball, that's the proper way to do things." In which case, can you describe 
how to make eclipse do this? Right now, when I'm developing, eclipse is always 
compiling files, so you can just switch over and test right away. It's a small 
but significant paint to have to type "(cd $JOSHUA; mvn compile assembly:single 
install"
    
    -  I really like being able to use the `-v` (verbosity) flag to Joshua, 
which sets the debugging level. This is much simpler than changing a properties 
file and linking to that from the command line. Is it possible to set the log4j 
debug level programmatically based on the value of -v? We could do
    
           -v 0 = OFF
           -v 1 = INFO
           -v 2 = DEBUG
    
       Or I would be okay to switch to those values directly (e.g., "-v OFF"). 
But the former seems more Unix-like.
    
    Thanks again for all your work on this!
    
    matt
    



> Make it possible to use Maven to build Joshua
> ---------------------------------------------
>
>                 Key: JOSHUA-252
>                 URL: https://issues.apache.org/jira/browse/JOSHUA-252
>             Project: Joshua
>          Issue Type: Improvement
>          Components: build
>            Reporter: Tommaso Teofili
>            Assignee: Tommaso Teofili
>             Fix For: 6.1
>
>
> As per discussion on the dev@ list for now Ant is the official build tool for 
> Joshua however we would like to possibly switch to Maven if / when someone is 
> able to do so.
> Assigning to me for now as I could be able to look into this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to