[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[hyades-dev] Hyades Features restructuring
|
Currently, there are a total of nine features in Hyades: source, hyades,
logging, models, core, porbekit, test, examples, and test.examples.
Currently, <includes> have been used to create bigger features, but this
has and with continue to cause serviceability problems. The solution is
use <requires> instead. The list below is the dependencies among the
existing features
Feature Requires
source nothing
logging emf
models logging
core models
probekit core
test core
example core
test.examples test
hyades everything except source
Furthermore, I would like to break the features into a more fine grained
list so that Hyades can be consumed at a more granular level. Several
products which have committed to consuming hyades, and others that have
expressed an interest, do not wish to pick up the entire Hyades content.
Today is it possible to break apart our existing features into the
following additional features.
Feature Requires
test.manual test
test.junit test
test.http test.junit
test.examples.manual test.manual
test.example.junit test.junit
test.examples.http test.http
probekit.examples probekit
profiling core
profiling.examples profiling
logging.examples logging
gla core
One of the biggest unknowns yet is how do we handle NL content. Do these
plugin fragments get packaged as part of the feature or as a separate
feature? If they are a separate feature, they need to correspond 1-1 with
a functional feature. I will see what I can find out about how the base
handles this.
I would appreciate any feedback on this before we move forward.
Richard K. Duggan
Problem Determination Enablement
IBM Toronto Laboratory
External: 905-413-2396
Internal: 969-2396