> - /LS has a good point about hitting a moving target. There are a couple of > ways of handling that > * A TCK which focuses on established contracts > (ie- merlin/fortress would already pass) > * A TCK which focuses on where we want to be > (ie- merlin/fortress wouldn't yet pass, but we want them to soon) >
+1 > - I'm not sure a single spec would be appropriate. That is, as you > mentioned, there are container<->component contracts as well as > user<->container contracts. Also, one person might be interested in saying > her component is Avalon compliant (can run in an Avalon container) while > other is interested in saying his container is Avalon compliant (can run > Avalon components). These are two related but perhaps separate issues. > +1 Jonathan Hawkes --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
