Code generation fails with NPE on Windows & OSX about eclipse-collections HOT 4 CLOSED

Thanks for reporting this. Could you please let us know what version of JDK/Maven are you building with? I build in Mac OSX (El Capitan) and cannot reproduce this.

As for the referenced issue, I see the NullPointerException is thrown in different place in the stack trace, so I suspect it is a different problem.

One another thing, could you please confirm if you made any changes to eclipse-collections-code-generator/src/main/resources/impl/block/factory/primitivePredicates.stg? The error suggests something went wrong while parsing this file.

from eclipse-collections.

Hi.

No, I had not modified anything because I was simply trying to create the source jars at the time.

Here's my OSX mvn --version output:

Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T11:29:23-06:00)
Maven home: /opt/local/share/java/maven32
Java version: 1.8.0_51, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_51.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"

On Windows:

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T10:41:47-06:00)
Maven home: C:\Program Files\Java\apache-maven-3.3.9
Java version: 1.8.0_92, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_92\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"

You could be correct that this issue is unrelated to file system case sensitivity, but you should double check that your FS is indeed case insensitive before ruling out this out. In particular, a networked FS may be case sensitive and OSX's hfs can be configured case sensitive.

from eclipse-collections.

Well this is interesting. The build succeeds in a ram disk on the same OSX machine, using the exact same JDK and maven, regardless of whether the ram disk is configured case sensitive or case insensitive. But the build still has the same failure when run on the main file system, even when I've freshly cloned the git repo. I also tried mvn clean and rm -rf ~/.m2, but each build behaves consistently.

from eclipse-collections.

I've confirmed this is caused by something on my local system. The build is fine outside some directories, but always fails in the same way in certain subdirectories.

from eclipse-collections.