You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by GitBox <gi...@apache.org> on 2019/12/17 22:46:13 UTC

[GitHub] [maven-compiler-plugin] hohwille edited a comment on issue #28: MCOMPILER-359 - Fix for NPE

hohwille edited a comment on issue #28: MCOMPILER-359 - Fix for NPE
URL: https://github.com/apache/maven-compiler-plugin/pull/28#issuecomment-566783173
 
 
   good to know that CI is present. Thanks for the link. You can even integrate Jenkins with github, though...
   
   > Can you expand the integrationtest of src/it/MCOMPILER-360 ?
   
   To be honest. I do not know how. My problem is that I would like to figure out the actual exception that was caused. Due to this NPE that is triggered instead, I am unable to see what is going wrong as the important stacktrace is finally lost. As I can only reproduce the error in travis-ci and not locally, I am completely lost. Here is my travis log:
   https://api.travis-ci.org/v3/job/626312654/log.txt
   
   It would be awesome to figure out what is really going wrong. However, I fear that it will take ages till a new version of maven-compiler-plugin is released where the NPE is fixed (no offence, we are all very busy coders - I myself also would urgendly need to implement various fixes for flatten-maven-plugin but can not find the time) and I have upgraded to that version so I can see what the actual error is. Any idea how to speed up this analysis?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services