SAS Java Projects are
created with a default set of jars in their SAS Repository. The dependencies
for these jars are resolved automatically. Although these default
jars and their dependencies are sufficient for many projects, some
projects require additional jars. For example, the AppDev Studio templates
add jars that are not included by default. Because the SAS Repository
of a migrated project might have been customized, there are three
issues that should be addressed when migrating from AppDev Studio
3.4 to 3.41.
First, if the SAS Repository
includes the
sas.oda.tkts jar, remove
it. The jar will be present if the SAS JDBC DataBean Class template
was added to the project in AppDev Studio 3.4. This class supported
the SAS Table Server, which is not supported in SAS 9.3.
Second, if the SAS Repository
includes
spring.jar, remove it. For
SAS 9.3, this jar has been reorganized into a number of separate jars
distinguished by technology. The new jars start with the name
org.springframework, followed by an abbreviated name
to identify the technology (for example,
org.springframework.aop).
Finally, if the SAS
Repository configuration includes jars with Match Rules other than
Latest, update the rule for those jars to the version
that is available in the SAS 9.3 Version Jar Repository. All SAS jars
and many third-party jars will have version numbers that differ from
the SAS 9.2 version.
For details about configuring
the SAS Repository in a project, see Chapter 8, Managing the Jars
in a Project, in the SAS AppDev Studio 3.4 Eclipse Plug-ins User’s
Guide in the
SAS
AppDev Studio Developer's Site.