These are chat archives for carymrobbins/intellij-haskforce

10th
Jun 2016
Figure I'll post new releases here as well
Andrei Dziahel
@develop7
Jun 10 2016 14:42
a-ha!
Cary Robbins
@carymrobbins
Jun 10 2016 15:03
drat, you found me!
W.P. McNeill
@wpm
Jun 10 2016 18:29
I hit an issue using Stack as a build tool on Haskforce. Am I doing something wrong, or is this a bug? http://stackoverflow.com/questions/37754956/how-do-i-set-up-intellij-to-build-haskell-projects-with-stack
W.P. McNeill
@wpm
Jun 10 2016 19:06

Here's something that I'm pretty sure is a bug. Periodically I get this error message.

Haskell Tools
           Nonzero exit status (1) from command: /Users/williammcneill/Library/Haskell/bin/stylish-haskell --version
           Process stderr: Invalid option `--version'
           Usage: stylish-haskell [FILENAME]

On the Haskell Tools I have the path set to my version of stylish-haskell (v0.5.17.0). This tool does not accept a --version argument on the command line.

It looks like we're periodically trying to run a stylish-haskell --version command in order to fill in the Version box on the Haskell Tools tab, and it's failing.

Cary Robbins
@carymrobbins
Jun 10 2016 20:39
Welcome @wpm! Thanks for bringing these up, let me check them out.
@wpm regarding your Stack issue, how did you create the hellohaskell project in haskforce?
did you use the import project wizard?
Cary Robbins
@carymrobbins
Jun 10 2016 20:48
so, it does seem that haskforce is not doing the right thing when re-building
i'll create an issue
W.P. McNeill
@wpm
Jun 10 2016 21:23
I use IntelliJ's Open option on the directory I had created with Stack. I did not use Import Project.
Cary Robbins
@carymrobbins
Jun 10 2016 21:24
@wpm ok, i see; it's best to use the import project feature to ensure things get configured correctly
W.P. McNeill
@wpm
Jun 10 2016 21:24
Let me try that real quick.
Cary Robbins
@carymrobbins
Jun 10 2016 21:25
you can use File > New > Project from existing sources
now, your building issue still persists though, i was able to reproduce that even after importing the stack project
carymrobbins/intellij-haskforce#282
W.P. McNeill
@wpm
Jun 10 2016 21:28
Started with a brand new "Hello Haskell" project: stack new hellohaskell new-template -p "category:Example"
Did IntelliJ Import Project->[choose the directory]->Create project from existing sources.
In Project Structure, no SDK is specified; it doesn't know to mark the src and test directories as type "source" and "test" respectively.
Build->Make Project doesn't do anything.
W.P. McNeill
@wpm
Jun 10 2016 21:33
Ah, I see. There's a Stack external model. I'd overlooked that.
That looks a lot better. The project SDK is set to Haskell. app, src, and test directories are marked correctly.
Make project just copies source files to production and test subdirectories of out, though. Doesn't appear to compile anything.
When I try to add a Haskell Stack Run run configuration, there's no executable to specify.
W.P. McNeill
@wpm
Jun 10 2016 21:39
(Also the stylish-haskell --version bug persists. That appears to be a separate issue.)
Cary Robbins
@carymrobbins
Jun 10 2016 21:46
@wpm - when you imported, did you select Stack as your model? See the guide
W.P. McNeill
@wpm
Jun 10 2016 21:47
Yes.
I just updated Issue #282 with the latest description of what I tried.
Cary Robbins
@carymrobbins
Jun 10 2016 21:56
ok, i'll have to dig into this more. i'll get this fixed for the next release
W.P. McNeill
@wpm
Jun 10 2016 21:57
Cool. Thanks.
Are the output files in this configuration supposed to go into out/production|test directories? I'd expect them to go under the .stack-work directory that Stack creates.
Cary Robbins
@carymrobbins
Jun 10 2016 22:00
it seems that the builder is copying the files, but i don't think it should. i think that's why we're getting the stale issue as well
so really, it should just completely delegate to slack
W.P. McNeill
@wpm
Jun 10 2016 22:01
I think so too. It's like when you use IntelliJ to build a Maven project, it doesn't use the out directory either.