Remove scala version from publishing path - scala

I'm trying to deploy my sbt plugin to azure artifacts. Sbt adds the scala version to publishing path like in:
https://pkgs.dev.azure.com/orgname/projectname/_packaging/feed/maven/v1/com/test/plugin-name_2.12_1.0/0.0.1-SNAPSHOT/plugin-name-0.0.1.pom
Azure artifacts replies with a 400. I'm quite sure that's because of the added scala version. Is there a way remove the scala version from the path?
I read the documentation, looked up examples, but didn't find a solution.

Related

Different version of scala lib in build path and scala-ide

I have two versions of scala (2.11.4 and 2.10.4). Currently I work on project based on scala 2.10. I've changed version in project properties but ide still complains about it:
The version of scala library found in the build path (2.10.4.) is different from the one provided by scala IDE (2.11.4.). Make sure you know what you are doing.
I am using
Scala IDE build of Eclipse SDK
Build id: 4.0.0-vfinal-20141216-1226-Typesafe
Project config:
Any idea how fix that?
That complaint is a warning, not an error; all is fine. I suspect the message is mostly left over from when scala-ide used to only support working with a single version of scala in a single install (which was only fixed in 4.0)
Yes, you can use the multiple scala version support, as described in this blog post.
Once correctly configured, as you showed in the image, this is just a warning and therefore safe to ignore.

Build and modify hadoop 2.5.0 source code using eclipse

I'm trying to build and modify hadoop 2.5.0 source code using eclipse.
I've followed all instructions in this tutorial
http://blog.cloudera.com/blog/2013/05/how-to-configure-eclipse-for-hadoop-contributions/
and this one too http://wiki.apache.org/hadoop/HowToContribute.
But still I don't understand, how to build and test my modification directly from eclipse?
or if there is no way to do that, what is the best way to achive my goal to modify, build, and run my own modified version of hadoop?
Note:
*I've already successfully build hadoop using maven via ubuntu terminal previously, and run the package successfully also.
*I'm new in java, eclipse, and hadoop development
Thanks.

IntelliJ 404 scala lang

Ok, I need some help in setting up a Scala project with IntelliJ, I have download and installed the project successfully, but i have had issues when it comes to installing the Scala compiler itself, WHen i go to configure a new Scalaa project and choose to set the Scala home, I choose the download Scala option and i get the following error "downloading failed, connection failed with error 404: http://www.scala.lang.org/downloads.distrib/files/scala2.10.0+RC2.tgz" i have tried downloading the things, such as primefaces and jSF through intelij, and they all work fine, any suggestions?
Download Scala manually and just select proper directory in new project window.
http://www.scala-lang.org/download/
You should be using SBT to define and build your project. Among other things, it handles retrieving the Scala compiler and libraries. IDEA is similarly self-contained as far as its Scala plug-in's internal Scala compiler is concerned. By using SBT and IDEA (see below for connecting the two), the only thing not covered is a Scala REPL for use outside of either SBT or IDEA. If you're using a Mac, Homebrew includes a Scala formula. Because SBT retrieves the Scala compiler and libraries for the version of Scala you specified, everything is self-contained.
By far the best way to build and maintain IDEA project definitions for Scala projects is with the sbt-idea plug-in for SBT. Once you install that plug-in, which is trivial, you simply use the gen-idea SBT task it provides. When your dependencies change, you run gen-idea again to update the project.

Is every Scala project targeted at a particular sbt version?

I am trying to solve this problem that I am facing. I have sbt version 0.12.2 installed on my laptop but every time I go to my scala assignment folder and start sbt from command prompt it automatically tries to download sbt 0.12.1. I gathered from the
build.sbt
file that the project is targeted at scala version 2.10.1 but I couldn't find anything on the sbt version.
My question is: Is there such a thing as sbt target version? If there is how and where can I modify it?
Note: I can provide the build.sbt file if it helps in solving this problem.
Usually the version of SBT used by a project is specified in a properties file.
Try looking in project/build.properties.
See the "Getting Started" guide here.

The scala-tools Maven Repo Change: sbt Broken

Yesterday, the Typesafe repo (at http://scala-tools.org/repo-releases) appeared to be down. Today, the page says it is being 'sunsetted' in favor of being served from Sonatype. Problem is that my just installed version of sbt (from homebrew on a mac) is still looking at the old repo and it's failing with:
[info] Resolving com.eed3si9n#sbt-assembly;0.8.0 ...
[warn] module not found: com.eed3si9n#sbt-assembly;0.8.0
Changing the repo URLs for the project is simple: found that in Build.scala. But that does me no good because the assembly jar not being found is coming up before the build of the project gets triggered (inferring this). Then I found this thread here about having to explode the jar.
Ok, I fixed this by getting a resolvers definition from the sbt-assembly github readme. However, my question is, why is 0.8.0 of sbt-assembly not on the new sonatype repo??
New Releases Repo
Eugene simply hasn't pushed sbt-assembly up to Sonatype yet. More importantly, you're running with an outdated version of SBT. The Scala Tools hosting was never provided or supported by Typesafe. Rather, it was a service provided to the community by David Pollak (the creator of Lift). He has since decided to withdraw his involvement in the community, including the hosting for Scala Tools. This is why the repository is in "sunset mode". The latest versions of most Scala build tools (including SBT) no longer point to Scala Tools.
My advice would be to first upgrade to a newer version of SBT. Second, file an issue on sbt-assembly prodding Eugene to take the necessary steps to get the project into Sonatype's repositories.