On 7/3/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
If we go that way, how could we deal with the examples ?
I guess they would either require the use to download the components,
or be available on a separate distros (and thus have their own
release cycle too).
On 7/2/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
> I'd like to start a discussion on splitting the container and
> components release cycles. What do people think about that ?
> Should we keep the container and all the components in a single
> release like we have done so far, or should we split these releases
> and release the components separately from the container ?
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Principal Engineer, IONA
> Blog: http://gnodet.blogspot.com/
>
--
Cheers,
Guillaume Nodet
------------------------
Principal Engineer, IONA
Blog: http://gnodet.blogspot.com/
Testing the integration of multiple components? Is this what you mean
by examples Guillaume?
Yes, this could be tricky. There needs to be a JBI TCKish thing,
that can evaluate BCs, SEs and SAs too. Something that can validate
compliance...
I realize this is probably a bit off-track from where the division
discussion was going - but, in the end there needs to be a way to
ensure components work - without a manual integration. Test cases can
handle some of the load - say for "stock" components. But, it will
most likely be up to the component developers to do the testing (and
it would be nice if there was an easy "test harness" to drop the
component in to to validate.
Kit
