I think its best if we follow the conventions too. However, do we have the required permissions to be able to move the feature I created into a different directory? It would be nice to get that moved out. We should also pre-create the test and documentation directories ready for when we use them.
Has anyone got experience in writing unit tests for plugins? I've never written any myself before. Also, automated CI builds would be good - is there a way to tap into the main WTP CI process?
Cheers,
Doug
----- Original Message ----
From: David M Williams <david_williams@xxxxxxxxxx>
To:
WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
Sent: Sunday, 16 December, 2007 4:22:29 PM
Subject: Re: [wtp-incubator-dev] Start made on code
One thing we do in WTP, which isn't
critical, but kind of nice, is that we put code plugins in the "plugins"
directory, features in a "features" directory, and unit test
plugins in a tests directory, examples, in "examples", documentation
in a documentation in "documentation". This is mostly just
to add a little structure to the otherwise large number of plugins, but
also since, presumably, things like "features" can be many things
(e.g. used just to build, used for update sites, mixed and matched ...
maybe we'll want a "core-only non-ui" feature someday, etc.
So ... just helps imposes a bit of order.
Do you others on the incubator project
think this would be a good convention to follow? Or, do you find it objectionable?
Thanks,
| From:
| DOUG SATCHWELL <doug.satchwell@xxxxxxxxxxxxxx>
|
| To:
| WTP Incbutor <wtp-incubator-dev@xxxxxxxxxxx>
|
| Date:
| 12/16/2007 07:12 AM
|
| Subject:
| [wtp-incubator-dev] Start made on code |
I've been busy and have made a lot of code - creating
the following plugins (roughly following the JDT naming conventions):
org.eclipse.wst.xsl.debug - contains the debugger and invoker code (no
activator required)
org.eclipse.wst.xsl.debug.ui - contains the UI launching and debugging
code
org.eclipse.wst.xsl.launching - contains the non-UI launching and debugging
code
org.eclipse.wst.xsl.xalan - contains the xalan library invoker and debugger
code
org.eclipse.wst.xsl.feature - wraps up the above plugins
Note that we already have a org.eclipse.wst.xsl.launch plugin. This contains
all of the Orangevolt code, but it was too difficult to integrate with
it straight off, so the plan is to integrate the org.eclipse.wst.xsl.launch
into org.eclipse.wst.xsl.launching, and then deprecate org.eclipse.wst.xsl.launch.
In particular we want the following from org.eclipse.wst.xsl.launch:
- console line tracker
- launch shortcuts (including class that looks better)
- contextual launch
- keywords
- launch config export
- anything else I've missed
I think it would be best to leave this conversion to Lars when he begins
work on this project. I will also continue to work on the invoker and debugger
for a while.
Jesper - do you need any of the X-Assist stuff (builder, hyperlinking etc.)
for your validation code? If so, just let me know and I will make it available.
Thanks,
Doug.
_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
