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

Enabling the plugin in project definitions with settings makes run raise exception #45

Open
biboudis opened this issue Jun 4, 2015 · 3 comments

Comments

@biboudis
Copy link

biboudis commented Jun 4, 2015

I tried to use two separate project definitions n scala-streams (build file), and after switching to each project separately, invoking run produces the No main class detected. error.

@biboudis
Copy link
Author

biboudis commented Jun 4, 2015

Additionally.

If I use the code below it works. If I pass settings it doesn't.

lazy val root = project.in(file("."))
     .enablePlugins(JmhPlugin)
   //.settings(defaultSettings : _*)

@biboudis biboudis changed the title Enabling the plugin in multi-project sbt file Enabling the plugin in project definitions with settings makes run raise exception Jun 4, 2015
biboudis referenced this issue in biboudis/scala-streams Jun 4, 2015
@ktoso
Copy link
Member

ktoso commented Jun 6, 2015

Thanks for reporting, sounds a bit weird - I'll try to get some time during scaladays to have a look at it :-)
See you here (scaladays amsterdam)?

@biboudis
Copy link
Author

biboudis commented Jun 7, 2015

Thx. Unfortunately not. I won't be able to attend! :-( :-(.

I'll report back if I solve it or find the root of the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants