# Licensing of Elasticsearch Dependencies
**URL:** https://discuss.elastic.co/t/licensing-of-elasticsearch-dependencies/27505
**Category:** Elasticsearch
**Created:** [August 17, 2015, 1:41pm UTC](https://discuss.elastic.co/t/licensing-of-elasticsearch-dependencies/27505 "2015-08-17T13:41:15Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@jamesbaker](https://discuss.elastic.co/u/jamesbaker)
#### Post date: [August 17, 2015, 1:41pm UTC](https://discuss.elastic.co/t/licensing-of-elasticsearch-dependencies/27505/1 "2015-08-17T13:41:15Z")
I'm working on a software project that outputs data into Elasticsearch, making it searchable. I want to release my project under the ASL2 license (as Elasticsearch is).
However, when I include Elasticsearch as a Maven dependency, I also get the JTS Topology Suite as a sub dependency. The JTS Topology Suite is licensed under the LGPL, and I didn't think the two licenses were compatible?
Could someone clarify what the situation is, and what steps I need to take when I release my project so that I can include Elasticsearch and it's dependencies without straying into dodgy legal territory?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 11:55pm UTC](https://discuss.elastic.co/t/licensing-of-elasticsearch-dependencies/27505/2 "2017-07-05T23:55:31Z")
---
### Author:  [@javanna](https://discuss.elastic.co/u/javanna)
#### Post date: [October 2, 2017, 7:39am UTC](https://discuss.elastic.co/t/licensing-of-elasticsearch-dependencies/27505/3 "2017-10-02T07:39:58Z")
Hi,
the JTS dependency is marked optional. You can exclude it, release without it and everything will work fine apart from the geo features that rely on JTS.