Skip to content

Correct build dependencies. #325

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

Merged
merged 1 commit into from
May 6, 2021
Merged

Correct build dependencies. #325

merged 1 commit into from
May 6, 2021

Conversation

ckipp01
Copy link
Member

@ckipp01 ckipp01 commented May 5, 2021

This makes a few small changes:

  1. I'm pretty sure the scala-compiler for the actual plugin can just
    have a Provided configuration. I don't believe we actually need to package it
    up seeing that it should always be there.
  2. Secondly, I mistakenly added the scala-compiler as a dependency to
    the runtime artifact when it indeed should not be. When I refactored
    the build, it came along, and should have not. If you look back
    you'll notice that it wasn't in 1.4.1
  3. When the change was made to start doing a full cross publish in this
    commit: ac3db32
    it was added for both the compiler plugin and the actual runtime.
    Looking through things and testing locally with the sbt plugin, I
    don't see a reason why the runtime needs to actually be crossed fully
    like the actual plugin. This removes the crossVersion full from the
    runtime.

@@ -70,8 +70,7 @@ lazy val runtime = CrossProject(
crossTarget := target.value / s"scala-${scalaVersion.value}",
crossVersion := CrossVersion.full,
libraryDependencies ++= Seq(
"org.scalatest" %%% "scalatest" % scalatestVersion % Test,
"org.scala-lang" % "scala-compiler" % scalaVersion.value % Compile
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lefou you were totally correct... this doesn't need to be a dependency for the runtime. If you look back at the commits it seems to have slipped in when I refactored the build definition.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What I wonder is, whether we can avoid the CrossVersion.full for the runtime.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So from digging further in, from what I can tell, no this doesn't need a full cross version. I've gone ahead and tested this locally and also with the sbt plugin to verify. I've gone ahead and removed the CrossVersion.full on the runtime and also then could remove the hacky thing we were doing to name the scalaJS artifact correct as well since it's now done correctly automatically.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should be able to give this a try now wtih 1.4.5+1-775fcaca-SNAPSHOT. Report back if something seems awry. I'd be good to get this more widely tested before a release.

This makes a few small changes:
1. I'm pretty sure the scala-compiler for the actual plugin can just
   have a Provided scope. I don't believe we actually need to package it
   up seeing that it should always be there.
2. Secondly, I mistakenly added the scala-compiler as a dependency to
   the runtime artifact when it indeed should not be. When I refactored
   the build, it came along, and should have not. If you look back
   you'll notice that it wasn't in 1.4.1
3. When the change was made to start doing a full cross publish in this
   commit: ac3db32
   it was added for both the compiler plugin and the actual runtime.
   Looking through things and testing locally with the sbt plugin, I
   don't see a reason why the runtime needs to actually be crossed fully
   like the actual plugin. This removes the crossVersion full from the
   runtime.
@ckipp01 ckipp01 merged commit 775fcac into scoverage:main May 6, 2021
@ckipp01 ckipp01 deleted the buildCorrections branch May 6, 2021 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants