Re: [sbt] Dependency management issue after upgrading to 0.12.2-RC2

[Mark Harrah]

On Mon, 14 Jan 2013 15:06:52 -0800 (PST)
Drew <dr...@venarc.com> wrote:

> I just upgraded from 0.12.0 to 0.12.2-RC2 and sbt can't download the
> sources for artifacts anymore. From what I see there are two issues:
> 1. It's using the wrong file extension (.src instead of .jar)
> 2. It's looking for the artifacts in Typesafe repo instead of Maven Central
>
> Anyone has an idea what's going on?

Can you post a build file that demonstrates the problem? At a minimum, what are your dependencies and resolvers?

-Mark

>
> [info] Loading project definition from
> /Users/drew/Projects/Tester/workspace/JacksonPlus/project
> [info] Set current project to JacksonPlus (in build
> file:/Users/drew/Projects/Tester/workspace/JacksonPlus/)
> [info] Updating
> {file:/Users/drew/Projects/Tester/workspace/JacksonPlus/}JacksonPlus...
> [warn] [NOT FOUND ] commons-io#commons-io;2.4!commons-io.src (702ms)
>
> [warn] ==== Typesafe Releases Repository: tried
> [warn]
> http://repo.typesafe.com/typesafe/releases/commons-io/commons-io/2.4/commons-io-2.4-sources.src
> [warn] [NOT FOUND ] com.github.stephenc.eaio-uuid#uuid;3.2.0!uuid.src
> (269ms)
> [warn] ==== Typesafe Releases Repository: tried
> [warn]
> http://repo.typesafe.com/typesafe/releases/com/github/stephenc/eaio-uuid/uuid/3.2.0/uuid-3.2.0-sources.src
> [warn] [NOT FOUND ] org.imgscalr#imgscalr-lib;4.2!imgscalr-lib.src (229ms)
> [warn] ==== Typesafe Releases Repository: tried
> [warn]
> http://repo.typesafe.com/typesafe/releases/org/imgscalr/imgscalr-lib/4.2/imgscalr-lib-4.2-sources.src
> [warn] [NOT FOUND ] org.iq80.snappy#snappy;0.2!snappy.src (240ms)
> [warn] ==== Typesafe Releases Repository: tried
> [warn]
> http://repo.typesafe.com/typesafe/releases/org/iq80/snappy/snappy/0.2/snappy-0.2-sources.src
> [warn] ::::::::::::::::::::::::::::::::::::::::::::::
> [warn] :: FAILED DOWNLOADS ::
> [warn] :: ^ see resolution messages for details ^ ::
> [warn] ::::::::::::::::::::::::::::::::::::::::::::::
> [warn] :: commons-io#commons-io;2.4!commons-io.src
> [warn] :: com.github.stephenc.eaio-uuid#uuid;3.2.0!uuid.src
> [warn] :: org.imgscalr#imgscalr-lib;4.2!imgscalr-lib.src
> [warn] :: org.iq80.snappy#snappy;0.2!snappy.src
>
>
> --
> You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/simple-build-tool/-/MQESEktyfEsJ.
> To post to this group, send email to simple-b...@googlegroups.com.
> To unsubscribe from this group, send email to simple-build-t...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
>

[Drew Kutcharian]

Hi Mark,

I put together a minimal configuration to demonstrate the issue: https://github.com/kutchar/sbt-deps-issue

There are two Play 2.1 (latest from master) projects there:
app: a barebones play application that has lib as a dependency
lib: another barebones play application that is used by app

When I try to build and publish lib, everything is fine and sbt downloads the sources correctly.

But when I try to build app, I get the errors.

Thanks,

Drew

[Mark Harrah]

On Mon, 14 Jan 2013 18:15:48 -0800
Drew Kutcharian <dr...@venarc.com> wrote:

> Hi Mark,
>
> I put together a minimal configuration to demonstrate the issue: https://github.com/kutchar/sbt-deps-issue
>
> There are two Play 2.1 (latest from master) projects there:
> app: a barebones play application that has lib as a dependency
> lib: another barebones play application that is used by app
>
> When I try to build and publish lib, everything is fine and sbt downloads the sources correctly.
>
> But when I try to build app, I get the errors.

Ok, thanks.

It is certainly the goal to make upgrades within 0.12.x seamless and if there is an sbt issue, we'll try to fix it. A complication might be that you upgraded to Play at the same time (nor not?) and I don't know whether things changed there.

It would help if you can make this reproducible outside of Play. I will try to reproduce it myself based on your sample so far, but I have a few other dependency management issues to look at first.

There are some other things that may or may not be related to this problem that you might do, just from an initial look.

The first one is that withSources() is generally superseded by the update-classifiers, which pulls down sources and javadocs. This task is used by the eclipse and intellij integration plugins.

One thing I would recommend is to try using the Typesafe ivy-releases repository instead of the full typesafe releases repository, which is broken. I don't know that it will fix your issue, though, and it might be defined by Play.

Next, is your company Artifactory a full proxy? If you would prefer to go through just that, you might see:

http://www.scala-sbt.org/release/docs/Detailed-Topics/Proxy-Repositories.html

This will definitively override repositories for all plugins and libraries for a user.

-Mark

[Drew Kutcharian]

> One thing I would recommend is to try using the Typesafe ivy-releases repository instead of the full typesafe releases repository, which is broken. I don't know that it will fix your issue, though, and it might be defined by Play.

Unfortunately the Typesafe repo is defined by Play so not sure if I have control over it.

> Next, is your company Artifactory a full proxy? If you would prefer to go through just that, you might see:

No, our Artifactory is not a full proxy.

So I'm stuck trying to fix the issue. It seems like the issue is with the process that gets the dependencies for a dependency.


-- Drew

[Drew Kutcharian]

I still haven't been able to fix this, but I found that that If I remove the withSources() on lib's dependencies before publishing it (so the generated pom doesn't have any source artifacts in there), then everything works as expected when I update app.

[delasoul]

Hello,

has there been a solution for this problem?
I have the same behaviour:
When publishing and I have dependencies with "withSources" I end up with a pom file including:
<dependency>
  <groupId>theGroup</groupId>
  <artifactId>theArtifact</artifactId>
  <version>1.0</version>
  <classifier>sources</classifier>
  <type>src</type>
</dependency>

When using the published artifacts as dependency tasks like update, gen-idea etc.fail with

download failed: com.typesafe.akka#akka-actor_2.10;2.2.0-RC1!akka-actor_2.10.src

Can I somehow exclude these src dependencies from the generated pom when publishing?

thanks in advance,

michael

[delasoul]

forgot, I am using 0.12.4

[Michael Slinn]

I hit exactly the same bug, using SBT 0.13.0 and Play 2.2.1

I wish SBT would consider a missing source file as a not-fatal issue!