This is the email that I sent out a while ago. Sorry I did not get a
chance to figure out an Ant script.
As for intellj, you just open the plugin project, right click it, and
there is an item ("prepare" or something) that you can use. Writing
an Ant target should not be too hard.
---------- Forwarded message ----------
From: Shane Duan <[EMAIL PROTECTED]>
Date: Nov 20, 2006 11:33 PM
Subject: How to Build Eclipse Plugin
To: [email protected]
Hi,
I have just taken a look at the three projects for building jBehave
Eclipse plugin, and my painful memory came back.
So, here is how we made it work. Grab something because you are in
for a wild ride:
To build Eclipse plugin, open the projects, and open the site.xml file
in jbehave-site project. It will be opened in an editor, click on the
first tab "Site Map" and you should be able to build the plugin by
clicking on "Build All" button. After it is done, you should have a
'features' directory and a 'plugins' directory created at the root of
jbehave-site project.
The site.xml, "features" directory and "plugins" directory are the
ones that you need to upload to the website for others to download.
The url that you are going to use should match the value specified in
the feature.xml under the jbehave-feature project.
What this means is that if you want to build it and install it
locally, you will have to change the value for the field "Update Site
URL" manually, and don't forget to change it back before you build for
deployment.
The following is a brief explanation of what the configuration files are.
In order to build an Eclipse plugin with an update site, you will need
three projects. One for the plugin itself, one for the feature
information, and one for the site.xml.
Plugin project contains the real code and a plugin.xml file. You can
open it in Eclpse editor and take a look. After we figured out ALL 7
(yes, seven) entry points that you need to create in order to create a
run configuration that can be launched through a shortcut, what is
left is to make sure that you update the version number (which is
0.5.2 right now).
Feature project contains the feature information. I think in this
way, you can bundle several plugins together and make it into a
'feature' of your product. For us, you just need to make sure that
the version number in the feature.xml is correct. Eclipse also
provide an editor to update this file. But I think for jBehave
plugin, it would be easier to manually edit it.
Site project is the one that builds the site.xml. And again, the name
of the jar file should match the version.
On each editor there is a link saying "synchonize versions" but I
never figured out how to get it work.
Looking at the generated file, I think we can cheat by launching
eclipse to build the class files in the plugin project (or we can even
create an Ant target to do that somehow), and just jar up the plugin
project and feature projects in the the appropriate jar files.
Hope this helps.
--
Shane
http://www.shaneduan.com
--
Shane
http://www.shaneduan.com
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
