This section provides notes on Java migration.
Project Java versions are specified below.
JRE system library in the Java build path
Project Facets
Compiler conformance level of the Java compiler
If a project was updated automatically with the standard workbench, basically the settings are as shown below. If a different version of Java is being used, it must be modified individually.
Java version before migration | Java version after migration |
|---|---|
6 | 6 |
5 or earlier | 6 |
Note
With the standard workbench, the above conversion may not be performed, depending on the migration source workspace or project settings. After migrating, check the Java version so that there are no conflicts with the project facet settings.
For example: When the [Java Build Path] > [JRE System Library] setting is [Workspace default JRE], [JRE System Library] conforms to the migration destination workspace setting.
The predefined libraries that can be used are shown below.
Predefined library name | Remarks |
|---|---|
EAR Library | |
JBK Library | Former compatible libraries are not supported. |
JRE System Library | |
JSF Library | |
JUnit | |
Web Application Library | |
Server Runtime | J2EE libraries are converted to server runtimes when projects are automatically updated. The old versions of server runtime and target runtime are changed to the latest versions. |
Plug-in Dependencies | |
User Library | |
Connectivity Driver Definition | |
Fujitsu XML Library | Not newly added because this is not a recommended function. |
Predefined libraries other than the above provided by older versions are deleted at the time of automatic update of projects because these functions are not provided by the latest version. If predefined libraries for which functions are not provided by the latest version are used, a compile error occurs. Therefore, the implementation must be changed to use an alternative method.
In principle, the workbench can perform debugging even if there are no archive files. Therefore, the default is that archive files are not automatically created during a build.
If archive files need to be created for distribution to an operating environment, refer to "6.2.7 Distributing to the Operating Environment".
Point
An Ant script for creating archive files is created by performing an automatic update of a project.
By registering this Ant script as an Ant build from [Builders] in the project properties, archive files can be created automatically during the build.
