# If your plugin build breaks when upgrading to 5.6+

**URL:** <https://discuss.elastic.co/t/if-your-plugin-build-breaks-when-upgrading-to-5-6/101752>\
**Category:** Elasticsearch\
**Created:** [September 25, 2017, 7:49pm UTC](https://discuss.elastic.co/t/if-your-plugin-build-breaks-when-upgrading-to-5-6/101752 "2017-09-25T19:49:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![loren](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/loren/32/44942_2.png) [@loren](https://discuss.elastic.co/u/loren)\
**Post date:** [September 25, 2017, 7:49pm UTC](https://discuss.elastic.co/t/if-your-plugin-build-breaks-when-upgrading-to-5-6/101752/1 "2017-09-25T19:49:52Z")

</div>

I built a custom ingest plugin with the helpful [cookiecutter](https://github.com/spinscale/cookiecutter-elasticsearch-ingest-processor) and now want to upgrade it from 5.5.1 to use 5.6.1 but the build failed with:

```auto
   > Must specify license and notice file for project :
   > Cannot get property 'projectSubstitutions' on extra properties extension as it does not exist
   > Must specify license and notice file for project :
   > Must specify license and notice file for project :

```

I see that this is because of [this PR](https://github.com/elastic/elasticsearch/pull/26373), but I'm too much of a Gradle newbie to figure out where I'm supposed to specify `noticeFile` and `licenseFile` in my `build.gradle` file.

If you run into this, too, here are the [changes you need to make](https://github.com/spinscale/cookiecutter-elasticsearch-ingest-processor/commit/c94205436debb561549b722ea1badedd7a875f7a) to get your build working again.

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [September 25, 2017, 8:12pm UTC](https://discuss.elastic.co/t/if-your-plugin-build-breaks-when-upgrading-to-5-6/101752/2 "2017-09-25T20:12:18Z")

</div>

Thanks for the write-up, especially since there is very little. I also  
encountered the same issue when updating a plugin. Somewhat silly since you  
can simply link to an empty file.

From what I understand, this check is executed if you use the esplugin task  
inside the gradle build tools. If you do your own assembly, the check does  
not occur. I use the build tools, so I have not checked this theory.

Cheers,

Ivan

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 23, 2017, 8:12pm UTC](https://discuss.elastic.co/t/if-your-plugin-build-breaks-when-upgrading-to-5-6/101752/3 "2017-10-23T20:12:40Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.