To include the Java™ source
code and classes in Archive files (JAR, WAR) use the following keyword
in the J2EE build script:
<property name="JAVA_SOURCE" value="YES"/>
If JAVA_SOURCE is set to YES, then include in MANIFEST directory
in JAR, WAR, or EAR. Provides audit and build map of parts included.
Note: When planning for J2EE applications in SCLM it is recommended
that you associate a separate SCLM type for each application component
of an EAR application. For example, an EAR can consist of multiple
web applications, such as WEB1.war, WEB2.war, WEB3.war and possibly
multiple EJB JAR application components. While each of these JAR,
WAR , components can be defined as separate projects in the Eclipse
Client workspace, all pf these application components will need to
be stored in the one SCLM project. It is important, however, to ensure
the application components are stored in SCLM under separate SCLM
types to avoid identical package/file name collisions in SCLM (especially
with special filenames such as .classpath .project etc). If SCLM types
have not already been added to the SCLM project to allow you to store
your projects in SCLM, contact your SCLM administrator to add the
necessary definitions and data sets.