Re: State of the Build

2015-11-06 Thread Jakob Odersky
gt; >> >> >> Second, the sbt build also uses maven "profiles" requiring the use of >> >> specific commandline parameters when starting sbt. Furthermore, since >> it >> >> relies on maven poms, dependencies to the scala binary versio

Re: State of the Build

2015-11-05 Thread Ted Yu
versions. >> Sbt could leverage built-in constructs to support cross-compilation and >> emulate profiles with configurations and new build targets. This would >> remove external state from the build (in that no extra steps need to be >> performed in a particular order to generate

State of the Build

2015-11-05 Thread Jakob Odersky
constructs to support cross-compilation and emulate profiles with configurations and new build targets. This would remove external state from the build (in that no extra steps need to be performed in a particular order to generate artifacts for a new configuration) and therefore improve stability

Re: State of the Build

2015-11-05 Thread Stephen Boesch
running an external script when switching versions. > Sbt could leverage built-in constructs to support cross-compilation and > emulate profiles with configurations and new build targets. This would > remove external state from the build (in that no extra steps need to be > per

Re: State of the Build

2015-11-05 Thread Sean Owen
when switching versions. >> Sbt could leverage built-in constructs to support cross-compilation and >> emulate profiles with configurations and new build targets. This would >> remove external state from the build (in that no extra steps need to be >> performed in a partic

Re: State of the Build

2015-11-05 Thread Koert Kuipers
ting sbt. Furthermore, since it > relies on maven poms, dependencies to the scala binary version (_2.xx) are > hardcoded and require running an external script when switching versions. > Sbt could leverage built-in constructs to support cross-compilation and > emulate profiles with configu

Re: State of the Build

2015-11-05 Thread Mark Hamstra
version (_2.xx) are >>> hardcoded and require running an external script when switching versions. >>> Sbt could leverage built-in constructs to support cross-compilation and >>> emulate profiles with configurations and new build targets. This would >>> remove exter

Re: State of the Build

2015-11-05 Thread Patrick Wendell
ndencies to the scala binary version (_2.xx) > are > >> hardcoded and require running an external script when switching > versions. > >> Sbt could leverage built-in constructs to support cross-compilation and > >> emulate profiles with configurations and n