Intellij-elixir: mix --version format changed for 1.3.0+

Created on 27 Jun 2016  路  6Comments  路  Source: KronicDeth/intellij-elixir

When importing a Mix project or checking the "Elixir External Tools" settings the Version field is populated with: N/A: Error: ** (Mix) Cannot implicitly pass flags to default Mix task, please invoke instead "mix run"

The path to mix is valid: /usr/local/bin/mix and I can run it with --version in my terminal no problem.

$ /usr/local/bin/mix --version
Erlang/OTP 19 [erts-8.0] [source-6dc93c1] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]

Mix 1.3.0

Also you simply can't import the mix project unless you uncheck "Fetch dependencies". Compiling and running mix tasks doesn't seem to be a problem after the project is imported (haven't added any dependencies to see though).

I am running Ubuntu 16.04 with recommended repo installation of erlang and elixir. Both Elixir and Mix are version 1.3.0. IntelliJ is 2016.1.3. Plugin installed via JetBrains repository, version reported as 4.0.0.

Bug

Most helpful comment

@n2o you should still have the issue in 4.0.0. It wasn't fixed in 4.0.0, it was reported against 4.0.0 and closed with a commit to master. It will be in the v4.1.0 release. If you would install the canary build of v4.1.0, you can confirm it works for your before v4.1.0 is officially released.

All 6 comments

I think they changed how the mix command is wrapped again. It seems to change with every version of Elixir, so it is really hard to get a machine parseable version out of it. I can confirm I can reproduce this locally now that I'm on Elixir 1.3.0.

Same here on a linux machine with elixir 1.3.0

It looks like the change is that "Mix " is no longer the first line. In 1.3.0, they started printing the Erlang version header on the first line and "Mix " is on the last line.

I am still having this issue with Mix 1.3.1, Elixir 1.3.1 and intellij-elixir 4.0.0

@n2o you should still have the issue in 4.0.0. It wasn't fixed in 4.0.0, it was reported against 4.0.0 and closed with a commit to master. It will be in the v4.1.0 release. If you would install the canary build of v4.1.0, you can confirm it works for your before v4.1.0 is officially released.

@KronicDeth thanks, works as expected!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

merqlove picture merqlove  路  3Comments

ryancammer picture ryancammer  路  5Comments

mariuszzak picture mariuszzak  路  6Comments

joshuataylor picture joshuataylor  路  3Comments

mjadczak picture mjadczak  路  6Comments