subproject

Gradle subproject not included in classpath

由 只愿长相守 提交于 2019-12-09 10:33:57
问题 We have a set up with 2 project, 1 main and 1 subproject, they are Java projects. They are all under the same directory. Here is how the directory structure looks like : ./dev ./Project_A build.gradle settings.gradle ./Project_B build.gradle Project_A includes Project_B. Project_A settings.gradle looks like : includeFlat 'Project_B' Project_A build.gradle contains : compile project(':Project_B') The issue Project_A misses the classes from Project_B when compiling from command line ( gradlew

Play Framework 2.2.1 - Adding non-play Java Project as sub-project

由 岁酱吖の 提交于 2019-12-08 06:08:51
问题 I am trying to add a non-play Java project as a sub-project. The main project is a Play Java Application and the sub-project is in the same directory as the main-project. I am following instruction given here. My build.sbt looks like import play.Project._ name := "main-project" version := "1.0" libraryDependencies ++= Seq(javaJdbc, javaEbean) playJavaSettings lazy val mainProject = project.in(file(".")) .aggregate(subProject) .depends(subProject) lazy val subProject = project.in(file("../sub

Why does git say a sub project is dirty if I do not have any sub-modules in my repository?

由 一世执手 提交于 2019-12-08 02:56:14
问题 Its a new git repository and all I've done is added a whole lot of code to it. However, it tells me: +Subproject commit 62402f4a7e3aa34a5f22532c8c699836b7ae4967-dirty Based on this question, this seems to imply that this has something to do with sub modules and is to be expected if you have sub modules. However, I do not have any. Why am I getting this message and how do I get of it? 回答1: Make sure there aren't some unintended .git folders in subdirectories of your repo. 来源： https:/

Play Framework 2.2.1 - Adding non-play Java Project as sub-project

由 别等时光非礼了梦想. 提交于 2019-12-08 01:54:26
I am trying to add a non-play Java project as a sub-project. The main project is a Play Java Application and the sub-project is in the same directory as the main-project. I am following instruction given here . My build.sbt looks like import play.Project._ name := "main-project" version := "1.0" libraryDependencies ++= Seq(javaJdbc, javaEbean) playJavaSettings lazy val mainProject = project.in(file(".")) .aggregate(subProject) .depends(subProject) lazy val subProject = project.in(file("../sub-projects/sub-project-1")) Here is my directory structure D: |-- projects | |-- main-project | |-- sub

Removing subproject commit from github

由 女生的网名这么多〃 提交于 2019-12-07 17:55:37
问题 I have two repositories namely A and B . By mistake I cloned repo B inside A on my machine. I removed all the code from the repo B but when I pushed and merged my code from A on origin, it also shows a subproject commit B on Github repo. I want to remove the subproject commit from my master on origin. Will these steps work? 1. rmdir B (on my local repo A) 2. Pushing my repo A to origin 3. Merging 回答1: Since GitHub displays B as a gray folder within A repo, that means B has been added to A as

Removing subproject commit from github

由 这一生的挚爱 提交于 2019-12-06 02:43:53
I have two repositories namely A and B . By mistake I cloned repo B inside A on my machine. I removed all the code from the repo B but when I pushed and merged my code from A on origin, it also shows a subproject commit B on Github repo. I want to remove the subproject commit from my master on origin. Will these steps work? 1. rmdir B (on my local repo A) 2. Pushing my repo A to origin 3. Merging VonC Since GitHub displays B as a gray folder within A repo, that means B has been added to A as a submodule. That gray folder is a gitlink , a special entry in the index . See " How do I remove a Git

SBT: How to define dependencies of subprojects in subprojects' build.sbt files?

由 馋奶兔 提交于 2019-12-04 16:16:39
The following build.sbt file works, but it defines the dependencies of all subprojects: name := "myproject" version := "1.0" scalaVersion := "2.11.8" libraryDependencies ++= Seq( "org.scalafx" %% "scalafx" % "8.0.60-R9" ) lazy val aLib = (project in file("lib/a")) lazy val bLib = (project in file("lib/b")) .dependsOn(aLib) .dependsOn(cLib) lazy val cLib = (project in file("lib/c")) .dependsOn(aLib) lazy val myApp = (project in file("myapp")) .dependsOn(aLib) .dependsOn(bLib) .dependsOn(cLib) .aggregate(aLib, bLib, cLib) Since each subproject (directories lib/a, lib/b, lib/c, myapp) has its own

Gradle subproject name different than folder name

由 99封情书 提交于 2019-12-04 08:07:31
问题 I have a couple of subprojects that are part of a multi-project build (flat hierarchy). I want to set the name on them to be different than their folder name. However in include (setting.gradle) it has to have the folder name otherwise it won't find it (same for the compile project (':ProjectName')). If I attempt to set project.name it tells me that is read-only. The reason is that we are converting from Ant and would like to keep the same name for Eclipse IDE. As far the artifacts go, we use

How to configure a subproject dependency in Maven without deploying jars?

由 落爺英雄遲暮 提交于 2019-12-04 00:20:30
I googled this and it seems that no one has an answer, yet it seems like such an elementary thing that it should be possible. I have the following project structure: parent ---sub-project1 ---sub-project2 sub-project2 needs to have sub-project1 as a dependency. So I have this in sub-project2's pom: <dependencies> <dependency> <artifactId>sub-project1</artifactId> <groupId>mygroup</groupId> <version>1.0-SNAPSHOT</version> </dependency> .... When I do this, Maven tries to dowload the sub-project1.jar file, which does not exist because it's not ready for the repo yet. I tried to put a <scope

Specifying a subproject's Configuration in Xcode

由 丶灬走出姿态 提交于 2019-12-03 08:06:19
问题 I have an Xcode project ( A ) referencing another project ( B ). By default (as far as I understand it) Xcode will implicitly build the configuration for the B dependency that matches the configuration of the A 's target (e.g., "Debug"). But what if I want, say, A to build as "Debug" and the B to build as "Release"? How would I go about specifying that in Xcode? 回答1: I don't know of any easy approach, but you can brute-force it by calling xcodebuild directly for the dependency with a "Run
订阅 subproject