sbt / sbt/sbt-eclipse

add recommendations for multiprojects and crossprojects

Open
#302 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
712
Forks
163
PR merge metrics
No merged PRs in 30d

Description

I am having huge issues with cross ScalaJVM/JS projects and projects with macroses. By experimenting I managed to figure out that without

 EclipseKeys.useProjectId := true,
  EclipseKeys.skipParents := false,

It cannot even import crossprojects. But even after importing I get a huge number (400+) compile errors for totally valid (in sbt console and in Intellij projects) =(

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named. Start by reproducing a cross ScalaJVM/JS project and a project using macroses with EclipseKeys.useProjectId := true and EclipseKeys.skipParents := false, then compare the generated Eclipse project with sbt console and IntelliJ results. Done means the crossproject imports without hundreds of compile errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.