sbt / sbt/sbt-eclipse

lib dependencies aren't visible in eclipse project

Open
#126 1 comment 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

If the project definition is as follows:

 lazy val project = Project(id = "core-project",
    base = file("modules/core-project")
  )

and the core-project has unmanaged libraries in it's related lib directory, then the .classpath file will contain incorrect library entries related to this unmanaged libraries.

The project's file structure looks like:

modules\core-project\src\<some sources>
project\Build.scala
project\plugins.sbt

The .classpath looks like:

<classpath>
  <classpathentry output="target\scala-2.9.1\classes" path="src\main\scala" kind="src"></classpathentry>
  <classpathentry output="target\scala-2.9.1\classes" path="src\main\java" kind="src"></classpathentry>
  <classpathentry output="target\scala-2.9.1\test-classes" path="src\test\scala" kind="src"></classpathentry>
  <classpathentry output="target\scala-2.9.1\test-classes" path="src\test\java" kind="src"></classpathentry>
  <classpathentry path="..\..\modules\metapido-core\lib\library1.jar" kind="lib"></classpathentry>  
                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...

should be:

<classpath>
  <classpathentry output="target\scala-2.9.1\classes" path="src\main\scala" kind="src"></classpathentry>
  <classpathentry output="target\scala-2.9.1\classes" path="src\main\java" kind="src"></classpathentry>
  <classpathentry output="target\scala-2.9.1\test-classes" path="src\test\scala" kind="src"></classpathentry>
  <classpathentry output="target\scala-2.9.1\test-classes" path="src\test\java" kind="src"></classpathentry>
  <classpathentry path=".\lib\library1.jar" kind="lib"></classpathentry>  
...

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

Reproduce the project layout using project/Build.scala, project/plugins.sbt, modules/core-project/lib/library1.jar, and the generated .classpath. Start with the Eclipse project generation path for unmanaged libraries, then compare the emitted library path with the expected .\lib\library1.jar entry.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
build-system
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.