Jacek, Am sure you know this from your experience in the Software industry....I just want to voice my 2 cents.
A lot of companies (including mine) when they decide to develop Software based on Cocoon or to deploy a Application based on Cocoon will use code from third-party vendors *ONLY* under the following circumstances: - Binaries from Third-parties where we are sure we will get Tech Support when/if necessary (AND are sure that the Third-party is going to be in the business for the Product/Application Lifecycle). - Source code is available either in some open source fashion (Apache/GNU LGPL etc...) For example the ONLY libraries we will ever ship in our product will be those in xml-cocoon2\lib\core directory and cocoon itself. So how ever fast,lean and mean your "new XSLT Compiler" is/will-be....It is of not much use to me personally. Thanks, dims --- "Jacek R. Ambroziak" <[EMAIL PROTECTED]> wrote: > On Wednesday 27 March 2002 03:11 pm, Stefano Mazzocchi wrote: > > and your > > fork is perceived as harmful more than useful to us, at this point and > > I'm very sad about this. > > I wouldn't call it a fork anymore; I am building a new XSLT Compiler. > > > I dislike the fact that two > > projects are now sharing the same name. > > > > Sun was the original owner of the XSLTC acronym > > Full synergy here: I don't want the confusion either. > > --Jacek > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > ===== Davanum Srinivas - http://xml.apache.org/~dims/ __________________________________________________ Do You Yahoo!? Yahoo! Movies - coverage of the 74th Academy Awards® http://movies.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
