# Building a custom plugin

**URL:** <https://discuss.elastic.co/t/building-a-custom-plugin/26595>\
**Category:** Logstash\
**Created:** [July 30, 2015, 9:15pm UTC](https://discuss.elastic.co/t/building-a-custom-plugin/26595 "2015-07-30T21:15:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![eeveaud](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eeveaud/32/3601_2.png) [@eeveaud](https://discuss.elastic.co/u/eeveaud)\
**Post date:** [July 31, 2015, 8:16am UTC](https://discuss.elastic.co/t/building-a-custom-plugin/26595/2 "2015-07-31T08:16:38Z")

</div>

maybee you would like to check this post.

> [@How to debug plugin installation](https://discuss.elastic.co/t/how-to-debug-plugin-installation/25841/4):
>
> I had similar problem once. is your source code pluggin under git ? as you say that you modified the LS gem plugin I suspect that iti s not. if not gem build will create an empty data.tar.gz directory because of the following line in gemspec. # Files s.files = `git ls-files`.split($\) you can check the content of the generated gem by untaring it pluggin install won't complain if data is empty and claim "installation succesfull" either git init (best way) your source directory in order t…

---

_[View the full topic](https://discuss.elastic.co/t/building-a-custom-plugin/26595)._