Hi all, A recent patch, provided for TUSCANY-535, has raised the issue of how will we control project dependencies and make sure that Tuscany doesn't become a mess - a "kitchen sink" of dependencies and technology. The specific issue with TUSCANY-535, is that It introduces several new dependencies to the SDO project. What's worse is that these new dependencies are duplicates of equivalent function provided in existing EMF-based dependencies (e.g., a different XML Schema model). If we generally accept this kind of change, I think that Tuscany will soon become a mess. On the other hand, rejecting patches contributed by the community will not help the project to succeed at Apache.
So the question is, what are the rules? 1) At what point do we add a new dependency vs. duplicate the function in Tuscany? 2) How do we decide which, of possibly many competing, components to use as a dependency? 3) Once we have a dependency that implements a particular function, can we introduce another different dependency, providing similar/same function? 4) Are there good ways to break these things out into replaceable alternative implementations? 5) Does anyone know if and how these issues are handled in other Apache projects? Thanks, Frank. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
