Closed daust closed 4 years ago
Works for Eclipse now. I had to create resource filters for the embedded jetty so that we don't get so many irrelevant error messages. Also, I had to exclude duplicate jar files from the local gradle cache: (it.path.contains('commons-lang-2.6.jar') && it.path.contains('.gradle/caches')) || (it.path.contains('commons-logging-1.1.1.jar') && it.path.contains('.gradle/caches'))
When you want to contribute as a developer, you can work with any Java development environment. When you are using Eclipse, IntelliJ IDEA, Visual Studio or Xcode, there are additional plugins for Gradle to simplify the generation of the respective project files for each environment:
Eclipse
Generates Eclipse project files for the build that can be opened by the IDE. This set of plugins can also be used to fine tune Buildship’s import process for Gradle builds.
IntelliJ IDEA
Generates IDEA project files for the build that can be opened by the IDE. It can also be used to fine tune IDEA’s import process for Gradle builds.
Visual Studio
Generates Visual Studio solution and project files for build that can be opened by the IDE.
Xcode
Generates Xcode workspace and project files for the build that can be opened by the IDE.
For now we will focus on the Eclipse plugin.