几个月来,我们一直在使用Buildship 1.X以及一些手动.launch / tasks来构建每个开发环境的Eclipse / WTP配置文件。我目前正在尝试迁移到使用Buildship 2(我希望我们不再需要手动位。)
然而,当我通过buildship / gradle导入导入项目(此时有0个eclipse配置文件)时,子项目通过' Libraries'而不是作为' Projects' (见下图。)相反,如果我使用gradle的eclipse任务来生成eclipse配置文件(即.classpath),那么配置最终会像我期望的那样结束。这是Buildship的当前限制,还是我需要在gradle文件中做一些不同的事情来强制Buildship将它们作为项目引入?
最终我不知道我应该关心这种差异,但我知道我收到编译器错误,说类子路径中缺少子项目中的类。只要我能解决这个问题,我就非常高兴。
可能有用的信息
settings.gradle:
rootProject.name = 'projectroot'
include 'Project2.0'
project(':Project2.0').name = 'projectx'
include 'the-platform'
include 'the-platform:central-repo:central-repo-common'
include 'the-platform:central-repo:central-repo-model'
include 'the-platform:central-repo:central-repo-persist'
include 'the-platform:central-repo:central-repo-service'
Project2.0 / build.gradle(摘录):
dependencies {
...
compile project(':the-platform:central-repo:central-repo-common')
compile project(':the-platform:central-repo:central-repo-model')
compile project(':the-platform:central-repo:central-repo-persist')
compile project(':the-platform:central-repo:central-repo-service')
...
}
答案 0 :(得分:0)