-
Notifications
You must be signed in to change notification settings - Fork 43
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
Add sbt-vspp for publishing the SBT plug-in in a Maven-consistent format #234
Conversation
This is to enable usage of sbt-scalafmt in Enterprise environments where only the valid-POM format is accepted for JAR downloads, enabling advanced Scala capabilities for many many environments. Currently the only way to use it is by manual republishing but we rather any updates get made available automatically. The only change this does is to add extra JAR and POM to the released artifact (while keeping the old structure -- notice how when you click on 'Browse' on here https://search.maven.org/artifact/org.scalameta/sbt-scalafmt/2.4.6/jar - it goes to a 404 Not Found page. More background here: https://github.com/esbeetee/sbt-vspp/blob/main/README.md
@kitbellew we already took it into bloop so in general PR is fine. The only issue is that scripted test fails with some binary-incompatibility error. |
Thanks for pointing out @dos65. Might be the SBT version vspp is linked against. I'll check later to fix this in a new version. |
Reported via scalameta/sbt-scalafmt#234 (comment) Error is here: https://github.com/scalameta/sbt-scalafmt/runs/7604602427?check_suite_focus=true When SBT processes the `if()`, it seems to have been updated more recently, ie does not work with SBT 1.2.6 for example.
Reported via scalameta/sbt-scalafmt#234 (comment) Error is here: https://github.com/scalameta/sbt-scalafmt/runs/7604602427?check_suite_focus=true When SBT processes the `if()`, it seems to have been updated more recently, ie does not work with SBT 1.2.6 for example.
Reproduced it - will fix in due course. This is because an SBT 1.6 build refers to settings that are not there in SBT 1.2.x |
hi @dos65 this is fixed now, would you be able to review it again? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey, sorry this has sat for such a long time. I see we did this in Bloop, and I also merged this into scoverage, so I don't think we have any issues here.
Hi! Hope you don't mind me making this PR to request to publish Maven-consistent format of this plugin alongside the existing artifact format.
This is to enable usage of sbt-scalafmt in Enterprise environments where only the valid-POM format is accepted for JAR downloads, enabling advanced Scala capabilities for many many environments. Currently the only way to use it is by manual republishing but we rather any updates get made available automatically.
The only change this does is to add extra JAR and POM to the released artifact (while keeping the old structure) -- notice how currently when you click on 'Browse' on here https://search.maven.org/artifact/org.scalameta/sbt-scalafmt/2.4.6/jar - it goes to a 404 Not Found page -- this is because of the inconsistent / invalid POM.
More background here: https://github.com/esbeetee/sbt-vspp/blob/main/README.md