On 12/06/2007, at 5:09 PM, markharw00d wrote:
As part of the documentation push I was considering putting
together an updated demo web app which showed a number of things
(indexing, search, highlighting, XML Query templates etc) and was
wondering what that might mean to the build system if I was
dependent on the servlet API. Are there any licence concerns around
handling servlet-api.jar that I should be aware of? I know Apache
foundation does not like linking to non-Apache code.
You should be fine on this, since many Apache apps need to reference
the servlet-api and jsp-api jars. (JSTL for a start..).
I just don't think you can 'package' up a distribution that includes
these jars in your distribution. That is, a downloaded unit from
Apache can't include that jar in the distribution.
The log4j projects I work in references quite a few non-ASL licensed
things, and as long as you can build a distribution environment that
requires the user to download that (and agree to any licensing bits
and bobs), you should be fine.
This is where Maven is cool...
cheers,
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
