About this task
When you have tested your user-defined pattern and you are
satisfied with its content and quality, package it into a
pattern archive so that you can distribute
it to your pattern users.
You
can include additional plug-in projects in your
pattern archive. For example, if your user-defined
pattern includes a user-defined editor, you can include the code plug-in
project that contains the code for the editor in your
pattern archive. If you want to include a
JAR archive package in your pattern archive, you must first convert
the JAR file to a plug-in. To convert a JAR file to a plug-in, complete
the following steps:
- Click .
- Expand Plug-in Development and select Plug-in
from Existing JAR Archives.
- Click Next to start the New Plug-in
from Existing JAR Archives wizard. Navigate through the
wizard, completing the fields as required. Click Finish.
If the code in the JAR plug-in is required by a code plug-in
in your user-defined pattern, you must ensure that the
MANIFEST.MF file
of your code plug-in includes a dependency to the JAR plug-in.
Results
The pattern plug-ins and features are generated in the workspace.
If the plug-ins already exist in the workspace, you are asked if you
want to overwrite them; if you have already created the
.doc plug-in
or your translated files, you might choose not to overwrite the plug-ins.
The pattern is temporarily displayed in the
Patterns Explorer view.
A
pattern archive with the extension
.patternzip is
created in the target location.