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

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

Github user lewismc commented on a diff in the pull request:

    https://github.com/apache/incubator-joshua/pull/32#discussion_r72566150
  
    --- Diff: src/main/java/org/apache/joshua/decoder/Decoder.java ---
    @@ -496,7 +496,7 @@ public Decoder initialize(String configFile) {
               errMsg.append("FATAL: Invalid feature weight line found in 
config file.\n");
               errMsg.append(String.format("The line was '%s'\n", pairStr));
               errMsg.append("You might be using an old version of the config 
file that is no longer supported\n");
    -          errMsg.append("Check joshua-decoder.org or email 
joshua_supp...@googlegroups.com for help\n");
    +          errMsg.append("Check joshua.apache.org or email 
joshua_supp...@googlegroups.com for help\n");
    --- End diff --
    
    The email should be d...@joshua.apache.org


> Remove presence of all joshua-decoder.org links in codebase
> -----------------------------------------------------------
>
>                 Key: JOSHUA-286
>                 URL: https://issues.apache.org/jira/browse/JOSHUA-286
>             Project: Joshua
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 6.0.5
>            Reporter: Lewis John McGibbney
>             Fix For: 6.1
>
>
> Right now, joshua-decoder.org exists in the following files, we should remove 
> it and replace it with joshua.apache.org
> {code}
> lmcgibbn@LMC-032857 /usr/local/incubator-joshua(JOSHUA-283) $ grep -lr 
> "joshua-decoder.org" .
> ./.gitignore
> ./CHANGELOG
> ./doc/mainpage.md
> ./scripts/support/make-release.sh
> ./src/main/java/org/apache/joshua/decoder/Decoder.java
> ./src/main/java/org/apache/joshua/decoder/ff/lm/KenLM.java
> {code}



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

Reply via email to