lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grant Ingersoll <grant.ingers...@gmail.com>
Subject Re: How to handle servlet-api.jar in build?
Date Tue, 12 Jun 2007 10:37:58 GMT
 From what I can tell, Tomcat bundles this, as does Solr, as do other  
products like Jetty.  FWIW, it might be worthwhile to have the demo  
package Jetty like Solr does so that we can run it right out of the box.

Also, see https://issues.apache.org/jira/browse/LUCENE-805

Thanks for helping out!

-Grant

On Jun 12, 2007, at 5:07 AM, mark harwood wrote:

> Thanks for the pointers Paul.
>
>>> I just don't think you can 'package' up a distribution that  
>>> includes these jars in your distribution.
>
> Clearly the binary distribution need not bundle servlet-api.jar - a  
> demo.war file is all that is needed.
> However, is the source distribution exempt from this restriction?  
> It would be convenient if the build.xml "just worked", referencing  
> our included copy of servlet-api.jar rather than requiring the user  
> to configure the build.properties etc to point to their copy of the  
> API. If this bundling was an issue, would an acceptable solution be  
> to have an ANT task to download the servlet-api.jar from a Sun server?
>
> Mark
>
>
>
>
> ----- Original Message ----
> From: Paul Smith <psmith@aconex.com>
> To: java-dev@lucene.apache.org
> Sent: Tuesday, 12 June, 2007 8:13:24 AM
> Subject: Re: How to handle servlet-api.jar in build?
>
>
> 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: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>
>
>
>
>
>
>       ___________________________________________________________
> Yahoo! Answers - Got a question? Someone out there knows the  
> answer. Try it
> now.
> http://uk.answers.yahoo.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-dev-help@lucene.apache.org
>

------------------------------------------------------
Grant Ingersoll
http://www.grantingersoll.com/
http://lucene.grantingersoll.com
http://www.paperoftheweek.com/



---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message