From 95496b3cb45ebb58dd31b6157d45093243667fd8 Mon Sep 17 00:00:00 2001 From: stschott Date: Fri, 1 Sep 2023 12:24:06 +0200 Subject: [PATCH] update doc --- docs/getting-started.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/getting-started.md b/docs/getting-started.md index 4e5d609bb81..d2b41ac9e60 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -53,6 +53,10 @@ You can use bytecode analysis typically when you do not have access to the sourc If you have access to the source code, it is also possible to create a project for analyzing source code. Following example shows how to create project for analyzing Java source code. +!!! info "Experimental" + + The source code frontend is experimental and should only be used for testing purposes. You should compile the code for analysis first and use the bytecode frontend instead. + !!! example "Create a project to analyze Java source code" ~~~java