Skip to content

SNAPSHOT dependency does not get resolved while compiling a dependent project after publishing depended-on jar to remote repository when both operations are on the same box. #1495

@Shrivallabh

Description

@Shrivallabh

Build chain

I am using scala 2.10.3 with sbt 0.13

The scenario

I have a module M that my service S depends on.

S and M are not under the same umbrella. \

The M is part of a multi module project, while S is a standalone project.

S has the snapshot version of the M added as a dependency.

  1. I made some changes to the M
  2. I published the changes to my remote repo
  3. I started a clean build of S on the same
  4. Sbt is unable to pickup the latest snapshot of M. In fact, the build fails.

The error

[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  ::          UNRESOLVED DEPENDENCIES         ::
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::
[warn]  :: com.something#someart_2.10;0.1-SNAPSHOT: not found
[warn]  ::::::::::::::::::::::::::::::::::::::::::::::

Observation

The ivydata xml file for M contains the following line after performing the publish operation.
resolver=sbt-chain

Removing this line allows the dependency to be picked up

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions