I did think about Maven, but (probably because I'm a Maven newbie) I didn't find an obvious way to do it and figured that Maven was meant more for libraries than for complete applications. In any case, your answer gives me more to work with, so I'll do some experimentation. Thanks!
- Demian ________________________________________ From: Daniel Collins [danwcoll...@gmail.com] Sent: Friday, July 29, 2016 11:18 AM To: solr-user@lucene.apache.org Subject: Re: Installing Solr as a dependency Can't you use Maven? I thought that was the standard dependency management tool, and Solr is published to Maven repos. There used to be a solr artifact which was the WAR file, but presumably now, you'd have to pull down <groupId>org.apache.solr</groupId> <artifactId>solr-parent</artifactId> and maybe then start that up. We have an internal application which is dependent on solr-core, (its a web-app, we embed bits of Solr basically) and maven works fine for us. We do patch and build Solr internally though to our own corporate maven repos, so that helps :) But I've done it outside the corporate environment and found recent Solr releases on standard maven repo sites. On 29 July 2016 at 15:12, Shawn Heisey <apa...@elyograg.org> wrote: > On 7/28/2016 1:29 PM, Demian Katz wrote: > > I develop an open source project > > (https://github.com/vufind-org/vufind) that depends on Solr, and I'm > > trying to figure out if there is a better way to manage the Solr > > dependency. Presently, I simply bundle Solr with my software by > > committing the latest distribution to my Git repo. Over time, having > > all of these large binaries is causing repository bloat and slow Git > > performance. I'm beginning to wonder whether there's a better way. > > With the rise in the popularity of dependency managers like NPM and > > Composer, it seems like it might be nice to somehow be able to declare > > Solr as a dependency and have it installed automatically on the client > > side rather than bundling the whole gigantic application by hand... > > however, as far as I can tell, there's no way to do this presently (at > > least, not unless you count specialized niche projects like > > https://github.com/projecthydra/hydra-jetty, which are not exactly > > what I'm looking for). Just curious if others are dealing with this > > problem in other ways, or if there are any tool-based approaches that > > I haven't discovered on my own. > > I wouldn't include Solr in my own project at all. I would probably > request that the user download the binary artifact and put it in a > predictable location, and configure my installation script to do the > download if the file is not there. I would strongly recommend taking > advantage of Apache's mirror system for that download -- although if you > need a specific version of Solr, you will find that the mirror system > only has the latest version, and you must go to the Apache Archives for > older versions. > > To reduce load on the Apache Archive, you could place a copy of the > binary on your own download servers ... and you could probably greatly > reduce the size of that download by stripping out components that your > software doesn't need. If users want to enable additional > functionality, they would be free to download the full Solr binary from > Apache. > > I once discovered that if optional components are removed (including > some jars in the webapp), the Solr download drops from 150+ MB to about > 25 MB. > > https://issues.apache.org/jira/browse/SOLR-6806 > > Thanks, > Shawn > >
