Hi Felix,
Please don't feel like I am against lenya. I am with you. I really
apreciate your effort in this great community. :-)
Felix Röthenbacher wrote:
Nope. It is part of the "extras" pack.
AFAIK, we don't need them to run jetty. Giacomo updated jetty in
cocoon without the need of all of these extras.
You are right, but Cocoon is not Lenya. And Lenya uses JettyPlus which
contains some additional functionality like transaction support based on
JOTM that will be handy when it comes to JCR integration. If there are
any licencing issues with these additional libs we should take care of
but AFAIK the libraries from ObjectWeb are open-source.
No problem if lenya requires additional libs that are not shipped in
cocoon. The point is: We cannot add any Open Source License, there are
some licenses that are incompatibles with Apache License.
I know this seems to be a boring task, but if we like Lenya, we need to
take care of the legal issues too! :-) We don't want to have a similar
trial as SCO vs. Linux right? The key to be out of any problem is to
review the license of every piece of code that we include from other
places. We need to copy the license into our repository, because the
license can also change in the mean time.
What about using Maven for Lenya and download the dependencies if
required?
Warning: IANAL
I think it depends of the type of the license. But IMHO even by allowing
a download from other repositories , the end user finish with some
licenses that are not compatible with the ASF. In other way, what is
more important the place from where we download or the final product by
itself? I think we need to raise this concern to the legal@ asking for
advises in this area.
Are there any intentions in the Cocoon community to "mavenize" Cocoon
itself?
Work in progress for cocoon 2.2.
Best Regards,
Antonio Gallardo.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
