FYI, My company is a large ASP. Each of our customers runs our products as if from their own web site, although they are all sharing the same code. Our development effort is using Cocoon as our Presentation Tier for our products, as it allows us to totally customize the look and feel for each of our customers. Eventually we also want to package the product and sell it to large customers who want to run it at their site. Of course, this will include Cocoon. Obviously, the kind of tricks being talked about here would not allow us to redistribute Cocoon. Our customers would have to get it themselves - which, of course, is totally unacceptable.
Ralph -----Original Message----- From: Torsten Curdt [mailto:[EMAIL PROTECTED] Sent: Friday, March 12, 2004 5:32 AM To: [EMAIL PROTECTED] Subject: Re: Using Maven (or something similar) for dependencies? (Was: Cocoon's Rhino+continuations fork) > Is a company using Cocoon to deliver web applications redistributing > Cocoon? (yes, I think). That's the question! I'd say no ...as long as you don't bundle it and sell it as part of you software removing the license or the like. But AFAIU you may use those (for us) problematic jars in your project. But hell - I am no lawyer. cheers -- Torsten
