Skip to content

Conversation

lrytz
Copy link
Member

@lrytz lrytz commented Apr 26, 2017

The build didn't use the scala-module-plugin before but duplicated
most of its settings - maybe I missed the reason why this is the case?

Also update tag-based publishing to the latest version.

The build didn't use the `scala-module-plugin` before but duplicated
most of its settings - maybe I missed the reason why this is the case?

Also update tag-based publishing to the latest version.
@lrytz
Copy link
Member Author

lrytz commented Apr 26, 2017

Also adds cross-building with 2.13.0-M1

@SethTisue
Copy link
Member

The build didn't use the scala-module-plugin before but duplicated
most of its settings - maybe I missed the reason why this is the case

I am curious about this as well

@retronym
Copy link
Member

retronym commented May 9, 2017

I don't recall the reason. Perhaps I took that across prior to those settings being factored into scala-module-plugin. Or perhaps scala-module-plugin at the time had some rough edge that prevented direct use. I'll merge and try out the new release mechanism and see what happens.

@retronym retronym closed this May 9, 2017
@retronym retronym reopened this May 9, 2017
@retronym retronym merged commit 8492b9d into scala:master May 9, 2017
@SethTisue
Copy link
Member

released 0.9.6 for 2.13.0-M1: https://travis-ci.org/scala/async/jobs/231268560 (I also closed and released the staging repo on Sonatype)

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.

3 participants