| Package/plug-in naming and CVS organization suggestion [message #564914] |
Fri, 29 April 2005 14:58 |
 Ed Burnette
Messages: 279
Registered: July 2009 |
Senior Member |
|
|
I'd like to suggest that the Data Tools project follow the example of
several other top level projects such as the Eclipse project, Tools, and
Technology in its package naming and CVS organization, as opposed to,
say, the Web Tools project. In particular:
- Don't have 'dtp' or 'data' in the package and plug-in names. It
makes them longer, cryptic (especially with acronyms like dtp) and makes
it harder when moving things between top level projects (for example
moving something from incubation in Technology). I think you'll find it
will work out better to just use the sub-project names and make sure
they're unique.
- Keep the CVS repository flat. WTP's component and category
organization has a few advantages but the big problem with it is it's
nigh impossible to find anything. The extra directories make it harder
to move things around too. So I'm suggesting you keep it simple: one
repository for Data Tools, with each plug-in and feature being a module
at the same level there. Use the "-feature" suffix convention for
features. If you have to have subdirectories, try to just have one
level. Your contributors will appreciate it.
- This one is more opinion, but in general, avoid acronyms,
especially short acronyms that include letters for 'platform' or
'framework' or 'project' or 'eclipse' or 'tools' or 'toolkit' or
'development'. It worked ok when there was only JDT and a few others,
but now it's just getting unworkable.
|
|
|
Powered by
FUDForum. Page generated in 0.03009 seconds
] 
Search
Help
Register
Login
Home
