Skip to content

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

Closed
wants to merge 2 commits into from
Closed

Add scalastyle #198

wants to merge 2 commits into from

Conversation

matthewfarwell
Copy link

No description provided.

@SethTisue
Copy link
Member

@SethTisue SethTisue self-assigned this Dec 13, 2015
@SethTisue
Copy link
Member

@matthewfarwell any idea what this is about?

[scalastyle] java.lang.RuntimeException: The configured repo MUST be a maven repo, but was: FileRepository(deploy-to-local-repo,FileConfiguration(true,None),Patterns(ivyPatterns=List(), artifactPatterns=List(/home/jenkins/workspace/scala-2.11.x-integrate-community-build/target-0.9.5/project-builds/scalastyle-f35b87524ecfea01fd360be9166e9f26ef467e63/.dbuild/local-publish-repo/[organisation]/[module](_[scalaVersion])(_[sbtVersion])/[revision]/[artifact]-[revision](-[classifier]).[ext]), isMavenCompatible=true, descriptorOptional=false, skipConsistencyCheck=false))
[scalastyle]    at scala.sys.package$.error(package.scala:27)
[scalastyle]    at aether.Aether$$anonfun$1.applyOrElse(Plugin.scala:98)
[scalastyle]    at aether.Aether$$anonfun$1.applyOrElse(Plugin.scala:96)
[scalastyle]    at scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:33)
[scalastyle]    at scala.Option.collect(Option.scala:250)
[scalastyle]    at aether.Aether$.deployIt(Plugin.scala:96)
[scalastyle]    at aether.Aether$$anonfun$deployTask$1.apply(Plugin.scala:68)
[scalastyle]    at aether.Aether$$anonfun$deployTask$1.apply(Plugin.scala:67)

@matthewfarwell
Copy link
Author

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?

@cunei
Copy link

cunei commented Dec 14, 2015

Yes, the community build first modifies publishTo (pointing to a local directory), then invokes publish so that the artifacts generated by each project are collected and cached.

@SethTisue
Copy link
Member

@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 extra.commands to alter some settings on the fly

sometimes both are necessary: the build needs to be altered to add some kind of hook, and then the entry in common.conf needs to be altered to take advantage of that new hook

@SethTisue SethTisue removed their assignment Dec 15, 2015
@SethTisue
Copy link
Member

@matthewfarwell Happy New Year! still interested in pursuing this?

@matthewfarwell
Copy link
Author

Yes I am, but haven't had time to look at it yet.

@matthewfarwell
Copy link
Author

I've added an option to not publish automatically to a maven repo - can you tell if this works?

@SethTisue
Copy link
Member

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)

@SethTisue SethTisue self-assigned this Mar 3, 2016
@SethTisue
Copy link
Member

Can you rebase this onto current 2.11.x, please? It's no longer possible to test unless recent changes are included.

@SethTisue
Copy link
Member

@matthewfarwell interested in getting this across the finish line...?

@SethTisue SethTisue removed their assignment Apr 28, 2016
@SethTisue
Copy link
Member

@matthewfarwell interested in getting this across the finish line...?

@SethTisue
Copy link
Member

closing for apparent lack of interest

@SethTisue SethTisue closed this Oct 7, 2016
@SethTisue
Copy link
Member

I'm working on resolving this by forking scalastyle and just removing the aether-deploy stuff. see #577, #535

@SethTisue SethTisue mentioned this pull request Jul 25, 2017
@matthewfarwell
Copy link
Author

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?

@SethTisue
Copy link
Member

@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.

@matthewfarwell
Copy link
Author

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: _*) ?

SethTisue added a commit that referenced this pull request Aug 1, 2017
as per discussion on #198
@SethTisue
Copy link
Member

@matthewfarwell looks like removing the plugin isn't necessary, so I was able to unfork in a2a81ce

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