The automated build process should publish the diff in compiler warning messages
--------------------------------------------------------------------------------

                 Key: PIG-854
                 URL: https://issues.apache.org/jira/browse/PIG-854
             Project: Pig
          Issue Type: Bug
          Components: build
    Affects Versions: 0.3.0
         Environment: Hudson
            Reporter: Santhosh Srinivasan
            Assignee: Giridharan Kesavan
             Fix For: 0.3.0


Currently, the automated build process publishes a report that captures the 
difference in the number of warning messages due to a patch from that of trunk 
However, the details of the new warning messages are not listed. For findbugs, 
a url that contains the details is published. A similar page is required for 
the compiler warning messages.

For reference, check out 

https://issues.apache.org/jira/browse/PIG-697?focusedCommentId=12720326&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12720326

The console output has the following line. Note that the details are stored on 
the build machine. Its not exported as a web page for users to figure out the 
details. At least,  I was not able to do so. It would be extremely helpful (I 
would say mandatory) to expose the details. If these details are already 
present then please point me to the right location.

{code}
[exec] /home/hudson/tools/ant/latest/bin/ant  -Djavac.args=-Xlint -Xmaxwarns 
1000 -Declipse.home=/home/nigel/tools/eclipse/latest 
-Djava5.home=/home/hudson/tools/java/latest1.5 
-Dforrest.home=/home/nigel/tools/forrest/latest -DPigPatchProcess= clean tar > 
/home/hudson/hudson-slave/workspace/Pig-Patch-minerva.apache.org/patchprocess/patchJavacWarnings.txt
 2>&1
     [exec] There appear to be 224 javac compiler warnings before the patch and 
259 javac compiler warnings after applying the patch.
{code}

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

Reply via email to