-----Original Message----- From: Henri Gomez
Here is a reply I got from the community list :
This is not a complete prohibition on all third-party jars or libraries, but only on those third-party libraries which are licensed under terms more restrictive than the ASL.
Ask them is there any list of accepted licenses and libraries. What about linking to static microsoft libraries?
That is probably not OK.
What can assure them that contributed binaries (and the code itself) are build with legally obtained software?
"legally obtained software" if someone is using those he kills its own business!
Do we need to sign that or ASF will perhaps provide us with the development tools needed?
Use Open Source tools and/or help to improve existing ones.
Perhaps they should think in that direction.
However, mx4j is a good example because apparently it includes code licensed under the Jetty and Jython licenses
Reading this seems that they've already made a decision, without the will to
help us. What are we suppose to do? Hire a lawyer to clear every library
that has a feature to link with the property software or they will? I mean, exactly the same situation as with the tomcat-connectors.
Seem that we cannot provide the binaries for that too, cause IIS apparently
doesn't falls nearly to the ASF license.
Are we linking to the any of the prohibited libraries (like api32, kernel32,
ws2_32)? I'm not sure.
You have to use dynamic linking...
Cygwin brings the same API but the license is not ASF like and the API is not 100% compatible.
Too many questions, and such a small head ;-).
MT.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
