Home » Language IDEs » ServerTools (WTP) » WTP CVS Structure
| WTP CVS Structure [message #38825] |
Sat, 14 August 2004 10:03 |
Eclipse User |
|
|
|
I have outlined the initial CVS structure that is planned to appear on the
WTP project sometime next week. I would like to open it to community
comments before these appear on CVS. It is hard to remove things from CVS
so we would like to discuss it before we commit to structure that will
probably remain int that form for a good lentgh of time
CVS Structure
There are some preliminary decisions made:
a.. Seperate the sub projects.
b.. Seperate the components in the subprojects. Each component implies
ownership of soeme functionality for a group of committers (i.e. server,
sse). Organize the code into smaller collections so they are easier to
understand.
c.. Keep the names short (for 256 character limits on some systems) for
top level folders.
d.. Organize components into features, plugins, and tests.
Example:
/sse (Structured Source Editor)
/features
/org.eclipse.wtp.wst.sse-feature
feature.xml
...
/plugins
/org.eclipse.wtp.wst.sse.core
plugin.xml
...
/org.eclipse.wtp.wst.sse.ui
plugin.xml
...
/tests
/org.eclipse.wtp.wst.sse.tests
plugin.xml
test.xml
...
Directory Stucture
a.. /home/webtools (cvs root)
a.. /wtp-home (will hold the wtp web site)
b.. /wtp-wst-home (will hold the wtp wst web
site)
c.. /wtp-jst-home (will hold the wtp jst web
site)
d.. /developmentDocs (documentation such as requirements,
arch.)
e.. /org.eclipse.wtp.releng (hold automatic build scripts, maps,
templates)
f.. /wst (web standard tools sub
project root)
a.. /common common utilities and infrastructure including project
support (for flexible, Maven-friendly projects) - we may promote project to
a top level /module later)
b.. /server server framework and adaptors
c.. /internet Internet preferences (e.g. proxy server configuration),
Web browser suport, TCP/IP monitor
d.. /sse Structured Source Editor framework
e.. /command command infrastructure including Environment Command
framework & Dynamic Wizard framework - we need to harmonize several existing
command approaches
f.. /html HTML/XHTML editor, model, views, wizards, etc.
g.. /js JavaScript editor, model, views, wizards, etc.
h.. /css CSS editor, model, views, wizards, etc.
i.. /xml XML editor, model, views, wizards, etc.
j.. /dtd DTD editor, model, views, wizards, etc.
k.. /xsd XSD editor, model, views, wizards, etc.
l.. /ws Web Service, explorer, SOAP, UDDI, & WSIL models & views
m.. /wsdl WSDL editor, model, views, wizards, etc.
n.. /wsi WS-I Test Tools - repatriated from the WSVT project
o.. /rdb relational database model, connections, views
p.. /sql SQL model, scrapbook, buiilder
g.. /jst /j2ee standard tools sub project root)
a.. /common common utilities and infrastructure including project
support (for flexible, Maven-friendly projects) - we may promote project to
a top level /module later)
b.. /server (application server runtime support, frameworks and
adaptors )
c.. /j2ee-modules (common models and abstractions for j2ee ears,
application client, wars, ejb-jar, rars /and project layouts and Common J2EE
models/ Natures/ wizards )
d.. /servlet (servlets, filters webapp DD project support / wizards )
e.. /jsp (editors, model support/ wizards
f.. /ejb - ejb DD project support / wizards , models, views and
wizards (cmp editing)
g.. /jca - J2 connector arch., models, wizards, and DD project
h.. /jndi - jndi utilities, explorer, etc.
i.. /ws - web services, ws client and java webservices using axis
j.. /jms - model support/ wizards
k.. /annotation -common apis and adaptors for providing source
annotations (i.e. xdoclet, pollinate etc.)
|
|
|
Goto Forum:
Current Time: Tue Jul 08 21:10:48 EDT 2025
Powered by FUDForum. Page generated in 0.02971 seconds |
Home