Skip to content

Commit 133308a

Browse files
committed
Fix steps for maintaining metadata in gradle guide
1 parent df35fdc commit 133308a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/src/docs/asciidoc/end-to-end-gradle-guide.adoc

+3-3
Original file line numberDiff line numberDiff line change
@@ -740,11 +740,11 @@ Considering that you run your tests on CI, at some point (after updating some de
740740
In that case, your metadata requires update.
741741

742742
[WARNING]
743-
Be aware that if you modified existing metadata file(s) on the default location, generating a new metadata will overwrite the existing one and your manual changes will be lost.
743+
Be aware that if you modified existing metadata file(s) in the default (not permanent) location, generating a new metadata will overwrite the existing one and your manual changes will be lost.
744744

745-
So if you modified existing metadata file(s) on the default location, please do the following:
745+
So if you modified existing metadata file(s), please do the following:
746746

747-
1. Move your metadata to some other, non-default location (with the `metadataCopy` task for example)
747+
1. Move your metadata to some permanent location (with the `metadataCopy` task for example), if you didn't do that already.
748748
2. Set `mergeWithExisting` option to true in the `metadataCopy` block
749749
3. Run your tests again to generate new metadata (as we already described in the <<collect-metadata, collect metadata section>>)
750750
4. Run `metadataCopy` task again (with `mergeWithExisting` set to true in step 2)

0 commit comments

Comments
 (0)