X-Git-Url: https://gerrit.simantics.org/r/gitweb?a=blobdiff_plain;f=README.md;h=65aad840fa6309231ceea865e5146082cb266644;hb=aa834e2e72826d0c9d4fe7a5541f085b31fedb05;hp=3bd55dfa1ad35aee3728aade625ad9e6fdf29d12;hpb=e290ec877230764ad5b3f4ee48c50df1c95b07e2;p=simantics%2Fthird-party.git

diff --git a/README.md b/README.md
index 3bd55df..65aad84 100644
--- a/README.md
+++ b/README.md
@@ -10,7 +10,7 @@ If you want to manually bundle an external third-party library into the Simantic
 
 If your bundled library has dependencies to other bundles, you should probably create a feature project in the *features* directory that includes the plug-in(s) required by those plug-ins.
 
-After you've created the necessary plugins and features, use the Eclipse PDE IDE plug-in/feature export wizards to produce the required P2 repository content under /p2/{features,plugins}.
+When building, it is recommended to use a separate otherwise empty workspace and the target definition file */externals.target*. After you've created the necessary plugins and features, use the Eclipse PDE IDE plug-in/feature export wizards to produce the required P2 repository content under /p2/{features,plugins}.
 
 The *publish.sh* script at the root of the repository will be ran automatically by the Simantics platform Jenkins job [SDK/manual-third-party-components](https://www.simantics.org/jenkins/job/SDK/job/manual-third-party-components/). It will create the required P2 repository content and artifact metadata files under the *p2/* directory based on the contents of directories *p2/{features,plugins}*.