Teradata Project Preferences - Teradata Studio

Teradata Studio IDE Plug-in User Guide

Product
Teradata Studio
Release Number
15.12
Published
August 2016
Language
English (United States)
Last Update
2018-05-03
dita:mapPath
pts1468860020550.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-2043
lifecycle
previous
Product Category
Teradata Tools and Utilities

Teradata Project Preferences dialog is divided into three sections: Project Folders, Spring Version, and Project Libraries. To open preferences, select Window > Preferences > Teradata Tools Preferences > Teradata Project Preferences.

The Project Folders section allows you to define the source folders and output directory defaults for a Teradata Project. The section displays the Teradata Project standard values as the default values for each preference.
Folders Description
Source Java Path for source Java folder; for example, src/java.
Source Configuration Path for source configuration folder; for example, src/config.
Source Resource Path for source resource folder; for example, src/resource.
Source SQL Path for SQL source folder; for example, src/sql.
Test Java Path for Java test folder; for example, test/java.
Test Configuration Path for configuration test folder; for example, test/config.

In the Spring Version section, select which version of the Spring framework to use. These versions, Spring 3.05 and Spring 2.5.6, can be used with the classes generated by the Teradata iBatis (MyBatis) Wizard. If you select the Spring 3.05 radio button, the JAR files that support the Spring 3.05 and MyBatis frameworks are used to create the Teradata Project. If you select the Spring 2.5.6 version, the JAR files that support the Spring 2.5.6 and iBatis frameworks are used to create the Teradata Project. A Teradata Project created with these JAR files only supports the Spring 2.5.6 and iBatis frameworks.

The Project Libraries section enables you to set the default libraries needed for the Teradata Spring DAO Wizard and Java Wrapper Bean Wizard. When you create a Teradata Project, the system copies these libraries to the lib directory of the new project. Also, the system creates a user library for copied JAR files and adds it to the build path of the project.