Branch your Releng Folder

I am assuming that you are adopting J2SDK 5.0/EMF 2.3 on the HEAD branch of your project. If you haven't
already created a maintenance branch on your releng project (org.eclipse.emf.*.releng), you will want to do
that now. Otherwise, the changes you make in the following steps will apply to the builds of the maintenance
branch(es) of your previous release(s).

Just use the same branch name and root tag as you used the last time that you branched your source projects.

For example, if you're working on 1.0.x builds, use the tag R1_0_maintenance for both your code and your releng. The build page will assume that if you're building from R1_0_maintenance that your releng code will come from the same place. Running your build in debug mode will allow you to override this, if ever necessary in future, or if you ever want to use a tag instead of a branch. When branching your releng code, pick only the folder that your code resides in, such as, for OCL, /org.eclipse.emft/releng/ocl/. DO NOT tag the common code, /org.eclipse.emft/releng/common/.

If you don't have permission to branch this code, please contact your administrator.

If you had already branched, then chances are that the patch you applied for
bug 159212 also needs to be applied to your maintenance
branch. Check now that it was. In particular, searching for transientPropertiesFile should find no hits
(this patch did away with the transient properties file).

Use the J2SDK 5.0 Version of the Doclet

EMF provides a version of the doclet that creates the topics_Reference.xml file in your doc plug-in specifically
for J2SDK 5.0. First, try the following in build/javadoc.xml.template file:

In this case, because the doclet was responsible for generating an import TOC file, we need an alternative
way to do that. The following appended to the end of your build/antJavadoc.sh script will
suffice (see the attachment to bug 163877):

Update the JUnit Testing

Now that we are building with J2SDK 5.0, we also want to test with it. In the
builder/tests/configs/local/testing.properties file in your releng project, change the following
properties (they don't all appear together, as shown):

# instead of downloading and unpacking the JDK each time, just reuse the symlinked one in /opt/
vmExecutable=/opt/ibm-java2-1.4/jre/bin/java
#extra vm flags
Xflags=-Xj9 -Xms256M -Xmx256M

to the following:

# instead of downloading and unpacking the JDK each time, just reuse the symlinked one in /opt/
vmExecutable=/opt/sun-java2-5.0/jre/bin/java
#extra vm flags
Xflags=-Xms256M -Xmx256M

Set javac Source (javacSource) and Target (javacTarget) Properties

If you see the equivalent assignments with "1.4", change them to "1.5" or "5.0". If you see neither and your build fails (in the next step), try adding these directives where appropriate.

Start your Build

Voilà! You are now ready to test your build. Thanks to fixes by Nick in the automagic
selection of which branch of the releng project is used to build your component, you need only
to select in the build page:

and hit the Build button. If you do not already have an appropriate branch, release number, and
JDK combination in the drop-down-list, you will need to add it to the
www/emft/build.options.txt file in the eclipse.org CVS repository. e.g:

1.1.0=HEAD,/opt/sun-java2-5.0

Required Execution Environment

EMF 2.3 requires JDK1.5 as a minimum requirement. If you'd like to
force the same requirement on your plugins, add this line to the end of your
MANIFEST.MF files: