This section outlines how to package your finished source code control extension as a JAR file that JDeveloper automatically loads on startup. This involves:
After you have created the JAR file, you can store it in your
directory to install your source code control client into JDeveloper. Using
an 'autoloading' JAR file means you and your users do not have to modify any
configuration files for the JDeveloper IDE to install the extension.
Note: For full details on how to package your source code control extension, see the JDeveloper online help.
A manifest file is an XML file that describes how your extension integrates into the JDeveloper IDE. You must include a manifest file in your JAR file to describe how the extension in that JAR should be installed into JDeveloper.
Note: We assume you want to package
your extension using JDeveloper. If not, you can also create the JAR file
from the command line. For more details on the format of a manifest file,
To create your manifest file in the JDeveloper IDE:
c:\jdev\myprojects\project1\src, you must be in
<?xml version = '1.0' encoding = 'windows-1252'?>
To create a JAR file in JDeveloper, you must use a deployment profile. To create a deployment profile in JDeveloper:
To deploy your JAR file to JDeveloper:
deploydirectory under your project directory (assuming you used the default options in step 4 of Creating a Deployment Profile above).
%JDEV_HOME%/jdev/lib/extthen restart JDeveloper.
If your source code control extension does not appear to work correctly:
jdevw.exe(Windows systems only). A console window appears at startup and will display any errors or exceptions that occur while trying to initialize your extension
If you believe your extension will benefit the wider community of JDeveloper users, we encourage you to make it available to them using OTN. For more details, see the OTN Extensions Exchange.