-
Notifications
You must be signed in to change notification settings - Fork 59
Add scalastyle #198
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 scalastyle #198
Conversation
@matthewfarwell any idea what this is about?
|
Yeah. I've replaced deploy with aetherDeploy, because I use a maven repo to deploy to. Do you call deploy as part of the build? |
Yes, the community build first modifies |
@matthewfarwell there are two possible ways forward here: either you can change the build in your repo to somehow allow what dbuild wants, or, you can update this PR to customize the build in the context of the community build only, e.g by using sometimes both are necessary: the build needs to be altered to add some kind of hook, and then the entry in |
@matthewfarwell Happy New Year! still interested in pursuing this? |
Yes I am, but haven't had time to look at it yet. |
I've added an option to not publish automatically to a maven repo - can you tell if this works? |
test run: https://scala-ci.typesafe.com/job/scala-2.11.x-integrate-community-build/243/consoleFull (will be 404 for a while, Jenkins is backed up) |
Can you rebase this onto current |
@matthewfarwell interested in getting this across the finish line...? |
@matthewfarwell interested in getting this across the finish line...? |
closing for apparent lack of interest |
Thanks for taking this up Seth. Is this just a case of removing the aetherDeploy (with a flag somehow) when running under the community builds? |
@matthewfarwell see my commits at https://github.com/scalacommunitybuild/scalastyle/commits/community-build-2.12 I had to fork anyway to get rid of the bintray stuff (an unfortunate dbuild limitation), so having forked, I didn't need to worry about putting the aether stuff behind a flag, I could just delete it. |
Thing is, I don't use bintray any more, I deploy to sonatype. So that can be removed on my end as well, and indeed has been done in master. For the aether-deploy, do you need to remove both the plugin and Seq(aetherPublishBothSettings: _*), or just the Seq(aetherPublishBothSettings: _*) ? |
@matthewfarwell looks like removing the plugin isn't necessary, so I was able to unfork in a2a81ce |
No description provided.