在线时间:8:00-16:00
迪恩网络APP
随时随地掌握行业动态
扫描二维码
关注迪恩网络微信公众号
开源软件名称(OpenSource Name):spring-attic/eclipse-integration-gradle开源软件地址(OpenSource Url):https://github.com/spring-attic/eclipse-integration-gradle开源编程语言(OpenSource Language):Java 99.6%开源软件介绍(OpenSource Introduction):eclipse-integration-gradle is no longer actively maintained by VMware, Inc.Eclipse Integration GradleThis project is no longer under active development. Please use BuildShip instead. The Eclipse-Integration-Gradle project brings you developer tooling for Gradle into Eclipse. It comes with Spring UAA (User Agent Analysis), an optional component that help us to collect some usage data. This is completely anonymous and helps us to understand better how the tooling is used and how to improve it in the future. It also comes with the SpringSource Dashboard as an optional component, which brings you up-to-date information about SpringSource-related projects as well as an easy-to-use extension install to get additional tooling add-ons, like the tc Server Integration for Eclipse, the Cloud Foundry Integration for Eclipse, Grails IDE and Groovy Eclipse. Requirements (for version 3.0.0 of the Gradle tooling)Either one of the following:
If you want support for editing .gradle files a compatible Groovy Eclipse installation is required. STS 3.0.0 requires Groovy Eclipse 2.7.0. The Gradle tooling should be usable without Groovy Eclipse, but some functionality (related to editing gradle files) will not work. DocumentationDocumentation for the functionality offered by Eclipse-Integration-Gradle tooling is available from our project's GitHub Wiki. Installation instructions:Installing from the STS dashboard:The easiest way to install is from the STS Dashboard "Extensions" page.
Installing Gradle Tooling from update siteAlternatively you can install from update sites. The following update sites are available:
Pasting the above URLs into a web browser will not work. You need to follow the instructions given below to use an Eclipse update site.
If you follow this installation procedure in a plain Eclipse, this will install the STS Dashboard. This gives you an easy way to subsequently install Groovy Eclipse as well. See instructions on Installing from the STS Dashboard above. Offline InstallationUse Update Site Archive for STS from https://spring.io/tools/sts/all Questions and bug reports:If you have a question that Google can't answer, the best way is to go to the StackOverflow. There you can also ask questions and search for other people with related or similar problems (and solutions). With regards to bug reports, please go to the Github issue tracker. Developing Eclipse Integration GradleThe remainder of this documents expects a familiarity with Eclipse architecture and how plugin development works. If you are not already familiar with Eclipse development, then you may want to read some tutorials about the Eclipse plugin architecture and how to develop with it. A good start is here: https://www.ibm.com/developerworks/library/os-eclipse-plugindev1/. Setting up the Development Environment and Target PlatformThe instructions here are tested starting with a 'clean' copy of Eclipse 4.4 JEE. It is also possible to setup a similar environment based on older versions of Eclipse. First we will start by setting up a suitable instance of Eclipse. This instance will serve a double purpose:
Steps:
Getting the source codeThe source code for this project is hosted on github. You can use egit (Eclipse Integration for Git) or commandline git tools to get the source code on to your machine. To get the source code onto your machine:
or if you are a committer:
Importing the source code into EclipseThe source code consists of a single root project and several sub-projects nested within it. You can use either 'EGit' or the generic Eclipse 'Import Existing Projects' wizard. However both wizards are tripped up by the nested project structure. As soon as the Wizard sees the root
After importing the sub-projects, reinstate the root
If you want to, you can now import the root project as well. Getting and Updating the Tooling API JarsAt this point you likely have errors in your workspace like 'The project cannot be build until build path errors are resolved'. Our tools are built on top of the Gradle Tooling API. However the Tooling API jars are not included in the git repository. They have to be downloaded and placed into Open the 'Gradle Tasks' View (via Window >> Show View menu).
You can also do this on the commandline:
This runs both If you do this on the commandline you will need to manually refresh the Note that the script only downloads the jars and updates the plugin After this all compile errors should disappear. (Note: In Eclipse 4.2 I have on occasion noticed that you need to force a workspace rebuild by cleaning the project before errors actually disappear). Running the tests inside of EclipseTo run the regression tests inside of Eclipse. Find the class 'AllGradleCoreTests' and run it as a 'Junit Plugin Test'. You can also run the smaller testsuites individually in the same way. Notes:
Building Gradle IDEThe Gradle IDE project uses Maven Tycho to do continuous integration builds and to produce p2 repos and update sites. To build the project yourself, you can execute:
This will use maven to compile all Gradle-IDE plugins, excluding test bundles and package them up to produce an update site for a snapshot build. The update site will be located in If you want to run tests during your build, then remove ContributingCode of ConductThis project adheres to the Contributor Covenant link:CODE_OF_CONDUCT.adoc[code of conduct]. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected]. Get InvolvedHere are some ways for you to get involved in the community:
Contributor License AgreementBefore we accept a patch or pull request we will need you to sign the contributor's agreement. Signing the contributor's agreement does not grant anyone commit rights to the main repository, but it does mean that we can accept your contributions, and you will get an author credit if we do. Active contributors might be asked to join the core team, and given the ability to merge pull requests. |
2023-10-27
2022-08-15
2022-08-17
2022-09-23
2022-08-13
请发表评论