-
Notifications
You must be signed in to change notification settings - Fork 27
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
<object> is already defined as trait ... #21
Comments
I have the same problem. Is there any known workaround? |
Explicitly disabling the javascript modules should solve that: unidocProjectFilter in ( ScalaUnidoc, unidoc ) :=
inAnyProject -- inProjects( i18nJS, schemaJS ) |
@taig Thanks. Explicitly removing JS projects worked for me. But I guess sbt-unidoc is including projects not mentioned in |
I encountered the same issue whilst using the
|
Unidoc is giving me errors when a trait or class has a companion object.
For example:
RunId is already defined as object RunId
RunId is already defined as case class RunId
The project containing the class is a scala/scala.js shared "crossProject" in a multi-project build (scala-2.11.7) .
When I remove the shared project, the unidoc problems go away.
This seems to also be a problem with the sbt gh-pages plugin.
The text was updated successfully, but these errors were encountered: