-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
=pro run multi-jvm tests when validating pr #17532
Conversation
Test FAILed. |
Test FAILed. |
|
||
implicit class RichBoolean(val b: Boolean) extends AnyVal { | ||
final def apply[A](a: => A): Option[A] = if (b) Some(a) else None | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to avoid such very broad conversions (on primitive type, providing an apply()), or if really needed define very near it's use-site.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It reduces boilerplate when used together with boolean flags that we have quite a few. Therefore it is not possible to add it to a narrower scope.
For example previously we had:
if (CliOption.sbtLogNoFormat) List("-Dakka.test.nocolor=true") else Nil
And now we have instead:
CliOption.sbtLogNoFormat("-Dakka.test.nocolor=true").toList
WDYT?
Test FAILed. |
val validateDiagrams = settingKey[Boolean]("Validate generated scaladoc diagrams") | ||
|
||
val javadocSettings = if (CliOption.genjavadocEnabled) Seq( | ||
scalacOptions in Compile += "-P:genjavadoc:fabricateParams=true", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be the failure culprit:
[error] bad option: -P:genjavadoc:fabricateParams=true
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the same setting was used previously... so what's different here hm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@2m no need for genjavadocExtraSettings
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
genjavadocExtraSettings
was used before as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, the comment was supposed to be "need for genjavadocExtraSettings
" it was there but now it's gone
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(does not solve the bad option problem we're having though, so maybe a non issue)
Test PASSed. |
LGTM, one nitpick about moving javadoc things out of the scaladoc plugin. |
Made dynamic task execution work with a bit of magic from http://stackoverflow.com/questions/24615783/combining-taskdyn-and-tags-in-sbt thanks to @jsuereth |
Test PASSed. |
Test PASSed. |
LGTM |
1 similar comment
LGTM |
Added one last commit which removed
when compiling akka build. Validated again that no additional tasks are run when project validation is skipped. Will squash and merge after successful validation. |
Test FAILed. |
* addunidoc task via an AutoPlugin that depends on PrValidation and Unidoc autoplugins * separate cli option logic to a case class * remove autoplugin for root project
Test PASSed. |
=pro run multi-jvm tests when validating pr
The essence of this is one more autoplugin
MultiNodeWithPrValidation
that gets triggered on a project which has bothMultiNode
andValidatePullRequest
autoplugins enabled.