Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 20.4

SpringSource Tool Suite (STS)
SpringSource Tool Suite (STS) Technology

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: SpringSource Tool Suite (STS), (formerly known as Spring Eclipse Plugin), provides an Eclipse based development environment for building Spring Framework enterprise applications. In addition, to support for the core Spring framework, STS also provides visual editors, project validators, and Spring Dashboard for other projects such as Spring Roo, Grails, Groovy, Gradle, tcServer, and Spring Insight. STS provides a ready-to-use environment to implement, debug, run, and deploy Spring applications, including integrations for Pivotal tc Server, Pivotal Cloud Foundry, Git, Maven, and AspectJ, and comes on top of the latest Eclipse releases.

Note: The approved VA environments for Java development are Eclipse, myEclipse and Rational Software Developer.
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:
Decision: Prohibited. This entry is not (currently) permitted to be used under any circumstances.

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v13.11
Decision Date: 11/01/2013
Introduced By: TRM Analysis
Vendor Name: SpringSource
- The information contained on this page is accurate as of the Decision Date (11/01/2013).