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.

Sign up for GitHub

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

Jump to bottom

Upgrade Scala 2.12 #3179

Closed
13 tasks done
slandelle opened this issue Nov 4, 2016 · 3 comments
Closed
13 tasks done

Upgrade Scala 2.12 #3179

slandelle opened this issue Nov 4, 2016 · 3 comments
Assignees
@slandelle
Labels
Type - Chore
Milestone
2.3.0

Comments

@slandelle
Copy link
Member

slandelle commented Nov 4, 2016 •
edited
Loading

  • akka
  • scala-swing
  • scala-xml
  • scala-java8-compat
  • fastring
  • scopt
  • scala-logging
  • jsonpath
  • boopickle
  • redisclient
  • quicklens
  • scalatest
  • scalacheck
@slandelle slandelle added this to the 3.0.0 milestone Nov 4, 2016
@slandelle slandelle self-assigned this Nov 19, 2016
@slandelle slandelle mentioned this issue Dec 7, 2016
Closed
slandelle added a commit that referenced this issue Dec 7, 2016
@slandelle
Upgrade Scala 2.12, close #3179
057f384 
Motivation:

Scala 2.12.1 is out and all our dependencies are available, so we can migrate too.

Modifications:

* Upgrade gatling-build-plugin to 2.0.0 that configures Scala 2.12 as the default
* Upgrade dependencies
* Let Expression[T] invariant, even though Validation[+T] is covariant, using `@@uncheckedVariance`. This is required for our DSL to compile, see https://issues.scala-lang.org/browse/SI-10099
* Add findbugs dependency, as Scala 2.12 seems to no longer accept compiling with a stub (warnings with Scala 2.11)
* Drop `io.gatling.commons.util.Future` in favor of standard `Future.unit`
* Fix `JsonPathExtractorSpec` that was actually broken

Result:

Gatling is now compiled against Scala 2.12
slandelle added a commit that referenced this issue Dec 7, 2016
@slandelle
Upgrade Scala 2.12, close #3179
d2ced35 
Motivation:

Scala 2.12.1 is out and all our dependencies are available, so we can migrate too.

Modifications:

* Upgrade gatling-build-plugin to 2.0.0 that configures Scala 2.12 as the default
* Upgrade dependencies
* Let Expression[T] invariant, even though Validation[+T] is covariant, using `@uncheckedVariance`. This is required for our DSL to compile, see https://issues.scala-lang.org/browse/SI-10099
* Add findbugs dependency, as Scala 2.12 seems to no longer accept compiling with a stub (warnings with Scala 2.11)
* Drop `io.gatling.commons.util.Future` in favor of standard `Future.unit`
* Fix `JsonPathExtractorSpec` that was actually broken

Result:

Gatling is now compiled against Scala 2.12
slandelle added a commit that referenced this issue Dec 7, 2016
@slandelle
Upgrade Scala 2.12, close #3179
40af03f 
Motivation:

Scala 2.12.1 is out and all our dependencies are available, so we can migrate too.

Modifications:

* Upgrade gatling-build-plugin to 2.0.0 that configures Scala 2.12 as the default
* Upgrade dependencies
* Let Expression[T] invariant, even though Validation[+T] is covariant, using `@uncheckedVariance`. This is required for our DSL to compile, see https://issues.scala-lang.org/browse/SI-10099
* Add findbugs dependency, as Scala 2.12 seems to no longer accept compiling with a stub (warnings with Scala 2.11)
* Drop `io.gatling.commons.util.Future` in favor of standard `Future.unit`
* Fix `JsonPathExtractorSpec` and `HttpBodyJsonPathCheckSpec` that were actually broken

Result:

Gatling is now compiled against Scala 2.12
@Tvaroh
Copy link

Tvaroh commented May 20, 2017

Is there a build using 2.12?

@SethTisue SethTisue mentioned this issue Jul 12, 2017
Closed
@slandelle slandelle modified the milestones: 2.3.0, 3.0.0 Aug 29, 2017
slandelle added a commit that referenced this issue Aug 30, 2017
@slandelle
Upgrade Scala 2.12 and sbt 0.13.16, close #3179
3fbcdd8 
Motivation:

Scala 2.12 is out and all our dependencies are available, so we can
migrate too.

Modifications:

* Upgrade gatling-build-plugin to 2.0 that configures Scala 2.12 as the
default
* Upgrade dependencies
* Let Expression[T] invariant, even though Validation[+T] is covariant,
using `@uncheckedVariance`. This is required for our DSL to compile,
see https://issues.scala-lang.org/browse/SI-10099
* Add findbugs dependency, as Scala 2.12 seems to no longer accept
compiling with a stub (warnings with Scala 2.11)
* Drop `io.gatling.commons.util.Future` in favor of standard
`Future.unit`
* Fix `JsonPathExtractorSpec` and `HttpBodyJsonPathCheckSpec` that were
actually broken

Result:

Gatling is now compiled against Scala 2.12
slandelle added a commit that referenced this issue Aug 30, 2017
@slandelle
Upgrade Scala 2.12 and sbt 0.13.16, close #3179
40ab3df 
Motivation:

Scala 2.12 is out and all our dependencies are available, so we can
migrate too.

Modifications:

* Upgrade gatling-build-plugin to 2.0 that configures Scala 2.12 as the
default
* Upgrade dependencies
* Let Expression[T] invariant, even though Validation[+T] is covariant,
using `@uncheckedVariance`. This is required for our DSL to compile,
see https://issues.scala-lang.org/browse/SI-10099
* Add findbugs dependency, as Scala 2.12 seems to no longer accept
compiling with a stub (warnings with Scala 2.11)
* Drop `io.gatling.commons.util.Future` in favor of standard
`Future.unit`
* Fix `JsonPathExtractorSpec` and `HttpBodyJsonPathCheckSpec` that were
actually broken

Result:

Gatling is now compiled against Scala 2.12
@AlexPerfMechnix
Copy link

Hi @slandelle ,
I was using gatling 3.0.0 and all was working fine until socket issues with ALB. I couldnt get proper document in migrating from 3.0.0 to Latest. Could you help me on this.

--Alex

@slandelle
Copy link
Member Author

@AlexPerfMechnix See the "Upgrading" section in our doc: https://gatling.io/docs/gatling/
Then, questions are better asked on our community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@slandelle slandelle

Labels
Type - Chore
Milestone
2.3.0
Development

No branches or pull requests
3 participants
@slandelle @Tvaroh @AlexPerfMechnix