Databases
StackOverflow2013
Postsdbo
POSbt publish-local use strange repo structure
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSbt publish-local use strange repo structure
    text
    copied!<p>I published jar with sbt to local ivy repo (<code>${$HOME}/.ivy2</code>). Then i have changed the play config file such way, that play started to use default local ivy repo (the same <code>${$HOME}/.ivy2</code>). But play did not managed to find jar, that i published with sbt. I think i fount out why this happend.</p> <p>all other dependencies that play downloaded has structure like</p> <pre><code>ivy_home/cache/group_id/artifact_id/jars/artifact_id-version.jar e.g. /home/maxim/.ivy2/cache/com.typesafe.akka/akka-actor/jars/akka-actor-2.0.1.jar </code></pre> <p>but jar, that i published with sbt is located in</p> <pre><code>ivy_home/local/group_id/artifact_id/version/jars/artifact_id.jar e.g. /home/maxim/.ivy2/local/com.mkotolyov.test/server-core/1.1.1-SNAPSHOT/jars/server-core.jar </code></pre> <p>i googled, but didn't find how to config sbt to publish with "default" structure.</p> <p>my project in Build.scala</p> <pre><code>lazy val core = Project( "server-core", file("core"), settings = buildSettings ++ Seq( publishTo := Some(myProxyMavenRepo), publishMavenStyle := true, publishArtifact in Test := false, pomIncludeRepository := { _ =&gt; false }, resolvers := depResolvers, unmanagedResourceDirectories in Compile &lt;+= baseDirectory( _ / "src" ), libraryDependencies ++= Seq( config, sprayJson, scalatest, prettyTime, casbahCore, casbahCommons, casbahQuery, mysql, squeryl, postgresql, quartz ) ) ) </code></pre> <p>I have the flag <code>publishMavenStyle := true</code> but it is targeted only for common <code>publish</code>, and not to <code>publish-local</code>. Any way i have tried to remove it - nothing changes.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload