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 24.4

Maven Integration for Eclipse (M2Eclipse)
Maven Integration for Eclipse (M2Eclipse) 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: Maven Integration for Eclipse (M2Eclipse), enables Maven projects to be built using the Eclipse Integrated Development Environment (IDE) instead of the command line. M2Eclipse features functionality for launching Maven builds from within Eclipse, dependency management for Eclipse build path based on Maven`s Project Object Model, resolving Maven dependencies from the Eclipse workspace, automatic downloading of required dependencies from remove Maven repositories, wizards for creating new Maven projects, and a quick search for dependencies in Maven remote repositories.

This technology does not store data and does not require the use of a database.

Note: Rational Build Forge is the recommended software for enterprise-level software building.
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 Please see reference tab for more information concerning product versions.
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v20.11
Decision Date: 11/19/2020 at 15:53:51 UTC
Aliases: m2e, M2Eclipse
Introduced By: ARB
Vendor Name: Eclipse
- The information contained on this page is accurate as of the Decision Date (11/19/2020 at 15:53:51 UTC).