Home » Language IDEs » ServerTools (WTP) » Plain Text - WTP CVS Structure
| Plain Text - WTP CVS Structure [message #38859] |
Sat, 14 August 2004 10:08  |
Eclipse User |
|
|
|
This one is more readable - Sorry for the HTML post.
-
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:
Seperate the sub projects.
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.
Keep the names short (for 256 character limits on some systems) for top
level folders.
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
/home/webtools (cvs root)
/wtp-home (will hold the wtp web site)
/wtp-wst-home (will hold the wtp wst web site)
/wtp-jst-home (will hold the wtp jst web site)
/developmentDocs (documentation such as requirements,
arch.)
/org.eclipse.wtp.releng (hold automatic build scripts, maps,
templates)
/wst (web standard tools sub project
root)
/common common utilities and infrastructure including project suppo
rt
(for flexible, Maven-friendly projects) - we may promote
project to a top level /module later)
/server server framework and adaptors
/internet Internet preferences (e.g. proxy server configuration),
Web browser suport, TCP/IP monitor
/sse Structured Source Editor framework
/command command infrastructure including Environment Command
framework & Dynamic Wizard framework - we need to
harmonize several existing command approaches
/html HTML/XHTML editor, model, views, wizards, etc.
/js JavaScript editor, model, views, wizards, etc.
/css CSS editor, model, views, wizards, etc.
/xml XML editor, model, views, wizards, etc.
/dtd DTD editor, model, views, wizards, etc.
/xsd XSD editor, model, views, wizards, etc.
/ws Web Service, explorer, SOAP, UDDI, & WSIL models & views
/wsdl WSDL editor, model, views, wizards, etc.
/wsi WS-I Test Tools - repatriated from the WSVT project
/rdb relational database model, connections, views
/sql SQL model, scrapbook, buiilder
/jst j2ee standard tools sub project root
/common common utilities and infrastructure including project
support
(for flexible, Maven-friendly projects) - we may
promote project to a top level /module later)
/server (application server runtime support, frameworks and
adaptors )
/j2ee-modules (common models and abstractions for j2ee ears,
application client,
wars, ejb-jar, rars /and project layouts and
Common J2EE models/ Natures/ wizards )
/servlet (servlets, filters webapp DD project support / wizards )
/jsp (editors, model support/ wizards
/ejb - ejb DD project support / wizards , models, views and wizards
(cmp editing)
/jca - J2 connector arch., models, wizards, and DD project
/jndi - jndi utilities, explorer, etc.
/ws - web services, ws client and java webservices using axis
/jms - model support/ wizards
/annotation -common apis and adaptors for providing source
annotations (i.e. xdoclet, pollinate etc.)
|
|
| |
| Re: Plain Text - WTP CVS Structure [message #39012 is a reply to message #38980] |
Mon, 16 August 2004 11:23  |
| Eclipse User |
|
|
|
The suggested eclipse prjetcorganization for new projects is to have
enloding folders for modules. Eclipse platform was committe to CVS prior
to that so it is hard to change now I guess, but new projects follow
similar principles (such as equinox and stellation). The suggestion was we
organize plugins under folders such as /plugins and /features for each
project.
However, the shear size size of the wtp project and number of groups is
only second to eclipse platform itself. We needed more structure. The
suggestion was to introduce an extra level which were the "modules". The
modules are typically made up of a group of plugins/features that are
owned by a group of committers.
-
Jeff Duska wrote:
> Is there a reason we wouldn't follow the existing Eclipse 3.0 CVS
> structure and use their tools? I could be wrong, I haven't dug a lot out
> of their CVS repository.
> It seems like each plug-in is a top level project. For example,
> org.eclipse.jdt.core is a top level project in Eclipse 3.0 CVS. I'm
> guess that this is done, because Eclipse doesn't work as well with large
> projects. Since this is a large project, it might make sense to what the
> other groups have done.
> Instead of Maven, Eclipse team already has some type of release
> engineering toolset that is being used for the main platform. Why
> wouldn't we reuse this, since it already works and was made for Eclipse.
> I'm not saying anything here is wrong, I'm just curious.
> Regards,
> Jeff
|
|
|
| Re: Plain Text - WTP CVS Structure [message #39093 is a reply to message #38859] |
Mon, 16 August 2004 16:52 |
| Eclipse User |
|
|
|
I think a flat hierarchy under /home/webtools would be more flexible and
allow projects and subprojects to move around more.
For example, what if in the future somebody wanted to break out all the web
services stuff into a wtp subproject (same level as wst and jst). You'd put
them under /home/webtools/wst/ws which wouldn't make sense at that point.
As you mention, the top level "/" has been flat up to now so people are used
to that. It's easy to find things; almost all you need to know is the
plug-in id. Having a hierarchy under /home/webtools would lead to extra
searching around when trying to check out the source. Plus you're
duplicating the hierarchy that is implied in the plug-in ids.
So I think something flatter would be better.
--Ed
|
|
|
Goto Forum:
Current Time: Thu Jul 24 18:39:30 EDT 2025
Powered by FUDForum. Page generated in 0.34326 seconds |
Home