Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error Java JDK isn't specified for module ..

See original GitHub issue

Sometimes the cabal build does not rebuild anything, and we get the above error. Here’s a console printout:

mac213:haskell-src-exts pj$ cabal build -j5
Building haskell-src-exts-1.15.0.1...
Preprocessing library haskell-src-exts-1.15.0.1...
In-place registering haskell-src-exts-1.15.0.1...
Preprocessing test suite 'test' for haskell-src-exts-1.15.0.1...
mac213:haskell-src-exts pj$

I’m not too worried about the error message, but the fact that it is signaled as an error is troublesome. Our primary mechanism for detecting errors are the return values from cabal, so maybe something is up with them.

Issue Analytics

State:
Created 9 years ago
Comments:11 (4 by maintainers)

Top GitHub Comments

1reaction

grguthriecommented, Feb 2, 2015

Yes, thank you.

Gregory Guthrie

From: Cary Robbins [mailto:notifications@github.com] Sent: Sunday, February 01, 2015 9:36 PM To: carymrobbins/intellij-haskforce Cc: Gregory Guthrie Subject: Re: [intellij-haskforce] Error Java JDK isn’t specified for module … (#31)

@grguthriehttps://github.com/grguthrie: This sounds like a slightly different topic, so let’s move the discussion over to #128 https://github.com/carymrobbins/intellij-haskforce/issues/128 to keep it relevant.

— Reply to this email directly or view it on GitHubhttps://github.com/carymrobbins/intellij-haskforce/issues/31#issuecomment-72402499.

1reaction

pjonssoncommented, Jul 15, 2014

Renaming a module, adding a new module with the same name and importing the renamed one, adding the new module to the cabal file and trying to build reproduces this.