Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reorganized spaces for shapeless 1 and 2 #1

Closed

Conversation

cunei
Copy link

@cunei cunei commented Apr 10, 2014

This pull request patches the shapeless-two-version so that all transitive dependencies are included.
Currently specs2 needs shapeless 2.x, and all the other projects that depend on shapeless also need specs, so there are no shapeless1.2.4-specific projects; an empty section is provided as an example.

This pull request relies on the fact that two incompatible versions of shapeless (1 and 2) will not be used together, and that spray will also use shapeless2. If the intent is using shapeless1 with spray, instead, your original hack will work ok as it will trim the transitive dependencies on shapeless2.

This pull request is provided as an example.

gkossakowski and others added 2 commits April 9, 2014 16:38
Make use of spaces feature of dbuild which allows us to build multiple
versions of the same project. We build shapeless 1.2.4 which is dependency
of spray. This allows us to get rid of the fork of spray.

We also build shapeless 2 which is dependency of specs2 and spire.

The specs2 and spire compile successfully. Spray is still failing with
compilations errors saved here:
https://gist.github.com/gkossakowski/10277880
@gkossakowski
Copy link
Owner

@cunei: this fail with: https://jenkins-dbuild.typesafe.com:8499/job/Community-2.11.x-manual/13/consoleText

It seems like publishing is broken with this new spaces setup.

@cunei
Copy link
Author

cunei commented Apr 16, 2014

I thought I had tested it. I had a look at the log, and I suspect that something might be awry with dbuild and sbt 0.13.2 (you merged this diff on top of the merged-in PR scala#33). We will know for sure tonight, as the community build in master (sans this diff) will fail in that case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants