How to simplify the development and unit testing procedures. - Eclipse Plugin Development [message #53039] |
Mon, 09 June 2003 03:26  |
Eclipse User |
|
|
|
We use Eclipse framework to develop our product as eclipse plugin.
We face issues with development and unit testing the same. The details
follows
Our plugin.xml, .properties reside in the following folder in CVS.
\<BRANCH>\prod_src\configuration\mb\plugin.xml
\<BRANCH>\prod_src\configuration\mb\plugin.properties
and our java code resides at:
\<BRANCH>\prod_src\java_src\com\rtg\mb (and in its subfolders)
and the icons for the product "mb" is at
\<BRANCH>\prod_src\java_src\com\rtg\mb\resource\images
And with the above structure, our installer will create the plugin at the
deployment stage like:
com.rtg.mb
--plugin.xml (copy of configuration\mb\plugin.xml)
--plugin.properties (copy of configuration\mb\plugin.properties)
--mb.jar (result of make command & contains the class files)
--icons (contains the gifs, a copy of mb\resource\images folder which is
mentioned above
and the plugin.xml will have references from this icons folder for
setting the icons in toolbar)
So, eclipse needs the plugin.xml, .properties and jar files in single/at
relative location.
How to unit test under this scenario?
-Should we simulate similar to deployment (i.e build the product, copy the
jar
files, icons, plugin.xml & .properties, and then start the eclipse)
-If we create the project at java_src folder, eclipse expects that
plugin.xml to be
at the same folder level(java_src) or have a link.
If it is at the same folder level(java_src), the plugin.xml
- has to be duplicated(copied from configuration\mb to java_src folder)
- icon references has to be changed from (icons\) to
(com\rtg\mb\resource\images) folder.
- And another issue whenever we change this copy, we need to sync this
with the CVS copy and vice versa.
Also, since we develop more than one plugin, we cannot have the CVS copy of
plugin.xml at the java_src level, we
need to place in a different folder. For this reason only, we placed it in
\prod_src\configuration\mb folder.
Moreover, we are unable to create the project at "mb"
folder(java_src\com\rtg\mb) and specify the classpath from "com"
folder level.
Give us a solution that could ease our development and unit testing
procedures.
|
|
|
Re: How to simplify the development and unit testing procedures. - Eclipse Plugin Development [message #53705 is a reply to message #53039] |
Tue, 10 June 2003 06:46  |
Eclipse User |
|
|
|
Originally posted by: daniel.megert.gmx.net
MorPheus wrote:
>We use Eclipse framework to develop our product as eclipse plugin.
>We face issues with development and unit testing the same. The details
>follows
>
>Our plugin.xml, .properties reside in the following folder in CVS.
>
>\<BRANCH>\prod_src\configuration\mb\plugin.xml
>\<BRANCH>\prod_src\configuration\mb\plugin.properties
>
>and our java code resides at:
>\<BRANCH>\prod_src\java_src\com\rtg\mb (and in its subfolders)
>
>and the icons for the product "mb" is at
>\<BRANCH>\prod_src\java_src\com\rtg\mb\resource\images
>
>And with the above structure, our installer will create the plugin at the
>deployment stage like:
> com.rtg.mb
> --plugin.xml (copy of configuration\mb\plugin.xml)
> --plugin.properties (copy of configuration\mb\plugin.properties)
> --mb.jar (result of make command & contains the class files)
> --icons (contains the gifs, a copy of mb\resource\images folder which is
>mentioned above
> and the plugin.xml will have references from this icons folder for
> setting the icons in toolbar)
>
>
>
>So, eclipse needs the plugin.xml, .properties and jar files in single/at
>relative location.
>
>How to unit test under this scenario?
>
I assume you can run your plug-in out of the workspace using an Eclipse
launch configuration. To test plug-ins there is a separate JUnit PDE
plug-in available that helps you with plug-in testing:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt- ui-home/plugins/org.eclipse.jdt.junit/index.html
HTH
Dani
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.27709 seconds