On Jan 4, 2007, at 12:06 PM, Jeff Ramsdale wrote:
I see on the site that there's a menu section entitled
"Subcomponents." Is that intended to be a mechanisms for organizing
sub-projects? Specifically, should the code repository and site
reflect a separation between the core code and the TCK and (possibly)
other subcomponents? For instance, is there any benefit in organizing
the Sun service implementations accordingly as well?
Whatever feels good. It came from what we were doing in Harmony,
where we have the classlibrary, the build/test infrastructure, the
DRL JVM, the other VMs, etc.
I was thinking of removing it, but left it as bait for discussion :)
geir
Jeff
On 1/4/07, Jim Hurley <[EMAIL PROTECTED]> wrote:
Another piece we should probably consider as part of
the initial codebase (or maybe to include down the line)
is the "Jini Technology Lookup, Discovery, and Join
Compatibility Kit" (LDJ). You can find it under "Associated
Downloads" at:
<https://starterkit.dev.java.net/downloads/index.html>
Way back when :-) under the SCSL, something similar
was named the "Technology Compatibility Kit" (TCK) and
was a legal measure for helping to ensure compliance for
commercial implementations.
I think some people have found it generally handy over
time to use to test their Jini service, etc -- so it might be
good to include.
Thoughts?
-Jim
