update to spray 1.3.2

[jrudolph]

This disables legacy subprojects depending on shapeless 1.

[jrudolph]

May fix first part of #67

[jrudolph]

Can you trigger a build for this one?

[jrudolph]

If it works we can try running the tests as well.

[gkossakowski]

Running here: https://jenkins-dbuild.typesafe.com:8499/job/Community-2.11.x-manual/75/console

[jrudolph]

This failed but it showed a few interesting things:

• we don't have a spray-testkit-shapeless2 project but spray-testkit just seems to work both for the shapeless1 and shapeless2 versions because it doesn't seem to touch any shapeless related code of spray-routing and the dependency is declared as "provided"
• docs and examples are still built using the shapeless1 version that's why this build ultimately failed

I made a small update to the spray build and updated this PR to use the new version. Could you trigger another build with this version?

[gkossakowski]

Running here: https://jenkins-dbuild.typesafe.com:8499/job/Community-2.11.x-manual/76/console

I found this comment related to shapeless in the config:

  // latest commits in scala-2.11.x branch break spray, Miles has been pinged about it
  // TODO: add shapeless 1.2.4 to dbuild definition which should allow us to switch to
  // upstream version of spray that depends on shapeless 1.2.4
  shapeless-ref                : "milessabin/shapeless.git#6dd9ec22b68d6a911ad83d0a537bf2043b748fc2"

I'm wondering if this might cause problems for you trying to upgrade to stable version of spray?

[gkossakowski]

Are those build fixes be included in future versions of spray so we can stick to a tag?

[gkossakowski]

Given that this builds successfully I'm going to merge it because it's net improvement. We can look into shapeless situation as a second step.

[gkossakowski]

Thanks for contribution!

[jrudolph]

I found this comment related to shapeless in the config

Yes, right, I read this but forgot about it later on. I think this is just an old comment and we should try to update to a proper tag of shapeless.

Are those build fixes be included in future versions of spray so we can stick to a tag?

Yes, exactly, it's current HEAD of the regular release/1.3 branch just two or three commits after the v1.3.2 release tag where I fixed the small things we noticed here.