Closed victornoel closed 7 years ago
The quick fix I applied was to add a null check at Project.Java line 531:
if( projectProfiles != null && dependencyMap != null)
Hi thanks for your fix. I guess it fixes the npe but I would like to investigate more about why this happens. Is it just me forgetting to check for null (which I doubt because I already analysed lots of projects with pomexplorer) or is it a more architectural problem which should be fixed at its source... Anyway I'm glad the fix makes it for you. I should have time to go into that next weeks. This days I just need to rest.... Thanks
Arnaud
Le mer. 28 sept. 2016 17:07, gcalis notifications@github.com a écrit :
The quick fix I applied was to add a null check at Project.Java line 531: if( projectProfiles != null && dependencyMap != null)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ltearno/pom-explorer/issues/24#issuecomment-250195620, or mute the thread https://github.com/notifications/unsubscribe-auth/AALqXXACwyB-dFUWBrsdIiKi99hToKNWks5quoLGgaJpZM4KFBMy .
The thing is, from what I've seen of the project, there is nowhere where this method is called with a non-null dependencyMap! But I may have missed something ^^
Anyway, as you check in the code just above if the dependencyMap is null, there should also be a check before doing the collections maps and filters... there is an inconsistency somewhere in this method :)
Hi, I'm seeing the exact same issue and can confirm that the fix @gcalis suggested solves the issue for me.
Thanks to you both, it's already a long time ago, and i could not find any time before today to re-open the project. Your commit fixes the problem, thank you!
Hi, when doing analysis I get this error:
I ran it with the debugger and apparently dependencyMap is null!