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

GenIdea does not trigger target recomputation #352

Closed
Baccata opened this issue May 27, 2018 · 1 comment · Fixed by #616
Closed

GenIdea does not trigger target recomputation #352

Baccata opened this issue May 27, 2018 · 1 comment · Fixed by #616
Labels
solved The issue was fixed/resolved
Milestone

Comments

@Baccata
Copy link
Contributor

Baccata commented May 27, 2018

I found it whilst testing #351, and found that I had to call upon mill __.ivyDeps after adding/removing dependencies to my modules in order for the idea config to be generated appropriately.

Steps to reproduce :

  • Generate idea config from mill
  • Add/remove an arbitrary ivy dependency to one module
  • Regenerate idea config (without running any other mill command after previous step)
  • Look at cache in /out/module/ivyDeps to check whether the dependency was indeed added/removed
@raskam
Copy link

raskam commented Jul 7, 2018

In my case calling mill __.ivyDeps is not sufficient and I always have to remove out/ and .idea_modules/ directories before running mill mill.scalalib.GenIdea/idea.

I also have to reopen the project in Idea, because sometimes Idea would still use old classpath.

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.

3 participants