SAS Java Projects are
created with a default set of JAR files in their SAS Repository. The
dependencies for these JAR files are resolved automatically. Although
these default JAR files and their dependencies are sufficient for
many projects, some projects require additional JAR files. For example,
the SAS AppDev Studio templates add JAR files that are not included
by default. Because the SAS Repository of a migrated project might
have been customized, there might be issues that should be addressed
when migrating from SAS AppDev Studio 3.41 to 4.4.
Although all the JAR
files in the SAS Version Jar Repository have new dates for SAS 9.4,
the base name of the JAR files has remained largely unchanged. If,
in the SAS Repository configuration, all the JAR files are set with
Latest as their Match Rule, it is likely that no action needs to be
taken. For projects that do need updating, it is not practical to
provide instructions about what is needed without knowing the specifics
of the project.
You should use the Report
and Jar Relationships tools in the
SAS Repository Configuration dialog
box to see whether there are problems that need to be addressed, especially
if the
Discover dependencies automatically option
is disabled. Internal dependencies between existing JAR files and
the inclusion of new JAR files might require the configuration be
updated.
For details about configuring
the SAS Repository in a project, see Chapter 8, Managing the Jars
in a Project, in the
SAS AppDev Studio 4.4 Eclipse Plug-ins:
User’s Guide, which is available at
support.sas.com/rnd/appdev/.