Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mill.scalalib.GenIdea/idea failes when no ScalaModules defined #532

Closed
lefou opened this issue Jan 25, 2019 · 1 comment · Fixed by #616
Closed

mill.scalalib.GenIdea/idea failes when no ScalaModules defined #532

lefou opened this issue Jan 25, 2019 · 1 comment · Fixed by #616
Labels
solved The issue was fixed/resolved
Milestone

Comments

@lefou
Copy link
Member

lefou commented Jan 25, 2019

The build project has no ScalaModule defined, but nevertheless using IntelliJ Idea to edit the build.sc makes still sence. Generating the idea project with mill -i mill.scalalib.GenIdea/idea fails with the following output:

[1/1] mill.scalalib.GenIdea.idea 
1 targets failed
mill.scalalib.GenIdea.idea scala.MatchError: Failure(
Resolution failed for 4 modules:
--------------------------------------------
  com.lihaoyi:mill-scalajslib_2.12:0.3.5 

  com.lihaoyi:mill-main-core_2.12:0.3.5 

  com.lihaoyi:mill-main-moduledefs_2.12:0.3.5 

  com.lihaoyi:mill-scalalib_2.12:0.3.5 

,None) (of class mill.eval.Result$Failure)
    mill.scalalib.GenIdeaImpl$.xmlFileLayout(GenIdeaImpl.scala:77)
    mill.scalalib.GenIdeaImpl$.apply(GenIdeaImpl.scala:45)
    mill.scalalib.GenIdea$.$anonfun$idea$2(GenIdeaImpl.scala:21)
    scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:12)
@ghost
Copy link

ghost commented Mar 21, 2019

The problem seems to be that the GenIdea module uses the repositories specified in the Scala and Java modules to resolve Mill modules. Would it make sense to use the default repos instead?

lefou pushed a commit that referenced this issue Jun 28, 2019
@lefou lefou added this to the after-0.4.1 milestone Jun 28, 2019
@lefou lefou added the solved The issue was fixed/resolved label Jul 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solved The issue was fixed/resolved
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant