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.

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

Where should we publish sbt-twirl to? #473

Closed
mkurz opened this issue Jan 3, 2022 · 2 comments
Closed

Where should we publish sbt-twirl to? #473

mkurz opened this issue Jan 3, 2022 · 2 comments

Comments

@mkurz
Copy link
Member

mkurz commented Jan 3, 2022

I want to publish twirl 1.6.0-M1, now I am asking myself where the sbt plugin should get published to?

The old 1.5.1 (plugin) release got published under com.typesafe.sbt in the read-only repo https://repo.scala-sbt.org/.
We could of course switch to com.typesafe.sbt on maven central, however looking at https://repo1.maven.org/maven2/com/typesafe/sbt/ it seems no one is actually publishing sbt-plugins there anymore. It seems all sbt-plugins are now moving to https://repo1.maven.org/maven2/com/github/sbt/. Actually, if you look at https://repo1.maven.org/maven2/com/typesafe/sbt/, the only newer stuff there is sbt-git, which IMHO should be published under com.github.sbt as well now, I don't know why they keep publishing to com.typesafe.sbt (started a discussion: sbt/sbt-git#198). And sbt-play-ebean only published a RC3, and actually I think that's the same story like sbt-twirl here.

Shouldn't sbt-twirl (as well as sbt-play-ebean) now be published under com.typesafe.play?
Or I am completely wrong and should we keep it under com.typesafe.sbt? However, be aware that whoever wants to publish twirl then will need permissions to publish to com.typesafe.sbt (for the sbt-plugin) as well to com.typesafe.play (to publish the twirl-api,... libs).
Moving twirl (the plugin) to com.github.sbt would be another option, not sure however, because I think that means twirl should move to the sbt Github organization as well.

@octonato
Copy link
Contributor

octonato commented Jan 3, 2022

I vote for com.typesafe.play. Makes lot of sense.

@mkurz
Copy link
Member Author

mkurz commented Jan 3, 2022

So everyone voted for com.typesafe.play 👍

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

No branches or pull requests

2 participants