- From: Alexandre Bertails <alexandre@bertails.org>
- Date: Mon, 2 Feb 2015 11:49:43 -0500
- To: Anton Kulaga <antonkulaga@gmail.com>
- Cc: "public-banana-rdf@w3.org" <public-banana-rdf@w3.org>
On Mon, Feb 2, 2015 at 3:16 AM, Anton Kulaga <antonkulaga@gmail.com> wrote: > Sad :_( Is there a way to make some subprojects appear for 2.11 and disapear > (be switched of) for 2.10 in order not to break 2.10 build? It is likely doable. Probably a one-liner in sbt but I don't have the answer on the top of my head. As for meta itself, I would recommend making it a standalone library for the time being. We definitely need more experience with it before making it part of the main project. Also, there is some clash with what's available in diesel, and it's a departure from all the approaches I have seen in the Scala world recently. Have you considered the shapeless path instead? Alexandre > > 2015-02-02 4:11 GMT+02:00 Alexandre Bertails <alexandre@bertails.org>: >> >> On Sun, Feb 1, 2015 at 8:36 PM, Anton Kulaga <antonkulaga@gmail.com> >> wrote: >> > Hi all, >> > >> > I wonder, is anybody using banana-rdf with scala 2.10.4? I see that >> > almost >> > everybody moved to 2.11.x Meanwhile cross-compiling to 2.10/2.11 makes >> > build >> > more complicated and blocks some features as not all code cross-compiles >> > well for both scala-s ( I failed to make macroses work well for 2.10.x). >> > So >> > I suggest to drop 2.10 support unless somebody is still using it >> >> My employer still builds with 2.10. >> >> Alexandre >> >> > >> > -- >> > Best regards, >> > Anton Kulaga > > > > > -- > Best regards, > Anton Kulaga
Received on Monday, 2 February 2015 16:50:10 UTC