Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 23.5

Eclipse Classic

General Information

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:	Eclipse Classic is an open source integrated development environment (IDE) and an extensible plugin system. Plugins must be loaded, integrated, and executed to equip Eclipse to handle Java software development. Eclipse is an open framework that has uses beyond that of a Java development environment by developing applications in Java and, using various plugins, other programming languages. This technology does not utilize a database.
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:	This technology has been assessed by the Section 508 Office and found non-conformant. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v23.3
Decision Date:	03/27/2023
Aliases:	Eclipse IDE
Introduced By:	Extended Tool List (ETL)
Vendor Name:	Eclipse

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
3.2	06/30/2006
3.3	06/29/2007
3.4	06/25/2008
3.5	06/24/2009
3.6	06/23/2010
3.7	06/22/2011
4.2	06/27/2012
4.3	06/26/2013
4.4	06/25/2014
4.5	06/24/2015
4.6	06/22/2016
4.7.x	06/28/2017
4.8.x	06/27/2018
4.9	09/19/2018
4.10	12/19/2018
4.13	09/19/2019
4.14	12/04/2019
4.16	06/04/2020
4.18	12/02/2020
4.19	03/03/2021
4.20	06/11/2021
4.22	11/24/2021
4.24	06/07/2022
4.26	11/23/2022
4.27	01/04/2023

Current Decision Matrix (03/14/2023)

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.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2022

CY2023

CY2024

Future>

Release

3.5

Unapproved

3.6

Unapproved

3.7

Unapproved

4.2

Unapproved

4.3

Unapproved

4.4

Unapproved

4.5

Unapproved

4.6

Unapproved

4.7.x

Unapproved

4.8.x

Unapproved

4.9

Unapproved

4.10

Unapproved

4.13

Unapproved

4.14

Unapproved

4.16

Divest
[1, 2, 3, 6, 7]

Divest
[1, 3, 6, 8]

Unapproved

4.18

Divest
[1, 2, 3, 6, 7]

Divest
[1, 3, 6, 8]

Unapproved

4.19

Divest
[1, 2, 3, 6, 7]

Divest
[1, 3, 6, 8]

Unapproved

4.20

Approved w/Constraints
[1, 2, 3, 6, 7]

Divest
[1, 2, 3, 6, 7]

Divest
[1, 3, 6, 8]

Divest
[9, 10, 11, 12, 13, 14]

Unapproved

4.22

Approved w/Constraints
[1, 2, 3, 6, 7]

Divest
[1, 3, 6, 8]

Divest
[9, 10, 11, 12, 13, 14]

Unapproved

4.24

Unapproved

Approved w/Constraints
[1, 3, 6, 8]

Divest
[9, 10, 11, 12, 13, 14]

Unapproved

4.26

Unapproved

Approved w/Constraints
[9, 10, 11, 12, 13, 14]

4.27

Unapproved

Approved w/Constraints
[9, 10, 11, 12, 13, 14]

Decision Constraints


[1]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[2]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[3]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

[4]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[5]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[6]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[7]	This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle.

[8]	This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - IBM. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - IBM.

[9]	This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - IBM. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - IBM. Per the Security Assessment Review, users must abide by the following constraints: To mitigate, the ISSO shall educate and prohibit users from using the integrated cloud service capability until the VA Cloud Security Requirements have been met and the affected A&A package has been appropriately updated.. To mitigate, the administrator shall control the versioning of Eclipse IDE version 2022.x software and do not allow users to install unapproved versions. To mitigate maintenance and support will be provided for the Open-Source Software used within Eclipse IDE version 2022.x as per the applications lifecycle. To mitigate, administrators shall disable features within the GUI and manage software sites.

[10]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the VA OIT Product Engineering team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[11]	The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website.

[12]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

[13]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[14]	Users should check with their supervisor, Information System Security Officer (ISSO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not approved and the user should take the proper steps to decline those installations.

Note:

At the time of writing, version 4.27 is the most current version, released 03/02/2023.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	Downloads \| Release Notes		This webpage outlines the release notes for the technology.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Eclipse Workbench	This component is the desktop development environment.
Equinox OSGi	This component is a set of bundles that implements various optional Open Services Gateway Initiative (OSGi) services and other infrastructure services for running OSGi-based systems.
JFace	This component is a user interface (UI) toolkit with classes for handling many common UI programming tasks.
Platform Runtime	This component provides support for the runtime platform, core utility methods and the extension registry.
Standard Widget Toolkit (SWT)	This component is a portable widget toolkit.


Application Technology Development Tools	Integrated Development Environment (IDE)

- The information contained on this page is accurate as of the Decision Date (03/27/2023).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 23.5

General Information

Vendor Release Information

Current Decision Matrix (03/14/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 23.5

General Information

Vendor Release Information

Current Decision Matrix (03/14/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES