我怎样才能在gradle BUT中覆盖源目录,只针对这个烦人的子项目

时间:2012-06-21 00:32:41

标签: gradle

我们有一个主要项目和两个子项目。其中一个子项目是具有“独特”构建结构的playframework。如何覆盖源目录但仅限于该子项目,以便所有其他项目都使用源目录src / main / java等的标准布局。

我尝试了第一个不起作用的答案和我的目录结构

 stserver
     build.gradle (1)
     project1
     webserver
         build.gradle (2)

第二个gradle文件是这个

sourceSets.main{
  java.srcDirs = ['app']
}

task build << {
  println "source sets=$sourceSets.main.java.srcDirs"
}

当我运行它时,它打印出stserver / app作为我的srcDir而不是stserver / webserver / app ????我在这里做错了什么?

感谢, 迪安

1 个答案:

答案 0 :(得分:2)

请看看彼得建议的文件。我已经准备好了build.gradle我正在使用Play Framework 2.0~,所以我将在此处分享,希望您能找到一些有用的设置提示。

我的项目结构:

+- master/
  +- build.gradle  <-- contains common setup, 
                       and applies 'java' plugin to all subprojects
+- ui/             <-- project using Play framework
  +- build.gradle  <-- excerpt from this file is posted below

build.gradle

的摘录
repositories{
  maven{
    //Play dependencies will be downloaded from here
    url " http://repo.typesafe.com/typesafe/releases"
  }
}

//Optional but useful. Finds 'play' executable from user's PATH
def findPlay20(){
  def pathEnvName = ['PATH', 'Path'].find{ System.getenv()[it] != null }
  for(path in System.getenv()[pathEnvName].split(File.pathSeparator)){
    for(playExec in ['play.bat', 'play', 'play.sh']){
      if(new File(path, playExec).exists()){
        project.ext.playHome = path
        project.ext.playExec = new File(path, playExec)
        return
      }
    }
  }
  throw new RuntimeException("""'play' command was not found in PATH.
Make sure you have Play Framework 2.0 installed and in your path""")
}

findPlay20()

configurations{
  //Configuration to hold all Play dependencies
  providedPlay
}

dependencies{
  providedPlay "play:play_2.9.1:2.0+"
  //Eclipse cannot compile Play template, so you have to tell it to
  //look for play-compiled classes
  providedPlay files('target/scala-2.9.1/classes_managed')

  //other dependencies
}

sourceSets.main{
  java.srcDirs = ['app', 'target/scala-2.9.1/src_managed/main']
  //Make sure Play libraries are visible during compilation
  compileClasspath += configurations.providedPlay
}

//This task will copy your project dependencies (if any) to 'lib'
//folder, which Play automatically includes in its compilation classpath
task copyPlayLibs(type: Copy){
  doFirst { delete 'lib' }
  from configurations.compile
  into 'lib'
}

//Sets up common play tasks to be accessible from gradle.
//Can be useful if you use gradle in a continuous integration 
//environment like Jenkins.
//
//'play compile' becomes 'gradle playCompile'
//'play run' becomes 'gradle playRun', and so on.
[ ['run',     [copyPlayLibs]],
  ['compile', [copyPlayLibs]],
  ['clean',   []],
  ['test',    []],
  ['doc',     [copyPlayLibs]],
  ['stage',   [copyPlayLibs]] ].each { cmdSpec ->
    def playCommand = cmdSpec[0]
    def depTasks = cmdSpec[1]
    task "play${playCommand.capitalize()}" (type: Exec,
                                            dependsOn: depTasks,
                                            description: "Execute 'play ${playCommand}'") {
     commandLine playExec, playCommand
    }
}

//Interate playClean and playCompile task into standard
//gradle build cycle
clean.dependsOn "playClean"
[compileScala, compileJava]*.dependsOn "playCompile"

//Include Play libraries in Eclipse classpath
eclipse {
  classpath {
    plusConfigurations += configurations.providedPlay
  }
}

注意:我刚刚从现有的更大的gradle文件中提取了上述文件,因此可能会遗漏一些内容,所以无法保证:)无论如何都希望它有用。祝你好运。