logo
Tags down

shadow

Subproject does not fetch dependencies from Super POM


By : Sachin Jadhav
Date : September 15 2020, 07:00 AM
hop of those help? Entries inside are not dependencies. They are just standard versions for dependencies.
Dependencies need to be in the tag outside of .
code :


Share : facebook icon twitter icon

Subproject dependencies in SBT


By : user3084325
Date : March 29 2020, 07:55 AM
around this issue It turns out to have been a problem enabling the continuations plugin on project B. Here's my working configuration:
code :
class MyProject(info: ProjectInfo) extends ParentProject(info) {

  lazy val a = project("a", "a", new AProject(_))
  lazy val b = project("b", "b", new BProject(_), a)

  object Dependencies {
    lazy val scalaTest = "org.scalatest" % "scalatest_2.9.0" % "1.4.1" % "test"
  }

  class AProject(info: ProjectInfo) extends DefaultProject(info) with AutoCompilerPlugins {
    val scalaTest = Dependencies.scalaTest
    val continuationsPlugin = compilerPlugin("org.scala-lang.plugins" % "continuations" % "2.9.0")
    override def compileOptions = super.compileOptions ++ compileOptions("-P:continuations:enable") ++ compileOptions("-unchecked")
  }

  class BProject(info: ProjectInfo) extends DefaultProject(info) with AutoCompilerPlugins {
    override def compileOptions = super.compileOptions ++ compileOptions("-P:continuations:enable") ++ compileOptions("-unchecked")
  }

}

adding dependencies in subproject causes failure


By : Jamone Kelly
Date : March 29 2020, 07:55 AM
wish helps you This means that you have some other code which resolves (i.e. asks for its files) the compile configuration at configuration time. Something like configurations.compile.each { ... }, outside a task action. After a configuration has been resolved, you can't add further dependencies to it. Usually it's undesirable (and unnecessary) to resolve a configuration at configuration time. Among other things, it will slow down your build.
See the Gradle user guide for more information on the distinct phases of a Gradle build (initialization/configuration/execution).

Gradle transitive dependencies of a subproject used in another subproject


By : saikishore Konda
Date : March 29 2020, 07:55 AM
I wish this helpful for you you havn't defined a compile dependency in subProjectB. Not sure if i got your setup correctly, I think you need to add the dependency to someDependantJar? an you try adding a dependency in projectB on projectA
code :
configurations{
    compile ":someDependentJar:1.0"
}

Subproject dependencies in pants


By : Aleksandar Vasić
Date : March 29 2020, 07:55 AM
I wish this helpful for you So it turns out that the functionality I was hoping for was not supported by pants. At first, I followed the advice of a Yi Cheng in the comments and created a script to replace all subproject BUILD rules with those that are in relation to the root project. That script can be found here: https://github.com/brandonio21/pants-subproject-prep
The script was pretty limited, however, and was far from a workable solution. I have since changed pants upstream to support the behavior. The PR was here: https://github.com/pantsbuild/pants/pull/4088

sbt subproject cannot find it's dependencies


By : Louis Hacking
Date : March 29 2020, 07:55 AM
help you fix your problem If you want to use another project as a dependency (rather than its binary version) you can use project references. There are two types of references, ProjectRef or a simpler version of the ProjectRef, which is RootProject.
You should change your build definition to reference slick_auth as
shadow
Privacy Policy - Terms - Contact Us © 35dp-dentalpractice.co.uk