Skip to content
This repository has been archived by the owner on Mar 25, 2020. It is now read-only.

Release for 2.13.0-M1 #14

Closed
ghost opened this issue May 9, 2017 · 17 comments
Closed

Release for 2.13.0-M1 #14

ghost opened this issue May 9, 2017 · 17 comments

Comments

@ghost
Copy link

ghost commented May 9, 2017

and bump the insanely low version number at the same time.

Needed for typelevel/cats#1648

@SethTisue
Copy link
Member

SethTisue commented Jul 8, 2017

@BennyHill is this something you might be able to give some attention to sometime soon...? or something you could use external help with?

@ghost
Copy link
Author

ghost commented Aug 28, 2017

Fyi, this blocked by scoverage that is in turn blocked by scala-logging

Also see comments is cats

The general "problem" here is that catalysts is the first in the lower levels to pull in more of the regular QA/util libs and so is the first to be "hit" if there are issues. Just saying as to why it can appear to be a bottleneck.

@ghost
Copy link
Author

ghost commented Aug 28, 2017

@SethTisue scala-logging is in the Lightbend stable, is this something you could look at?

@ghost
Copy link
Author

ghost commented Aug 28, 2017

Also waiting for tpolecat/tut#183 and after that, 47degrees/sbt-microsites#215 needs bumping before release

@SethTisue
Copy link
Member

@SethTisue scala-logging is in the Lightbend stable, is this something you could look at?

sort of in the Lightbend stable... it was Heiko's project, but he left the company a few years ago and the library has been community-maintained since then. we're more conservative these days about adding new libraries under the typesafehub or lightbend orgs.

but anyway, sorry for the delayed reply, I've commented on lightbend-labs/scala-logging#93

@SethTisue
Copy link
Member

SethTisue commented Oct 4, 2017

scala-logging is now published for 2.13.0-M1, and I submitted a new PR bumping it to M2 (lightbend-labs/scala-logging#97)

@SethTisue
Copy link
Member

scala-logging 3.7.2 is now published for M2 as well

@SethTisue
Copy link
Member

Scala 2.13.0-M3 is now out

@ghost
Copy link
Author

ghost commented Jan 31, 2018

Ref https://github.com/BennyHill/catalysts/tree/fix/14 - bulk of work done already 😄

@LukaJCB
Copy link
Member

LukaJCB commented Feb 23, 2018

@BennyHill Any update? :)

@ghost
Copy link
Author

ghost commented Feb 23, 2018

Sorry, mid-term, 2 week school holidays... looking now 😉

@ghost
Copy link
Author

ghost commented Mar 30, 2018

M3 released after #16

@ghost ghost closed this as completed Mar 30, 2018
@SethTisue
Copy link
Member

if I add this to a test project:

+    "org.typelevel"                    %% "catalysts"                 % "0.6",

a number of catalysts artifacts do resolve, but then I get:

[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	::          UNRESOLVED DEPENDENCIES         ::
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	:: org.typelevel#catalysts-tests_2.13.0-M3;0.6: not found
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::

@ghost
Copy link
Author

ghost commented Mar 31, 2018

The tests are just internal tests, not published. So this looks correct

@ghost
Copy link
Author

ghost commented Mar 31, 2018

Oh... We should not be publishing a catalysts artifact in fact. That's the issue. So we can fix that. But just add the libs needed. Eg catalysts-macros, catalysts-platform

@ghost
Copy link
Author

ghost commented Mar 31, 2018

See #19

@SethTisue
Copy link
Member

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants