I'll bet Phil thought this would be
a quick and easy question (see attached mailing list item from 12/3) when
he originally asked it TWO MONTHS AGO! (how time flies).
But the issues are still with us --
the map files are a bit meaningless to view, its hard to "load released
a particular component or subsystem,
and worse of all, on busy days its hard to release new project versions
for builds because
a dozen teams might be trying to update
the same files in CVS.
I'd like to propose a new division of
our map files, based on the *subsystems* as
defined in http://www.eclipse.org/webtools/development/arch_and_design/ArchitectureOverview.html.
The reason for picking subsystems, instead
of components, is that we have 24 components, so multiplied by 2, one set
another for tests, gives 48 map files
... I think that's too many to easily view/select for loading/and
just generally manage (and
many would have only one or two entries).
Doing the division by subsystems, still
gives us 24 total (12 main ones, 12 test ones) but that seems more manageable.
(and more "scalable" over time).
The only down side is there's still
some overlap between teams for some subsystems, but should be minimal (usually
just 1 or 2 teams would
share a subsystem). We can always fine
tune later if we still see conflicts while trying to release code for a
build. Plus, I believe subsystems will form the
basis of our (sub)features and units
of maintenance and major dependancies, so its natural there would be a
map file per (sub) feature.
I've placed a file in org.eclipse.wtp.releng\development\proposedmapfiles.txt
which gives a complete listing of today's
plugins, divided up by subsystem, with
proposed map file names. Please review
for accuracy. Following is the list of proposed
map file names ... the main (code) ones
first, and the test ones formed by adding 'test' after
the project name (consistent with preferred
As far as I know, this makes no difference
to the build scripts, which simply look for all
.map files in the maps directory. (Let
me know if anyone's customized any scripts!).
If there's no objections (or calls for
longer discussion), then after this weeks I-build, I will personally edit
the current jst and wst map
files to make this split once ... then
component leads can correct and/or do their own test map files
as the week progresses. Sound reasonable?
If so, I'll plan on making this change on Friday morning (EST).
----- Forwarded by David
M Williams/Raleigh/IBM on 02/02/2005 01:56 PM -----
Phillip Avery/Raleigh/IBM@IBMUS Sent by: wtp-dev-admin@xxxxxxxxxxx
12/03/2004 02:13 PM
Please respond to
[wtp-dev] test map files
It seems like there are (starting to be) way too many map files in the
org.eclipse.wtp.releng plugin (one for each plugin?)
To clean up the clutter, it seems like there should just be one test map
for wst and one for jst. (so just wst-tests.map, and jst-tests.map)